silverpill

If you want to run your own node, check out mitra (its i2p docs). This software powers mastodon.i2p

@phnt @sun Miniapps

@pernia About the same size

mitra=> SELECT pg_size_pretty(pg_database_size('mitra'));
 pg_size_pretty 
----------------
 903 MB
(1 row)

This might due to aggressive pruning, which is enabled by default here.

@sun @lnkr I think the equivalent of realtimeChannel can be implemented over ActivityPub too - client-to-client encryption is not very difficult. Iroh is not magic either - when it doesn't know how to connect to a peer directly it connects to a relay operated by the iroh team. I suspect this relay is used for the vast majority of iroh connections, so ActivityPub might be actually a better choice because AP servers can act as relays and we already have so many of them.

@lnkr @sun Yes, I think we can just ignore joinRealtimeChannel. It is marked as "experimental" in the docs, anyway

@sun So, I think the biggest problem with this proposal is that it requires a publicly accessible HTTP server. Is there a good reason for that?

WebXDC, for example, is designed for offline first apps. I am reading WebXDC docs right now and it seems to be compatible with ActivityPub. Maybe we should work on this instead?

In this FEP, roles are not limited to "admin", "moderator", .... Custom roles and permissions are also allowed.

@nimda Much appreciated.

@pernia @kirby You said it's only two lines if we switch to another argon library. That's beautiful

@evan It depends on the terms of the agreement.

No agreement should be necessary, though - FEPs are in public domain, they can be implemented by anyone and can be included in other documents without restrictions.

Also, it is not clear what is the benefit of submitting a FEP to W3C. I already submitted it to the FEP repository, and this was always enough for everybody, including major players like Mastodon and Lemmy. These task forces look like totally unnecessary bureaucracy, I don't really have time for that.

@julian

@nimda I will be adding more pages to the panel. Do you have any suggestions?

The last time I checked, not much progress had been made there. However, they are welcome to provide feedback on this FEP.

The super admin is a server operator (or the controller of a DID if group's id is an 'ap' URI).

@nimda Do you like the admin panel?

@JasonW I've seen people using https://gancio.org/ (it's ActivityPub based)

Adding examples: https://codeberg.org/fediverse/fep/pulls/909/files

I think Follow-Accept could be broken down into Create(Relationship) and Add activities.

Group actors should have the maximum privileges because some actions may need to be performed by a Group actor rather than an admin or moderator actor. This may be necessary to protect moderators from retaliation, for example. Another use case for this is anonymous groups where all posts are attributed to a Group actor (example: Telegram channels).

Multiple admin actors are already allowed - in this FEP and in FEP-1b12.

@japananon Sure, I'll add that. Most mitra CLI actions will be available in the admin panel. I also want to move some configuration options from the YAML file to the panel.

@phnt @theorytoe @sendpaws @caohuak I want everyone here. All social networks, video platforms, messengers, even email.

How to deal with the consequences of technology becoming ubiquitous is a separate question, I think. Twitter migration was disruptive because almost nobody was prepared for it but we're still here, the network survived.

@phnt @theorytoe @sendpaws @caohuak

>I nominate everybody in this thread.

I am completely serious - only Dark Fedi people can be trusted with maintenance of the most important communication protocol of the 21th century.