#social 2017-07-06

2017-07-06 UTC
#
@hvdsomp
@Lambo Taking back control of one's social data can also be achieved using HTTP-based social web standards, see https://www.w3.org/TR/social-web-protocols/
(twitter.com/_/status/882721597261582336)
tantek, prtksxna, xmpp-social and ben_thatmustbeme joined the channel
#
cwebber2
heya puckipedia, around?
#
cwebber2
wanna pick your brain for a second about how you're doing some things and see how it aligns with what I'm doing
#
cwebber2
specifically around ACL stuff.
#
cwebber2
it's not protocol stuff, just implementation decisions.
#
puckipedia
cwebber2: should be possible right now
#
cwebber2
puckipedia: heya!
#
cwebber2
puckipedia: so what's your route for storing ACL stuff on more... I dunno what to call it... "core" objects, specifically Actors
#
cwebber2
I know you keep an is_public type boolean on things
#
cwebber2
do you just set that to True for all actors?
#
cwebber2
and keep such lists?
#
cwebber2
or are they dynamically generated and you don't bother
#
cwebber2
also what ACL lists do you use? right now (embarassingly) I just use actor/attributedTo and the addressing, but I have a branch that stores actual db lists
#
puckipedia
currently I don't have any special ACL data.
#
puckipedia
the is_public is set on the connection between an object and a collection, and it's just for optimization
#
puckipedia
and currently I also only use actor/attributedTo and addressing
#
cwebber2
well, at least I know I'm not alone ;)
#
cwebber2
the branch isn't finished, and I've been debating whether or not to merge it
#
puckipedia
actors and such get an exception to that (also, iirc, viewing a collection attributedTo you)
#
cwebber2
puckipedia: cool, thanks for the notes-compare :)
#
puckipedia
I need to kinda think about that, if someone posts an object into your inbox where you're mentioned in a collection, should I reprocess the ACL if the receiving actor gets removed from the group
Loqi_ and tantek joined the channel