Notices by silverpill (silverpill@mitra.social), page 43

@kowalabearhugs There's no obligation, but what are the alternatives? I only see Twitter and Discord mentioned. And what is the point of using these services? Looks like organizers are trying to prevent people who actually value privacy from participating.

@gabriel Lol this is so bad that Dero looks like a work of art in comparison

@gabriel Never heard of tree network. What is that?

@cheeaun There is a FEP which describes feature detection mechanism, but I don't know how many server developers intend to implement it: https://codeberg.org/fediverse/fep/src/branch/main/fep/9fde/fep-9fde.md (by @nikclayton)

@cheeaun @neet

>supports('@pixelfed/trending')

Oh interesting, how it works? Is feature detection included in masto.js library?

@frogzone @kowalabearhugs Forgejo has federated stars: https://domaindrivenarchitecture.org/posts/2024-03-27-state-of-federation/
They say it is almost ready for production.

This is only the first step, but also the most difficult one, so hopefully federated replies and issues will come shortly after.

@kowalabearhugs

>Join dedicated hackathon Discord

Discord? Really?

@arcanicanis Even 115MB is too much for me. May I have an invite to were.social? Thanks in advance

@gabriel Dero is a scam. I did some research on them a couple of years ago and came to conclusion that they don't actually have the technology. They were making extraordinary claims about solving very difficult problems, but there were no documentation, and very little amount of code.
People who were working on the same problems (FHE/ZK) also said that Dero is not what it claims to be.

I haven't heard of Dero for a while, but recently their shills again started to talk about it in various crypto-related chatrooms.

No idea what they are doing now. A vaporware can become real if enough people believe in it, but it will never be good.

@cuchaz There is an option to donate to Servo development

https://servo.org

@arcanicanis How much memory Prosody / ejabberd require? I may consider this option, though registering on someone else's server would be better for me.
Also I don't mind furries.

@arcanicanis @Inginsub @PurpCat @f_o_u_r_t_y @perplestuff @Pawlicker @thegame6668 Any suggestions? I'm looking for a new home too

@simon @posts

This command line client implements AP C2S https://github.com/evanp/ap/

Streams should have a working C2S implementation on the server side: https://codeberg.org/streams/streams/src/branch/release/FEDERATION.md#c2s

@hongminhee Yes, GtS uses /main-key path. This is the only project I know of that does it differently

@fentiger DID methods such as key: represent identity types. Right now the development is focused on simple key-based identity, but other kinds of identity are also possible with FEP-ef61. Managing keys is difficult and many people will probably want to delegate this task to identity providers. With DIDs this is very easy, just replace did:key with did:web.

Other DID methods can also be used, FEP-ef61 enables further experimentation with identity.

Of course we can invent our own standard for representing identities, but DID standard already exists and developers are more or less familiar with it. Some may dislike DIDs because they are associated with blockchain technology but this too shall pass. If technology works, eventually it will be widely accepted, and if not it will be forgotten. And in any case, DID standard does not depend on it, there are maybe 2 or 3 mentions of "DLT" in the entire spec.

@mikedev Another thing that should probably be changed is format of URLs (mentioned in Discussion - URL scheme section):

People familiar with DID standards are saying that the idea of a "wrapper" method such as did:ap is not well aligned with the DID spec, and my implementation experience also shows that self-referential DIDs make DID parser more complicated than it should be.

FEP-ef61 breaking change: https://codeberg.org/fediverse/fep/pulls/295

Resolvers are now gateways and may accept POST requests.

#fep_ef61

@hongminhee In theory locations of public key and actor object can be different, but in practice this feature only makes software more complicated for no reason, and you can make Fediverse more friendly to developers by not supporting it. Almost everyone already uses fragment IDs, so you can either ignore projects that contribute to protocol decay or add special rules for them

@juanro49 There was an embarrassing bug in 2.15.0. I recommend updating straight to 2.15.1

https://mitra.social/objects/018ec04c-f239-e36d-4c6f-febc9e8d82a8

@Hyolobrika Thank you, this page is very helpful.