#social 2018-01-16
2018-01-16 UTC
rowan, mib_mbeteo, xmpp-social, Loqi, KevinMarks, JanKusanagi, jankusanagi_, jankusanagi__, KjetilK, KevinMarks_ and cdchapman joined the channel
pfrazee joined the channel
# taravancil hi! pfrazee will be joining here soon
# pfrazee o/
# saranix when is meeting?
# Loqi [@dustyweb] Dat / Beaker looking at exploring ActivityStreams: https://github.com/beakerbrowser/beaker/issues/820 Really excited about this!
# saranix thx
# pfrazee cwebber2: :) appreciate it
# pfrazee cwebber2: too busy this week but appreciate the offer
# pfrazee cwebber2: we'll be in SF the last week of the month, so we may be traveling. But even better, if anybody here lives in SF, maybe we can meet for drinks or coffee
cdchapman joined the channel
# pfrazee cwebber2: too bad! Well if you're ever in austin :)
rowan and KevinMarks joined the channel
JanKusanagi joined the channel
# pfrazee cwebber2: yeah tara and I are constrained on travel budgets but if we can make it, we'd be very happy to be there
# pfrazee cwebber2: Im looking at activitypub's spec and thinking about how a dat app could leverage it. One of the interesting differences is about how objects are created. My read of the spec so far is that clients affect changes by sending activities to servers, and those activities wrap objects. In the dat ecosystem, we have a shared FS of json objects, so you could think of it kind of like an object store that's exposed directly to the client app
cdchapman joined the channel
# pfrazee cwebber2: my natural inclination would be, instead of using activities, we'd just write the object records and assemble the feeds from them
# pfrazee cwebber2: but I suppose the other option would be to write the object records, and then also write activities as .json files which reference the object .json files
# pfrazee cwebber2: right, sensible for the federated server design
# pfrazee right
# pfrazee cwebber2: right there'd probably be no need for update or delete. I'll keep reading and mention thoughts as they come to me
# pfrazee cwebber2: the inbox/outbox differs. In a way, every dat is an outbox, and the inbox is assembled by syncing the followed outboxes.
# pfrazee if I were to try to build a reliable mail system on top of Dat, one element I'd include is a federated server layer which helps the client discover mail from users that they don't follow. That server could discover the mail by crawling the dat network like a search-engine spider, or it could use a server-to-server signal like activitypub does. (I hope that's illustrative of how dat works.)
KjetilK joined the channel
Eugene, JanKusanagi, KevinMarks, cdchapman, KevinMarks_ and rowan joined the channel