Seems like birdsite is gearing up to #embrace #extend & #extinguish the fediverse: https://mobile.twitter.com/jack/status/1204766078468911106
@rra jack's hug of death
Complete tangent but I'm reminded of this great article on Wolfram vs the iPython notebook that you might enjoy. Contrasts the "maniac in the middle" Wolfram to the open source iPython team.
@rra I raised the question last year at fosdem during activity pub roundtable. And I felt it was not taken seriously, indded it seems people feel that if proprietary platforms started decentralising, it could benefit other people then them...
@natacha It it is a really big threat indeed. If there is no work done preventing the capture of the distributed fediverse social graph (like what was proposed re ocaps etc after GAB joined) the network will be taken over and made harmless. The sad thing is that I see many people here not feeling threatened but rather the opposite, feeling flattered and curious like it is 2011 again.
This is probably good publicity for the #Fediverse. By the time they burn all the cash they got for this "new protocol" on endless discussions whether they should implement smart contracts on top of it or not, there will be enough articles on ActivityPub and Federation for the masses.
@xuv @320x200 It is not about invention but about implementation and public opinion first of all. Building good will. If anything, this will work to remove building regulatory pressure and deflect existing and potent efforts to make a proper alternative.
Essentially what I think they will do is buy talent and keep them with busy on something that is set up to fail.
There are several suggestions from European politicians to force the big platforms to use open interoperable standards so this may just be eyewash to say "Please don't regulate! We are working on it."
I have a colleague who points out that \@jack, in his tweet, actually talks about doing this for his customers, meaning the people trying to target an audience, advertisers and alikes. And for that reason, ActivityPub is not the answer.
That's the thing though, it's going to be a failed attempt from a consumer point of view. It's likely to be quite effective in the following points:
1) deflect currently mounting regulatory pressure
2) distract / buy out / exaust development labour that is out of their control (you can see already there are some fediverse devs that are excited at the possibility to become part of this and use #activityPub for it... and for good reason, perhaps they finally get paid and recognized for their work?)
3) get access to the steadily growing decentralized social graph. As per recent facebook leak: '"The number one threat to Facebook is not another scale social network, it is the fracturing of information / death by a thousand small vertical apps which are loosely integrated together,'
Do note that this social graph is completely open to capture at the moment. Blocking e.t.c. is mostly a cosmetic feature aimed at protecting users from seeing content.
Addressing the issue of protecting the social graph could be a common motivation, probably it should be addressed by activity pub developers https://socialhub.network/
@natacha @rra @KnowPresent @320x200 correct me if I'm wrong, but the social graph being in the open is not necessarly AP's fault. It's how different programs implement AP that they make it more open than others. Do I understand this correctly? The social graph, afaik, is not transmitted entirely in one AP package, nor provided upon request. It's deducted through capturing complete history of communications. Right?
Addressing the issue of protecting the social graph could be a common motivation, probably it should be addressed by activity pub developers https://socialhub.activitypub.rocks/
Welcome to post.lurk.org, an instance for discussions around cultural freedom, experimental, new media art, net and computational culture, and things like that.