Conversation

Notices

:blank: (i@declin.eu)'s status on Friday, 02-Aug-2024 03:48:21 JST :blank:
@hj @feld @lain @takao without it, followbot MRF would become essential again

since the only alternative to receive posts not send by a follow, is scrapping user outboxes

feld would turn this instance straight back to the dark ages of ostatus if i don't want to maintain a personal follow list

In conversation about 4 months ago from declin.eu permalink
- likes this.
- (mint@ryona.agency)'s status on Friday, 02-Aug-2024 03:51:15 JST
  in reply to
  @feld @i @lain @hj @takao I'd bet a good half of those are empty accounts from Mastodon instances spamming deletes. Either way, removing relays would leave us only with people we personally subscribe to and whatever gets fetched as part of the context.
  
  In conversation about 4 months ago permalink
- feld (feld@bikeshed.party)'s status on Friday, 02-Aug-2024 03:51:16 JST feld
  in reply to
  @i @lain @hj @takao I have literally like 400,000 accounts on my server which are posts from users who nobody on my server follows. You don't need to follow people directly to receive their posts on your instance.
  
  In conversation about 4 months ago permalink
- feld (feld@bikeshed.party)'s status on Friday, 02-Aug-2024 03:52:11 JST feld
  in reply to
  @hj @i @lain @takao I believe Mastodon is currently just delivering public posts to every server it has federated with instead of targeting only the inboxes of servers on which the followers reside.
  
  Pleroma only delivers to relevant servers. Perhaps we should just change that? Then all you have to do is like authorized_fetch of one post on a server and you'll start getting all their public posts too
  
  I mean how else am I getting these posts?
  
  In conversation about 4 months ago permalink
- (mint@ryona.agency)'s status on Friday, 02-Aug-2024 03:52:11 JST
  in reply to
  @feld @i @lain @hj @takao >I believe Mastodon is currently just delivering public posts to every server it has federated
  It sure doesn't, otherwise TWKN would be unusable on every single instance that doesn't block its useragent.
  
  In conversation about 4 months ago permalink
- Proud owner of a potato sack :flag: (hj@shigusegubu.club)'s status on Friday, 02-Aug-2024 03:52:13 JST Proud owner of a potato sack :flag:
  in reply to
  @feld @i @lain @takao i can see one very good usecase is when you're part of "community" i.e. SPC, and browse local timeline a lot but then decide to make your own instance. I used to have a post-it note that when we'll have grööps we should make automatic "instance" group a-la @everyone :DDD
  
  In conversation about 4 months ago permalink
- (mint@ryona.agency)'s status on Friday, 02-Aug-2024 03:54:27 JST
  in reply to
  @i @feld @lain @hj @takao Lotta people that's been involved in early-day instances now treat fedi as a friends-only chatroom. Après nous, le déluge.
  
  In conversation about 4 months ago permalink
- (mint@ryona.agency)'s status on Friday, 02-Aug-2024 03:56:03 JST
  in reply to
  @feld @i @lain @hj @takao Check the logs, unless those posts are part of the thread context, someone might've force-added you to some relay, seen that happen a couple times.
  
  In conversation about 4 months ago permalink
- feld (feld@bikeshed.party)'s status on Friday, 02-Aug-2024 03:56:04 JST feld
  in reply to
  @mint @i @lain @hj @takao why am I getting their posts then?
  
  c.im? never heard of it
  
  random user from mastodon.social? What the hell?
  In conversation about 4 months ago permalink
  Attachments
  1. Untitled attachment
    https://media.bikeshed.party/pleroma/cfe6096410a028d65f81a57bafbb918bbf9f5395c9b19da9b95e5d3f3a1f4725.png
  2. Untitled attachment
    https://media.bikeshed.party/pleroma/fa4cdf0558e5154d5f4a6190d06f8fab23cb862629b3569a1fa3bfff90209200.png
- Proud owner of a potato sack :flag: (hj@shigusegubu.club)'s status on Friday, 02-Aug-2024 03:56:49 JST Proud owner of a potato sack :flag:
  in reply to
  @feld @i @lain @mint @takao my guess is that somebody you follow reprööhs post by that user and pleroma fetches the remote post and user
  
  In conversation about 4 months ago permalink
  
  repeated this.
- Angry Sun (sun@shitposter.world)'s status on Friday, 02-Aug-2024 03:57:01 JST Angry Sun
  in reply to
  @hj @feld @i @lain @mint @takao I like how nobody knows how it works including core developers
  
  In conversation about 4 months ago permalink
  
  likes this.
