Part of my frustration with #ActivityPub and one of the things I find baffling giving everything else in it: the lack of tools for backpressure.
Backpressure is fundamental in building reliable distributed systems (c.f., Notes on Distributed Systems for Young Bloods). From a C2S perspective I get why it wouldn't need to be specified, but from a S2S federated protocol perspective its absence is frustrating.
All that it says is to take care not to overwhelm others and a bit on rate limits
Just saw in a random discord from a few months ago that certain Fediverse softwares don't federate "Trending".....but NO Fediverse software federates "Trending", it's all propagated with posts from users that people on your instance follow. That's how it is for EVERY software that I've used so far.
If an instance doesn't know about an account posting with a specific hashtag, then it can't trend, now can it?🧐Just sayin....
Obviously I don't know everything there is to know about Fediverse and ActivityPub. I don't have firsthand knowledge because I'm not a dev.
However, what I do have that a lot of others don't, is passion.
I am passionate about the Fediverse in a way that I don't think some people are. I want this platform to succeed and thrive because if it does, then so do I because then I get to interact with SO many more talented people!
THAT is what I'm advocating for. Open platform by default with the options to choose who you do or do not want to interact with and the content you do or do not want to see.
No whispering sweet nothings into the algorithms ear. No forced ads. No cookies to track me across websites.
This is the future of social media and if I'm the last damn person here, then sobeit. But I love most of you people here and I believe in all of you. I believe we can make this platform a safe, welcoming, open platform where we can share our lives, passions, jobs, and hobbies across the federated universe of social media.
The future is you. Without each of you. Fediverse wouldn't be where it is today and neither would I.
The max_id, since_id, and min_id parameters in #Mastodon's Timeline API assume that the post ID is a sortable number. (Is this correct?) #Hollo, the #ActivityPub implementation I'm building, uses UUIDs for post IDs internally, so I'm stuck on how to implement a Mastodon-compatible API.
If you're looking to host your very own single-user/a-few-users #fediverse instance, you cannot go wrong with #snac. It is simple to install on Ubuntu and works very well with some really solid clients. It is also written in C, so it is fast, with few dependencies. Great work @grunfink, you've got a new monthly supporter on Ko-fi!
@BeAware Threads.net at least does something to get integrated, I can already read posts from many interesting people from Threads. I am not sure if Bluesky will ever catch up, it still does not have video posting ability, and #atproto is very hard to bridge to #ActivityPub (I read both protocols' specifications and know what I am talking about)
Bluesky enthusiasts are stating that Bluesky has ”plans” to make ATProto universal and transfer it to W3C or the like. Well, there is no evidence that Bluesky wants to give up control or the protocol is going to be widely adopted after 5 years of development so forgive me being sceptical. The story is a bit different with ActivityPub.
Both Rachel and Peter suggest that some moderation functionality could/should become part of the protocol stack. #AtProto does composable moderation and that is really cool. Peter hopes that #ActivityPub may learn from it and evolve in this direction.
"In 2024, for the first time, it finally feels like we have a critical mass of people and platforms who are interested in rewilding the internet to bring back what we lost, and create something new. ... There's a palpable feeling that this just might be the year of the open web."
Did you know about the Momostr.Pink Bridge to Nostr that's currently "opt-out" (just like the rest of the Fediverse) and that Nostr doesn't allow deletes of any kind by normal users?
Nevertheless, if you didn't know about it, you know now. Knowing what you know now, do you feel you were a BIT heavy handed regarding BridgyFed and the absolute ridiculous harassment of it's developer? And do you realize now, that there's MUCH worse things here than a bridge to BlueSky and your knowledge of ActivityPub and how it works were previously incorrect?
PS. If you don't feel that this poll applies to you. Don't answer it. I didn't expect complete parity between the polls. Just answer whichever poll you think fits your experience.
Lol. Just found a workaround for replies not showing up on followers timelines. Just boost the reply yourself!🤣
Idk why I didn't think of this. I guess some would find it annoying to see I boost my own posts, but I wouldn't have to do it that way if it was shown to my followers in the first place!🤦♂️
All in all, I found a temporary solution until the issue is somehow worked around down the line...🤷♂️
@dansup there used to be a full-blown (non-federated) remake of Stackoverflow in a GH project. Firing it up would give nearly the same UI and a whole bunch of the gamification features.
I was only mildly interested at the time, and did not star or anything. Later on, seeing "federated SO" thread for the N-th time I tried to find it again on multiple occasions. No luck, unfortunately.
Such project would be a great basis to add #ActivityPub to.
@julian
Interesting. Does #NodeBB implement #ActivityPub natively as its core mechanism or is there a plugin to allow a NodeBB server to be federated? @BeAware
What do you mean by Meta "supporting" servers?
Everyone is demonizing with extreme ignorance the word Ad. Every account in the #Fediverse IS an AD, is a promotion. Me with this toot I am promoting myself and what I think, Im selling my ideas to everyone who reads this. Every #threads post that anyone sees in the fediverse is and AD for Meta. So again before demonizing the word advertising can you explain in tech terms how using #activitypub instances "will run ads" ?
#activitypub The Podcast Index ActivityPub bridge now properly handles Mastodon "authorized fetch". If you had trouble following a podcast from an authorized fetch enabled instance, please cancel that follow and try again.
This may also resolve other sporadic follow issues from Sharkey/Misskey instances. Testing from people on those platforms would be welcome.
But if #BridgyFed becomes more user-friendly, that will be a big step towards interoperability. And we can finally put this silly competition between #ActivityPub and #ATProtocol to rest.
I believe Flipboard will prove to be a counterweight to Threads and a prime location for news & pundits (as #Meta does not really desire the latter two on their platforms).