jaywink[m]trwnh (IRC): sure, though I find it difficult to understand how "public" could mean "followers only" so yeah definitely there should be a way for for example mastodon to define this without having to abuse `as:public` - since by no definition of the world can public mean "only a defined list of public". Every definition of "public" in for example https://en.wiktionary.org/wiki/public indicates not limited to a group of people but open to an unknown
trwnhi didn't say public = followers-only. i said that there should be levels between the two. consider "logged-in users only", or "password protected", or "friend-of-a-friend"
jaywink[m]if you share content with an unknown number of people then one cannot realistically be disappointed if a random person you don't like sees it or a search engine indexes it
jaywink[m]I remember we had this discussion in diaspora years ago and attempts to introduce a "logged in" visibility was rejected due to the simple fact that the software cannot make any guarantees for you - it gives a false promise of privacy. but I also understand people might want that (and actually have the same visibility in socialhome, my own software ;))
jaywink[m]I definitely agree to your earlier comment re visibility field, just pointing out my opinion of guarantees of "unknown number of people" visibility and the problems it will inevitably also introduce
trwnhreally, i think the fundamental issue here is that once the data leaves your server, it's effectively a question of trust in whether the other system will respect your rules
trwnhit would also be easier to do access control if you moved from a push model to a pull model, but that's not a direction i think most people want to go bc of the centralization dynamic it introduces
rialtate[m]The idea that any software system could keep something perfectly private under any conditions is completely nonsense. And users will always be a weak link. You can't stop leaking of a token? Well netflix can't stop people from sharing passwords to their entire account. There is no such thing as security, only trust, and that will always be in the hands of some human somewhere along the lines.
jaywink[m]that probably works for non-public (in every sense limited and known who shared with) content, but as soon as something is shared with an unknown number of people it becomes a matter of "I'll tell you my rules, please respect them"
vitalyster and xmpp-social joined the channel; vitalyster left the channel
fr33domloverthe AP spec says 'followers' is for actors; what if I want to follow something that isn't an actor? What should I name the 'followers' collection?
fr33domloverjaywink[m], well I'm listing that collection under the non actor object, e.g. an issue or merge request may have a followers collection. I'd love to just use the 'followers' property because this is what it's for, subscribing to updates etc., and since there's no Actor type I imagine the RDF domain of 'followers' has to be 'Object', BUT the AP spec says: 'followers' is a collection of actors following
fr33domlovercjslep[m], I already checked that stream stuff and decided it's a weird unspecified thing and there's no benefit using an object inside an object, and I'd need to choose a property either way