- Angry Sun (sun@shitposter.world)'s status on Friday, 02-Aug-2024 04:01:10 JST Angry Sun
  in reply to
  @feld @i @lain @mint @hj @takao why would pleroma be consuming it if it was sent erroneously
  
  In conversation about 4 months ago permalink
- feld (feld@bikeshed.party)'s status on Friday, 02-Aug-2024 04:01:11 JST feld
  in reply to
  @sun @i @lain @mint @hj @takao well for all we know it's a Mastodon federation bug where they're just federating to too many servers but nobody noticed because at least the posts are being delivered
  
  In conversation about 4 months ago permalink
- (mint@ryona.agency)'s status on Friday, 02-Aug-2024 04:01:38 JST
  in reply to
  @sun @feld @i @lain @hj @takao A post with /activitystreams#Public in `to` gets sent to shared inbox. It might or might not be from someone people on your server follow, there's no way to check that other than iterating over every local subscription which might add quite a bit of latency. And with that, why bother if we're fetching whatever gets referenced by other activities already?
  
  In conversation about 4 months ago permalink
- (mint@ryona.agency)'s status on Friday, 02-Aug-2024 04:07:28 JST
  in reply to
  @sun @feld @hj @i @lain @takao Part of the spec, apparently.
  https://www.w3.org/TR/activitypub/#shared-inbox-delivery
  >Additionally, if an object is addressed to the Public special collection, a server MAY deliver that object to all known sharedInbox endpoints on the network
  I remember chirp.social has been sending repeats from its porn spambot groups to the whole fedi, to the point I had to block it in nginx.
  https://github.com/michaelcpuckett/activity-kit/issues/11
  In conversation about 4 months ago permalink
  Attachments
  1. announcing group messages to the whole fediverse is spammy · Issue #11 · michaelcpuckett/activity-kit
    
    As far as I understand, the groups plugin sends Announces to all known inboxes: https://github.com/michaelcpuckett/activitypub-core/blob/34d57d2d7f89bf48da698116273dc86240f2f088/packages/activitypu...
  2. ActivityPub
    
    The ActivityPub protocol is a decentralized social networking protocol based upon the [ActivityStreams] 2.0 data format. It provides a client to server API for creating, updating and deleting content, as well as a federated server to server API for delivering notifications and content.
- :blank: (i@declin.eu)'s status on Friday, 02-Aug-2024 04:10:11 JST :blank:
  in reply to
  @mint @feld @lain @hj @sun @takao chirp.social is now only 240 a month to lease to own
  In conversation about 4 months ago permalink
  Attachments
  1. Untitled attachment
    https://declin.eu/media/fc37529c531db16444f27b0ed10c031dc6100117e24309ddf6dafb0ab501e605.png
  likes this.
- feld (feld@bikeshed.party)'s status on Friday, 02-Aug-2024 04:11:58 JST feld
  in reply to
  @mint @i @lain @hj @sun @takao so the spec agrees that it's perfectly OK to just blast public posts to every known shared inbox, as I suspected.
  
  In conversation about 4 months ago permalink
  
  likes this.
- (mint@ryona.agency)'s status on Friday, 02-Aug-2024 04:12:41 JST
  in reply to
  @feld @i @lain @hj @sun @takao AP would've been a spam protocol even without that note.
  
  In conversation about 4 months ago permalink
- :blank: (i@declin.eu)'s status on Friday, 02-Aug-2024 04:15:51 JST :blank:
  in reply to
  @mint @feld @lain @hj @sun @takao honestly we would be seeing SMTP levels of spam if the details on how to send an activity weren't a single blogpost from gargron https://blog.joinmastodon.org/2018/07/how-to-make-friends-and-verify-requests/
  In conversation about 4 months ago permalink
  Attachments
  1. No result found on File_thumbnail lookup.
    
    How to make friends and verify requests
    
    from Eugen Rochko
    
    In the previous tutorial we have learned how to send a reply to another ActivityPub server, and we have used mostly static parts to do it. Now it’s time to talk about how to subscribe to other people and receive messages. The inbox Primarily this means having a publicly accessible inbox and validating HTTP signatures. Once that works, everything else is just semantics. Let’s use a Sinatra web server to implement the inbox.
  likes this.

Public

Conversation

Notices

Feeds