Gregory's Server@markearnest Even if Meta’s ActivityPub host is not allowed access there will be ways to access nearly all of the posts because most are public and there is no encryption on private posts. Privacy will be a concern that must be handled by the ActivityPub protocols as it evolves. @paul
|
5 comments
 @markearnest Given that servers hold everything in a database which admins can access everything there really is an opportunity to sell that data. We share these posts publicly, so there is no expectation that it won’t be used. It is easy to link my data together via LinkedIn, GitHub, Linktree, etc. It is fairly easy to build a profile and target users. ActivityPub is not a place for privacy. @brennansv fair point, but I see no reason why I should make it any easier for Meta. I’m assuming they will be a bad actor on the fediverse based on how they behave everywhere else. @markearnest We have to keep it open which prevents Meta from taking it over. This is like how Jeffrey Zeldman and others fought for web standards years ago to ensure no browser or company could own the web. Fortunately ActivityPub is a W3C standard already. The sudden interest in #Fediverse apps is going to reveal concerns (scaling, privacy) that must be handled. I am sure the community will come together to work on it all. @markearnest Fortunately there are now decades of work that can be used as a great reference from DNS to SMTP to HTTP/2. Many of these problems have already been solved so the solutions are there to be found. From what I have learned so far ActivityPub has been doing this already. |
@brennansv very true.