Notices by infinite love ⴳ (trwnh@mastodon.social)

@silverpill @julian how is "the entire network built around the idea"? why do you have this idea of an actor that necessarily maps to a user?

from https://www.w3.org/TR/activitypub/#actors we see that:

> ActivityPub does not dictate a specific relationship between "users" and Actors

so why introduce the concept of "observers" and then prevent users from knowing what they are following? Why the avoidance of calling a conversation a Conversation, and why the artificial limitation of not being able to follow one?

@pfefferle @laxla @naturzukunft @linos @evan @johnonolan yeah, that's fine, i think if it's a one-off thing where the preview is only intended to be used by you and only in that singular context as a preview (and nowhere else), then you can leave out the id

@laxla @naturzukunft @linos @pfefferle @evan @johnonolan if you're going to refer to it later, it needs an id.

@pfefferle @evan @johnonolan @linos "null" id is a mistake and should not be explicitly set like that. just leave it out. the only `id` you need is the top-level one.

@cwebber beware olive

@dansup @nopatience the plan is to call them Audiences but yeah

@jbarsant @dansup @PixelFed i think it's possible or even really the meta-default to have them be kept and given a cover -- the expiration is built on top of that. there's definitely room to tweak the design of the feature as well, so it's not like they have to end up exactly like instagram or snapchat.

as far as importing existing ones from instagram, that depends on whether instagram includes them in exported archives, and whether they're in a format that's easily convertible. so maybe not?

oh man out of curiosity i was googling a minecraft server i used to play on back in 2012-2013 and there's like basically zero record of it now because the free gamer forum thing they used at the time has shut down and pivoted to being a web3 gaming nft thing. rip in peace enjin forums

@dansup it's not "for clout", c'mon

@julian @pfefferle there's a few options on what it would ideally be, but it *can* be any Object

1) group by `id`
2) possibly moderated by `attributedTo`
3) should have some collection associated with it somehow, just a flat list of everything included

the jury's out on how best to do #3 because the goal is to eventually be able to Follow a conversation. but https://github.com/w3c/activitypub/issues/486 makes it problematic to try to Follow a Collection directly...

@julian @pfefferle in terms of what kind of Object to use other than a Collection, i would say maybe don't use a Note because this is often not semantically correct. the current WIP idea is to define a `Conversation` entity that has something like a `posts` property. the thinking is that a conversation *has* a collection of posts, not that it *is* a collection of posts. this is the topic of a separate FEP though. nodeBB briefly went ahead and used Conversation before rolling it back as too early

@dansup they can exist in atproto, it's just that the network effects of the bluesky network won't be there. the way atproto works, you have to know to look for the right repos and records. imagine if pixelfed wasn't compatible with mastodon despite both using activitypub. this could be reality if pixelfed didn't use the mastodon protocol for Note objects and instead it used Image objects.

linkedin moment

@dansup 69 is cancer ♋

@finner @darkling @jwz

or, hear me out: you sign up for one account, like email. you can then use whatever apps you want with that same account.

mastodon, pixelfed, etc don't all need to be separate accounts on separate servers. just like we don't need a separate Web for chrome vs firefox -- they let you browse the same Web.

@finner @darkling @jwz it's how the spec was designed lol

there is a Client api to POST activities to an outbox, and your Server delivers those activities to other inboxes

it's not a change in protocol as much as it is a change in philosophy. everyone chose to build monoliths instead

@dansup not what the question was. in your analogy it'd be like if instagram used something other than HTTP when they could have used HTTP

@dansup @jwz those could still be handled with Pixelfed being an AP Client -- say pixelfed.example asks to oauth into activitypub.example, and whatever you would POST to an inbox you would instead POST to your outbox

@jwz ActivityPub C2S is missing a few bits. Rather than fill in the gaps, most fedi devs have decided to rewrite the same delivery-server logic over and over and over and over and over and o

@helge 75% of fedi servers that have ever existed are dead? huh.