how can anything be verifyed?
You put a green checkmark emoji at the end of your display name. There, you're verified.
ActivityPub: decentralized social networking protocol
71–80 of 140 posts
Re: ActivityPub: decentralized social networking protocol
#72Earlier quoted context omitted.
> which meant some clients may not honor the private status of theses posts. Does this mean they may have accidentally published a message intended as private, to the public? If so, I don’t think I can imagine a more efficient way to rob me of any confidence I ever had in Mastodon…
Socal media is orthogonal to privacy. If you want to keep something private, don't post it on a social media platform -- or at least, encrypt it out of band before you do.
I think you meant antisymmetric. Orthogonal means "irrelevant to".
But it's like saying that publishing is opposite to privacy. Yeah... It is so by design and definition.
Re: ActivityPub: decentralized social networking protocol
#73Earlier quoted context omitted.
In AP, messages are signed with http signatures ( https://tools.ietf.org/html/draft-cavage-http-signatures-09 ). OStatus has a similar mechanism called salmons, which are signed XML payloads.
server-to-server signatures are a good start, but what about encrypting messages end-to-end? I assume the servers already talk over HTTPS.
it's really not worth it. If people want to exchange encrypted messages, they should use a proper tool for that.
Re: ActivityPub: decentralized social networking protocol
#74From my quick read of the spec, server-to-server federation assumes that servers can be trusted. That need not be the case; unless a message is signed it should not be assumed to have come from a specific user. I don't know if there's an easy way to share keys in a decentralized way, but that'd be an interesting problem to solve (some blockchain maybe). The other question is whether we want server-to-server federatio…
> I don't know if there's an easy way to share keys in a decentralized way, but that'd be an interesting problem to solve (some blockchain maybe). This is exactly what namecoin tried to solve. Buy an identifier, put whatever you want in it. Example: https://nameid.org/?name=rakoo > The other question is whether we want server-to-server federation at all instead of a P2P network like bittorrent. We want something in b…
The scuttlebot link mentions append-only. Does this include the possibility of appending a "delete" or "edit" message?
Re: ActivityPub: decentralized social networking protocol
#75Earlier quoted context omitted.
Scuttlebut is, so far, the most interesting decentralized social media tool I've seen. Even Mastodon and Matrix still require a server of some form, while SSB will continue to work offline and via truly local peer to peer connections. The only issue is client support and the fact that I don't have a good sense of the state of development/stability/soundness for SSB. If you (or anyone) has experience actually using SS…
SSB is rock-solid in that the community encourages the use of diverse client and server implementations rather than having a monolithic interface that's meant to do everything. On the other hand, the underlying libraries are opinionated in that they usually use depject and a handful of other tools/techniques that aren't super familiar to those outside the SSB community, which makes it harder to write brand new client…
> ssb webclient
https://github.com/ssbc/patchfoo
you do need to host your `sbot` somewhere tho
Re: ActivityPub: decentralized social networking protocol
#76Does anyone have a reference to all the expected/discussed use-cases? https://github.com/jasnell/activitystrea.ms/blob/master/READ... shows a number of activity types.
Re: ActivityPub: decentralized social networking protocol
#77Earlier quoted context omitted.
server-to-server signatures are a good start, but what about encrypting messages end-to-end? I assume the servers already talk over HTTPS.
it's really not worth it. If people want to exchange encrypted messages, they should use a proper tool for that.
Please don't say that. We already had such pain from HTTP, FTP, and SMTP not starting with it.
If building the next version of internet discussion and sharing, we really need first-class support for encryption.
Re: ActivityPub: decentralized social networking protocol
#78Does anyone have a reference to all the expected/discussed use-cases? https://github.com/jasnell/activitystrea.ms/blob/master/READ... shows a number of activity types.
Re: ActivityPub: decentralized social networking protocol
#79Earlier quoted context omitted.
In AP, messages are signed with http signatures ( https://tools.ietf.org/html/draft-cavage-http-signatures-09 ). OStatus has a similar mechanism called salmons, which are signed XML payloads.
server-to-server signatures are a good start, but what about encrypting messages end-to-end? I assume the servers already talk over HTTPS.
Hello! Co-editor of ActivityPub here. I wrote a paper for Rebooting Web of Trust on how this could be done: https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust...
Re: ActivityPub: decentralized social networking protocol
#80Earlier quoted context omitted.
it's really not worth it. If people want to exchange encrypted messages, they should use a proper tool for that.
Please don't say that. We already had such pain from HTTP, FTP, and SMTP not starting with it. If building the next version of internet discussion and sharing, we really need first-class support for encryption.
no, we really don't. Not every tool needs to be equipped for private discussions. ActivityPub and OStatus are used for Twitter-style communication. Those aren't high security communication services.