Conversation

Notices

1. Embed this notice
   Alex Gleason (alex@gleasonator.com)'s status on Monday, 09-Oct-2023 22:24:00 JST Alex Gleason
   The comments are interesting. https://evanp.me/2023/10/06/activitypub-the-socialcg-and-the-social-web/
   • Embed this notice
     Sexy Moon (moon@shitposter.club)'s status on Monday, 09-Oct-2023 22:31:56 JST Sexy Moon

     in reply to
     @alex > I think Blue Sky, Nostr, and others are a threat to ActivityPub breaking out and becoming ubiquitous.
   • Embed this notice
     Rusty Crab (rustycrab@clubcyberia.co)'s status on Monday, 09-Oct-2023 22:38:22 JST Rusty Crab

     in reply to

     • Sexy Moon
     @Moon @alex
     >be activitypub
     >suck
     "why are people making competitors"
     Sexy Moon likes this.
   • Embed this notice
     Sexy Moon (moon@shitposter.club)'s status on Monday, 09-Oct-2023 22:40:12 JST Sexy Moon

     in reply to

     • Rusty Crab
     @RustyCrab @alex as long as activitypub implementations are dominated by Mastodon, the "standard" is second-fiddle anyway
     Alex Gleason likes this.
   • Embed this notice
     Tassoman (tassoman@orwell.fun)'s status on Monday, 09-Oct-2023 22:40:48 JST Tassoman

     in reply to
     I think time has come, for an AP update, after years. But no one wants to puts his hands on it.
     Too much time has passed cooking and now it's too hot. Should had happened already a few years ago.
     That's why of today's protocols proliferation and competition.
   • Embed this notice
     Alex Gleason (alex@gleasonator.com)'s status on Monday, 09-Oct-2023 22:42:17 JST Alex Gleason

     in reply to

     • Tassoman
     @tassoman The update it needs is ChatterNet: https://github.com/chatternet/chatternet-client-http
     
     But what do I know
   • Embed this notice
     Rusty Crab (rustycrab@clubcyberia.co)'s status on Monday, 09-Oct-2023 22:44:57 JST Rusty Crab

     in reply to

     • Sexy Moon
     @Moon @alex the "push only" problem is such a colossal fuckup that the protocol should have never been published to begin with until that was fixed. "I love seeing threads full of missing responses and holes" said the crazy person.
     Alex Gleason likes this.
   • Embed this notice
     Rusty Crab (rustycrab@clubcyberia.co)'s status on Monday, 09-Oct-2023 23:35:28 JST Rusty Crab

     in reply to

     • Sexy Moon
     • Rusty Crab
     @Moon okay @alex maybe you know why but is there a good reason that AP does not have a condition that says "if you read a post, request a list of replies to said post from OP's home server" because that would fix 99% of the issue. I don't need all posts from everywhere always but I do need all posts in that thread.
   • Embed this notice
     Pawlicker (purpcat@clubcyberia.co)'s status on Monday, 09-Oct-2023 23:35:28 JST Pawlicker

     in reply to

     • Sexy Moon
     • Rusty Crab
     @RustyCrab @Moon @alex almost like there's an inbox thing nobody uses
     https://www.w3.org/TR/activitypub/#server-to-server-interactions
     Alex Gleason likes this.
   • Embed this notice
     Alex Gleason (alex@gleasonator.com)'s status on Monday, 09-Oct-2023 23:37:38 JST Alex Gleason

     in reply to

     • Sexy Moon
     • Rusty Crab
     @RustyCrab @Moon That's called the outbox: https://clubcyberia.co/users/RustyCrab/outbox?page=true
     
     It's not used because 1) push is more efficient than pull, 2) babies on Mastodon scream and cry whenever a software uses it.
   • Embed this notice
     Alex Gleason (alex@gleasonator.com)'s status on Monday, 09-Oct-2023 23:55:40 JST Alex Gleason

     in reply to

     • Sexy Moon
     • Rusty Crab
     @RustyCrab @Moon When a server pushes, it already has the post in memory. When it pulls, it is requesting the remote server to get the post out of its database. The remote server should rate-limit that. And on the Nostr pull model it does, which is a challenge I'm facing in Ditto. If the CLIENT pulls, it has its own IP unique to the user. If the server pulls, it will quickly get rate-limited. In Ditto I will have to mostly rely on a push model, and perform pulls through a narrow pipe where I rate-limit myself in a batched queue type of thing. The client-relay model goes with the grain (what I'm doing goes against it), although it brings a different set of challenges.
     
     ActivityPub does pull in some cases, mainly for fetching posts inside of threads, and for direct links pasted into search. The reason you're seeing broken threads is because of private accounts, deleted posts, domain/IP blocking, network failures, and other bugs. Nostr does improve the situation by making everything portable, and because the developers are more focused on public conversations and anti-censorship. But it's more about design choices of existing software in either protocol than a technical limitation of either protocol.
   • Embed this notice
     Rusty Crab (rustycrab@clubcyberia.co)'s status on Monday, 09-Oct-2023 23:55:41 JST Rusty Crab

     in reply to

     • Sexy Moon
     @alex @Moon mastodon is its own separate network as far as I'm concerned. I will take your word on the efficiency but I do not see why that would be a problem if the scope was limited to that one specific thread being requested.
   • Embed this notice
     narcolepsy and alcoholism :flag: (hj@shigusegubu.club)'s status on Tuesday, 10-Oct-2023 00:12:09 JST narcolepsy and alcoholism :flag:

     in reply to

     • Sexy Moon
     • Rusty Crab
     @Moon @RustyCrab @alex a damn second-fiddle, too.
     image.png
   • Embed this notice
     Alex Gleason (alex@gleasonator.com)'s status on Tuesday, 10-Oct-2023 00:13:10 JST Alex Gleason

     in reply to

     • Sexy Moon
     • Rusty Crab
     @RustyCrab @Moon Check the network tab and see if it makes an API request when you hit reply. I'm not aware of any endpoint to do that. It just recursively fetches the inReplyTo for posts when the post first comes in.
   • Embed this notice
     Rusty Crab (rustycrab@clubcyberia.co)'s status on Tuesday, 10-Oct-2023 00:13:11 JST Rusty Crab

     in reply to

     • Sexy Moon
     @alex @Moon
     >ActivityPub does pull in some cases, mainly for fetching posts inside of threads
     my experience with this is odd on pleroma. Threads are usually missing a bunch of posts by default UNTIL I click on reply arrows from people I am already either following or someone else on my server is following. That tells me that they can be fetched but they aren't by default. If that's not intentional then that's a big implementation problem.
   • Embed this notice
     :ihavenomouth: (inginsub@clubcyberia.co)'s status on Tuesday, 10-Oct-2023 00:14:08 JST :ihavenomouth:

     in reply to

     • Sexy Moon
     • Rusty Crab
     @RustyCrab @alex @Moon I think pleroma-fe doesn’t pull threads in real time, it loads your follows and adds the posts if they happen to be in the same thread
     Alex Gleason likes this.
   • Embed this notice
     Alex Gleason (alex@gleasonator.com)'s status on Tuesday, 10-Oct-2023 00:15:13 JST Alex Gleason

     in reply to

     • :ihavenomouth:
     • Sexy Moon
     • Rusty Crab
     @Inginsub @RustyCrab @Moon Oh. So it's a frontend issue? It doesn't fetch /api/v1/statuses/:id/context when it should. But the server has the info.
   • Embed this notice
     Rusty Crab (rustycrab@clubcyberia.co)'s status on Tuesday, 10-Oct-2023 00:15:22 JST Rusty Crab

     in reply to

     • Sexy Moon
     @alex @Moon I will do that the next time I'm at my PC
     Alex Gleason likes this.