@trwnh@darius I think personally I lean towards a pure firehose model. Send me everything you got and let my clients pull out the data they're interested in
In part because we're unlikely to ever agree on one exact axis of filtering
@trwnh@darius I actually think this demonstrates a fundamental flaw in the email model
There are times you want to be able to do endpoint to endpoint but potentially automatic message exchanges, and email doesn't really have a mechanism for doing this
The straightforward example is my client noticing your S/MIME or GPG key is expiring and asking if there's a new one
Things just work much better in many ways if activities can be thought of as largely ephemeral.
If the podcast listen is important enough that it's worthwhile keeping around in my feed - say, it has commentary or something like that - then perhaps it's better framed as commentary, not as a pure listen
@trwnh@julian@mike@hongminhee@thisismissem@pfefferle@michael@renchap we don't really have a way of knowing what activities our followers are interested. In fact in the general case that's impossible; if I started using a music suggestion system based upon my friends listening habits today, I'd like to be able to use their historic listening data that they have been broadcasting to seed it.
Alternatively, consider that I decide to make my listening history public and it hits a relay. My as:Listen activities are going to absolutely carpet bomb the federated timeline.
Aside from the Annointed Two (Create, Announce) we really need to treat most activities as ephemeral and largely unimportant
Imagine I used a federated last.fm like application. If Mastodon converted as:Listen to a note, my followers would probably get pissed off about the "Now listening to: X" statuses every 2 minutes
To be fair, if I were selecting which university to go to - either today or back when I was a student making said selection - “Will let me operate their nuclear reactor” would be a ranking criterion which would catapult any university to the top of my list
Reed’s licensed reactor operators are also unique in that men are a minority. On my visit, Reed students boasted that their reactor operators include more women, and more gender non-conforming people, than at all other research reactors in the US combined. Thanks to Reed’s reactor operators, the Nuclear Regulatory Commission (NRC) no longer questions anyone who wants to change their names from one gender to another on their licences.
@helge If the replies collection’s items were always inlined (or were always inlined when low enough in number, at least), it would be N fetches for N posts which is not too unreasonable.
The Threadiverse people (Discourse, NodeBB, Lemmy?, MBin?) are also coalescing around the idea of a context collection which contains every post in the entire (logical) thread
@helge Akkoma and Pleroma already internally maintain the same idea of a context so I have plans to implement an MR which reifies it at a fetchable URL.
immigrant | they/them | software engineer in card paymentsliker of ISO 8583, the 8051, ASN.1 and EBCDIC.I wrote the ActivityPub initial draft, so this social network is in some way my fault.Formerly @erincandescent@queer.af Instance admin, queer.af (2018-07 - 2024-02, RIP)