In my week off I had intended to work on my #JsonLD#FEP, but my body had other plans on one front and the internet had other plans on another front, so here we are.
#FEP#AE97 is interesting, but while it makes possible open relays (in the #SMTP-relay sense) obviating the dependency on much static infrastructure for message emission, reception remains a problem.
Standards are codified activity.
Standards bodies sometimes help create standards and sometimes hurt them.
There can be standards without the standards bodies.
We all get that right?
Some seem to be in denial about that.
Many so called standards in standards bodies never get any meaningful usage.
And many standards live happy lives long before they get into standards bodies, if ever.
I want to find a solution to #moderation tools like #fediblockmeta inadvertently advertising content they oppose. I want to design a safety tool different in execution from #fsep and #fediseer.
I'm introducing an idea called #fediflags, where servers can moderate servers blindly, based off info supplied by the moderated server itself. Has a server ever asked another to BE suspended, or to have their media rejected? Well, with this they can, to ALL applicable servers.
@Gh0stVX Several people have put forth various proposals on how to address the latter problem in a systematic way: it is easily doable within AP, but not necessarily within mastodon, and playing nicely with AP doesn't mean much if you can't get the major tools to support it.
But flagging per user (or per message) is comparatively easy.
This #FEP is an attempt to make a synthesis of various approaches to implementing portable identities on Fediverse: Mastodon's "Move to a different account" feature, Nomadic Identity in Hubzilla and Streams, and FEP-c390 identity proofs.
Hey #fediverse and #ActivityPub devs: is anyone aware of any specs, proposals, or discussions regarding the announcement of multiple different profiles for different activity types in Webfinger JRDs?
Would be amazing if we could use the same user address to point to different URLs for profiles for micro-blogging, photo sharing, book reviews, etc..
@raucao I'd encourage you to participate on the #SocialHub community forum and in the @fedidevs matrix channel to bring up such functionalities. If there's interest or you want to take it furter, an #ActivityPub#FEP can then be created.
Extra-features (disabled by default) is somewhat confusing in #Fedilab.
This option allows to enable features that #Mastodon doesn't support (quotes, reactions, submit messages in a specific format, etc.)
But softwares like #Pleroma, #Akkoma, #GlitchSocial, #FireFish don't support (currently) same features.
We plan to use #NodeInfo to automatically enable features depending on the user's instance (ie: software).
The fragmentation among friends that follows Twitter’s collapse is exactly the kind of problem that Mastodon and the social web solves for. Imagine that you don’t have to pick and choose which new platform to adopt, or make and maintain a million accounts—because you can follow anyone regardless of which platform they’re on. That’s our reality.
The extension mechanism isn't very well specified and mostly done on best-effort basis in the scope of particular projects. They are tricky to do well too. For a broadly interoperable app you need to 'dumpster-dive' various codebases and reverse engineer. Then whack-a-mole to keep interop alive as these codebases change.
At #SocialHub the #FEP process is trying to bring some order..
Doing some writing on #JsonLD and realizing that JSON-LD is really doing two things.
It is providing a mechanism for converting back and forth from RDF.
It provides a way of describing a syntactic presentation of the data that is distinct from the semantic interpretation. Technically it provides several different syntatic presentations that lead to the same semantic interpretation.
But for most protocols (1) isn't important and (2) is usually standardized on a single presentation.
This is part of why concepts like #JsonLD Framing ( https://www.w3.org/TR/json-ld11-framing/ ) exist, but these sorts of tools come with substantive performance penalties and increases in complexity.
But we can absolutely 100% address this in something like a #FEP.
If you want to be kept in the loop on new #Fediverse Enhancement Proposals, or FEP's, which document best-practices extensions to #ActivityPub and related protocols, then simply follow:
@feps
And once you do, give every #FEP-related toot your boost, to maximise awareness and help make a more interoperable social networking landscape.
Considering writing an #FEP that allows using #IndieAuth logins as display handles. The basic idea is that next to the meta tags/headers for OAuth links, you'd have a public key that can be used to verify a signature placed in a field in an AP Actor object. There would be another field next to the signature that tells remote servers what the preferred handle is. If lookup succeeds and the signature is valid, show the handle (possibly simplified) next to an IndieAuth icon.
Idle thought — what happens when a server is temporarily down? According to #ActivityPub spec, sending instances should re-deliver:
> For federated servers performing delivery to a third party server, delivery SHOULD be performed asynchronously, and SHOULD additionally retry delivery to recipients if it fails due to network error.
Deliberately vague by design, I wonder if there's an #fep that specifies something more, e.g. exponential backoff, batching, when to give up, etc.
Since the lemmy issue is getting overrun with people talking about other proposals, I'm thinking about submitting this as a #FEP. Is that still a useful process? I don't know how many projects look to FEPs for implementation guidance.
I and others have talked a lot about the #Facebook / #Meta#FediVerse issue over the past few days, analyzing their strategy, and possible responses, and why pre-emptive blocking isn't an effective measure.
This leaves the question of "what should we do?" So....
ITT: actually effective measures for building the resilience of the FediVerse and #ActivityPub, informed by the experience of the #OSS movement.
To add to his points, I want to encourage everyone supporting pre-emptive blocks to look at that from the POV of our relationships with people using fediverse servers owned by DataFarms, rather than our antipathy to their owners.
@strypey sorry, how does connecting with other networks relate to moving services with connections intact?
#XMPP has #XEP, for servers to specify what features they support. Unless AP servers start enforcing that supported #FEP s be specified, you don't know that a new kid (bully?) on the block will both federate and support account portability (or when they stop supporting something).
At the #SocialHub developer community that evolves the #Fediverse and the #ActivityStreams / #ActivityPub open standards we are thinking of using #Gherkin and #BDD test suites to formally define the expected behaviour of the protocol and AP vocabulary extensions that various apps use.
Among others this will be part of Fediverse Enhancement Proposals or #FEP's. See:
I'm wondering how the #Mastodon folks who were mortified to find out the #ActivityPub protocol specs to be pretty wanting re #privacy when they found out the *key apps had long had 'full text search' are feeling now having all these folks joining the #fediverse from #Reddit, and being able to access the same social timeline. Oh and #Meta coming soon.
For all the talk about the #fediverse being queer-built and a space for minorities, it's quickly been shown to not be that rugged #safety wise at the mass adoption level beyond a social contract and the fediblock.
My #Instagram is on private, thanks to the amount of bots and creepy guys that try to follow & message me. Can't wait until they can harass me on #Pixelfed, or worse - here. And if the laugh-reaction pile-on cookers that harass the queer creators I follow on Facebook ever get here, let alone my Karen and Kevin relatives and school friends, who'll force me to lock down here when they're not longer "over there", then we're gonna need to reinvent the fediverse again. Web 1.0 third times a charm or something.
I'm beginning to see why being a niche unknown community mostly using the same software was considered safety by so many.
Contrary to most people I consider ANY interaction of people online to be an example of social networking. If you consider that, this goes way beyond where corporate #SocialMedia are, and also way beyond the extent that current fedi apps are duplicating their functionality.
As for the #ActivityPub#FEP process.. anyone can and should contribute here if they can, so that we might move in the direction of this diversity and heterogenous nature of our #FediverseFutures.