Any personal favourites that are not so linear that you would like to suggest?
I think it depends. Not entirely sure though. Now given the context of Lemmy right, you can certainly post to instance C from both A and B. Even if your instance (either A or B) will not fetch messages from each other (due to not federating) you can always go see the messages through instance C (not logged in). That probably works for all defederation scenarios but that is also a very loosely defined interaction as both parties will have to do the same.
A diplomatic answer I know.
Its early still. I guess some patience and effort is needed! The journey is home. :)
It's the ActivityPub API (client to server) where clients supposed to interface with so that you could have one client, for all fedi. But turns out server implementations (Lemmy, mastodon etc) find it not so well designed or performant or adequate (or idk what else) so instead they implement their own client APIs, effectively making clients being specific to the server rather than interoperable (one client that could understand all servers). It's reasonable though, it's just .. I thought... that this was already done and established.. but well..
I'd take my kids there. Give them markers and crayons. Let them roam..
That's a very inspiring idea. Thanks for that!
This captures exactly my inner feeling regarding the fact that no fedi servers implement the C2S api .. (I just realised)
But really, this is very well done, thanks for sharing
MS-DOS Mastodon client. Contribute to SuperIlu/DOStodon development by creating an account on GitHub.
![GitHub - SuperIlu/DOStodon: MS-DOS Mastodon client](https://beehaw.org/pictrs/image/ed5766d9-a309-4ec2-a38b-151e7a6d0368.png?format=webp&thumbnail=256)
Then maybe I got confused sorry. Somebody mentioned it and then the post was saying it's a service I thought it wasn't open. Will check it properly later. Shouldn't have spoke so quickly I guess
However it does not look like it is open source.
The MIMI working group is chartered to define tools that messaging providers can use to interoperate with one another. The W3C ActivityPub protocol is already widely used for several use cases that resemble the MIMI use case. This document examines whether ActivityPub might be a good baseline for ...
Isn't that a (implementation) detail beyond the point of uselessness though? The big point for me is there. To keep it with the metaphor, that tree is also quite a complex structure, yet still useless.
However let me just bring into mind that we recently defederated from some Lemmy instances and for which reasons we did that (as beehaw I mean).
Friendica, I believe, federates their groups. You can see them from mastodon as a user. I guess in AP vocabulary they are an actor. You can post to the group from mastodon too.
Also how's the setup? You setup for example 5 max children in fpm and 5 persistent connections? Per server? So your overall connections to the db server will be 5x your server instances?
If you setup 5 fpm children and less connections, one child will eventually reuse from another, but only when the connection is free (does not do a query for another process or pdo does not consume a resultset). If it tries to do a query at that time it will have to wait and it will block. This is my understanding. Also how you do transactions with persistent connections?
This has evolved into such an interesting conversation.
Hades was really good. Also Bastion from the same developers.
It's not that there isn't the option, it's just that I don't know how to help you. MySQL has an option to reconnect, I suppose might be the same for postgres?
The single running process that was so easily dismissed, could save tons of queries, for example! Sorry I keep thinking about that direction
Oh, I see what you mean now. I think I was looking at it from a more technical perspective. One could say that essentially LW is phishing the beehaw communities right now :D
Not entirely sure on what is the oversight.
I've been reading for AP these days so it's out of my understanding so far.. I might be wrong.
So from my understanding, the owner is the one that is responsible for holding the master copy. Given that the community is a owned by beehaw, all other places except LW that actually accepted the message(s) shouldn't see it.
Otherwise LW would have to ask beehaw every time if the message should be accepted, which would be very problematic and not close to federation but more like replication ("every server using activity pub is an active relay").
Imagine sending an email and your server not accepting until it receives a positive answer from the recipients server that your mail was accepted. You wouldn't see your email at the sent folder up until 4 days. You wouldn't even know if you actually sent the message after you click the send button.
Also excuse my lengthy post, I think it's because understanding AP is recent for me.
If anyone that has a better understanding than me, please feel free to correct me