T
@AuntyRed @ouguoc @dynomight yeah it's more like bsky tech is centralized but mastodon tech is neutral/unaligned. the latter allows social resistance to rugpulls but doesn't guarantee it. the former locks you in without being able to do anything about it outside of building entirely separate architecture
with mailing, usps, fedex, ups will all deliver to an address. and you pick a house/apt/etc to live. but if the only mega-stadium in your area shuts down, then where do you go for huge events?
@utsuho he will be baked soon alhamdulillah
@codl this is the oldest one i can think of
road work ahead? i sure hope it does
based? based on what?
apartment complex? i find it quite simple
the bird flu? yeah they tend to do that
you’re telling me a ginger bred this man?
chefs kiss? do they really?
wood fired pizza? how’s pizza gonna get a job now
@ouguoc @dynomight notably you can run your own email but you cant easily run your own google. and it’s a lot less useful even if you manage to do it
@ouguoc @dynomight basically the mastodon tech is like email (move from hotmail to gmail, you can still talk to people because there is a standard for sending messages), but the bluesky tech is more like google (the websites exist independently but all the discovery/searchability happens in one service that can easily go to shit)
@ouguoc @dynomight both? technologically there is no single point that everything must flow through. socially there is a current to ensure this by encouraging people to run their own servers. a mastodon rugpull would be harder to do because mastodon isn’t the only software in this space. if mastodon did something unpopular, it’s possible that people would just move to something else that still let you talk to the same people. bluesky on the other hand is only one service that fetches/sorts data.
@helge people have inherently conflicting ideas which can never be reconciled, and different social expectations which also conflict. i don't think a singular "Public" is possible or even desirable to define.
the first step needs to be identifying and describing what you call desires. ODRL maps out what they call "rights". i suspect this is a question people don't even want to engage with meaningfully, though... the prevailing current seems to be assuming one's personal norms apply to everyone.
@checkervest your timeline has officially been deemed Too Slow by the codebase
(i'm not kidding this is how it works)
@codl "all i know is that i know nothing"
@scott AS2 didn't define a Hashtag type and also literally yes it's not for that, it's for the concept of a "tag". like if you tag an Image with a Person you are implying the Image contains the Person, and you can reverse query for all objects with a `tag` of that Person. they're basically categories. this is in the definition
- context isnt just collections, it's basically a supertag that lets you group things that belong together, the other half of scoping (next to audience)
- tags are literally "related to" taxonomical references so this shouldn't be mismatched at all
- threads aren't necessarily trees with a top or root, they may be a chronologically sorted ordered set
- names have multiple interpretations and connotations, this is ideally why we use URIs not basic string terms. as2-vocab has definitions.
@scott use `tag` for that
@saxnot i don't see why it has to be either/or -- it depends on which direction you're approaching it from
either you ask an authority for "every post in the thread (flat list or set)", and then you can say sort that set by time if not already sorted... and replies are just metadata within that thread (a la slack/discord/element)
or you try to construct the graph of replies independently of anyone's authority, with each resource being self-sufficient
sometimes you care about authority!
man, email threading is a mess... https://www.jwz.org/doc/threading.html
@scott you might reuse *some* terms from AS2 but there's no need to overdo it. use different terms from different vocabs as appropriate. if an AS2 term isn't a perfect fit for a concept, don't try to force it in.
@scott i imagine in the case that you're describing, a Task might have a `context` of a Project, but if you want to say that some Conversation is "related to" the Task, you would use something like `tag` instead? it doesn't make much sense to claim that an Article exists in context of a Task...
the other thing i have to ask is why even bother using AS2 for something that clearly isn't related to the AS2 content model of Note, Article, and Document? i'd consider using a different vocab entirely.
@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
@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...
@usagi i think theyve been steadily made less useful due to security issues and poor UX