silverpill

@jupiter_rowland @elle I am also concerned about mobile and desktop clients. The developers may not want to add Rust compiler to their toolchains.

Nice. I'm going to keep an eye on it.

@elle It's good that you brought it up. I think fediverse standards should be discussed on Fediverse.

In addition to MLS, I want to explore:

- DMLS variants
- BeeKEM
- Autocrypt

@elle If nobody can implement it, it's a bad standard.

I didn't say that we should go in a totally different direction. But how ActivityPub E2EE will look like remains an open question.

@elle It's not the main standards body, it didn't even exist before 2022-23 https://lists.w3.org/Archives/Public/public-swicg/

At that time, we already had FEP process and 12 years of fediverse development behind us.

Do you see many fedi developers in these github working groups? I don't. And there is a good reason for that.

What other AP frameworks do you know of?

This one is used in Mitra and all my other projects: https://docs.rs/apx_sdk/latest/apx_sdk/

There are many libraries, actually - the Delightful List has already been mentioned in this thread. But most of these libraries are not actively developed, or not used in any serious project.

So I've been thinking of adding a curated list of libraries to the ActivityPub developer guide.

It's been a while since an update! While the automated status updates on this account have stopped (four years ago), the site has been running in the background all this time. Work has been done by the new owners to fix some of the performance related issues, and to modernize the site. Latest updates, in addition to fixing loading times, include icons for most of the major platforms and a search box for instance names.

Check it out and join the Matrix chat room.

https://the-federation.info

#thefederation #fediverse #activitypub #diaspora #decentralization

@benpate @elle The observed output and the very existence of SWICG is completely at odds with what I do and what I value about Fediverse, no matter what the intentions may be.

@elle @mkljczk It returns 404. Maybe the author deleted the post.

@elle

bureaucracy

Bureaucracy is not necessary, the FEP process proves that. However, I can tolerate bureaucracy if people who are running the standardization process are qualified for the job. E.g. I wouldn't mind if fediverse was represented by an alliance of Mastodon, PeerTube and Lemmy developers.

I'm also down to work together with you on writing an FEP together, and/or writing up some of my ideas about how an MLS-based protocol could work

That would be great, although I am not sure if MLS is our best option. It is too complicated.

When the fourth activity appears, the context is checked, C's reply isn't in it, and I proceed without knowing about it. Oops!

I don't understand this part. Is C's reply being dropped?

I think if you encounter an object where inReplyTo is not known to you, that unknown object should be fetched, regardless of context.

this is related to FEP f228.

FEP-f228 specifies a backfill algorithm that works from top-level post down the thread. But it would be nice to provide an algorithm that works for any post in a thread. I'll think about it.

@yuzuki How do you want blocks to be implemented?

The federation filter system is more thorough. For example, it can prevent user's messages from entering your server. But it affects all local users.

As @caohuak says, user-level blocks wouldn't differ much from mutes.

@greyarea

>Non-Interactive-Key-Exchange

I think interactive key exchange is fine too. Activities and requests are often sent back and forth between fediverse servers. The most canonical example is probably the Follow activity to which remote server responds with Accept.

>but if you have cryptography related questions, please let me know.

Thank you. I will surely have a lot of questions in the future.

@elle

also, what do you mean by corporate takeover?

This picture: https://pl.fediverse.pl/objects/2fee01c3-d3d2-4443-9dd5-6d4ec84580c4

(thanks @mkljczk)

@mkljczk @elle What did they present?

@elle

fwiw the gate is pretty easy to open, but does require signing a CLA.

It's not that simple. But it might appear easy if you don't inconvenience them too much, and jump through all the hoops https://github.com/swicg/charters/blob/main/stage-process.md

how else do you suggest we develop an E2EE protocol for the fediverse?

In the same way as everything up until this moment has been developed. Somebody just needs to do it.

If the result is good, others will copy it.

>you mention in your FEP that you are giving up on it for a proper E2EE impl. genuinely asking b/c I'm interested in getting E2EE, hopefully interoperable with widest number of clients possible.

Not giving up - I want to explore a more advanced encryption scheme. I think the basics are not going to change too much.

also, what do you mean by corporate takeover?

A lot of things.

@harblinger I agree that /api/v1/statuses is generally useful, and would be happy to merge your implementation even if you don't need it.

>conversation-root-proposal.md

Sounds good (and easy to implement)

@elle No, I don't want to participate in corporate takeover of fediverse. I didn't come here for gatekept workgroups and endless meetings.

@harblinger Does it make the /conversations/public endpoint unnecessary?