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

@evan the only point i'm trying to make here is that a Create is a "notification that someone created something", not a "notification that someone replied". if you have something which is both a reply and a quote and who knows what else, then you are overloading the Create with highly specific introspection and possibly complex boolean logic (Create AND object.inReplyTo NOT (object.tag[*] is Link AND Link.rel = _misskey_quote))

a simple match on the top-level type array could suffice!

@evan it's a genuine question, which you may ignore.

@evan evan, not only did i read your book, i also reviewed it for o'reilly at your request. the topic at hand is about reply notifications and reply acknowledgements, two things which are not specified in the activitypub TR. we have Like+likes and Announce+shares, and to some extent we have Follow+followers, but everything else is left as an afterthought perhaps stuffed in a Create. i'm very confused what this kind of response is supposed to mean.

by "AP" here i mean the Follow/Like/Announce bits and how they affect the followers/likes/shares collections. since that's the only part that has any sort of consistency

even then, i do kind of think that WebSub was/is/remains better for handling subscriptions. also they should have kept calling it pubsubhubbub

rather unfortunate that AP didn't leave any protocol signaling mechanisms for itself, so "upgrading" to a different/future version of AP is kinda fraught, since there is no concept or awareness of multiple protocols potentially using the same vocabulary

@evan

1. how do you notify someone that you've replied to them?

2. how do you manage side effects?

activitypub should have defined a `Reply` activity and the `replies` collection should have contained these activities

hot take but a real “social web” should let you interact with any resource on the web, not just a strict and limited subset of things that can be considered “fedi posts associated with fedi accounts”

@julian @johnonolan @angus @evan 301/308 are meant to permanently update old identifiers regardless of request headers. consider 303 See Other for content negotiation purposes, or consider rel=alternate type=… Link headers otherwise.

@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