Live data from Hacker News

ActivityPub: a federated social web standard

w3.org

51–57 of 57 posts

Re: ActivityPub: a federated social web standard

#51
post #24

Small section about how Spam should be handled somehow by a server. Sigh. How about we build a federated spam/harassment prevention system first? I have little hope that a spec not designed to reduce/stop harassment up front can have it bolted on later successfully.

https://indieweb.org/Vouch (for Webmention, which is a much simpler spec, already a W3C Recommendation, and deserves more hype)

Vouch is a pretty clever scheme — as the sender, you include a link to someone who linked to you, who the receiver also linked to. So your server can detect, essentially, "randos" — unknown sites that might be spam, harassment, or good replies from someone who found your site accidentally.

I haven't yet implemented Vouch in my server software https://github.com/myfreeweb/sweetroll but my idea is to eventually have a settings switch that determines what to do with mentions from randos — reject, require pre-moderation or accept. Depending on your situation you'll be able to change it — e.g. set it to pre-moderation when some spam appears, or set to reject when a harassment campaign attacks you.

Re: ActivityPub: a federated social web standard

#52

This is neat stuff. I see immediately how it interacts with things like Mastodon and MediaGoblin. I'd like to see how it could be made to interact with IndieWeb stuff. Particularly, how minimal could you make an ActivityPub server and still have it federate with the things you want it to federate with?

Hopefully someone will make a brid.gy type thing that would just convert ActivityPub server-to-server notifications to Webmentions…

Re: ActivityPub: a federated social web standard

#53

The standard is awesome and looks well-designed. The biggest issue is that it was lead solely by the people around Mastodon/Pump.io/Mediagoblin. While not a bad thing per se (on the contrary, it shows a commitment to a free internet), it means that there is little chance for it to penetrate the general (social) networking scene (Facebook, LinkedIn, Twitter, VK etc.). Did you try reaching out to each of those major so…

While, I'm W3C staff contact for the working group now, I wasn't involved as staff when the group started, so I'm not sure exactly what happened. By W3C practice, ever member organization is consulted on every new thing we do, though, so Facebook, Google, Twitter, etc were informed and asked for input and invited to participate. The public is also informed, although I don't know how much people pay attention to W3C news, and the framing might not have caught the right people's attention: https://www.w3.org/blog/news/archives/3958. I still have a hard time understanding what that announcement is talking about.

In any case, as other people have said, perhaps these companies didn't see the business case to participate. This baffles me a little. I can see why as the market leader Facebook wouldn't necessarily benefit financially from helping the effort, but if I were them, I'd want to at least have someone in the room, paying attention. And if I were anyone else, I'd probably see the value in teaming up and helping. But that's not what happened, so I'm clearly wrong about something. It's possible they just thought the problem was too hard and the group would never succeed, so it wasn't worth paying it any attention. My sense is it's done well enough that with more help it might have done great. But it was touch and go at many points, and I personally thought it would go nowhere until our Paris meeting, about 8 months in. It's also possible they just didn't have anyone senior enough to handle the job who had any desire to do it.

And yes, OpenSocial were one of the big motivators for this work starting at W3C (as the news announcement says). But, aside from IBM, they never actually showed up in the group. Someday, I'd like to understand that, too.

Re: ActivityPub: a federated social web standard

#54
"They just want to be in control of their data"

sure .. but that's not a problem massive centralised services can solve.

If you put your data on someone else's computer then who REALLY has control of it?

whom you trust is of course your choice and theres no "one size fits all" re any of it.

re: opensocial

That wasn't about federation.

the scope of it was closer to webapps.

remember Google Gadgets? it was pretty much based on and extending that.

btw I think from memory Myspace was part of that group and implemented some parts of the opensocial spec.

I don't remember Facebook being involved with Opensocial.

Re: ActivityPub: a federated social web standard

#55
post #35
post #7

I really like the idea of a social web standard. This seems like a very constricting protocol, though: the one-to-one correspondence between a user and a server means I need to individually post my activity to the "inbox" of everyone who wants to read it (or they poll my "outbox" - I'm not sure). Not a recipe for an efficient system. It's called ActivityPub, so this was clearly a design decision to meet the goal of b…

Have a look at the related w3c spec WebSub that is designed to deal with this issue: https://www.w3.org/TR/websub/

WebSub literally does the same thing, except ActivityPub cuts away the middle layers, removing some redundancy on the way. It makes ActivityPub less of a protocol hodge-podge than OStatus, which has the same drawbacks and benefits as any introduction of a dependency into a protocol or software.

Re: ActivityPub: a federated social web standard

#56
post #42

The BuddyCloud [0] project also came up with a standard proposal. Is this related to that work ? [0] https://github.com/buddycloud/buddycloud-xep

Not at all. ActivityPub comes from pump.io, which was based on the experiences with OStatus.

BuddyCloud is a parallel track to OStatus, possibly inspired by the OStatus predecessor OpenMicroBlogging, but I don't know that. Both tracks came about around the same time a decade ago.

Re: ActivityPub: a federated social web standard

#57
post #14

ActivityPub is awesome, and I'm excited that it's reached this stage. Looking forward to the core Known platform supporting it.

In general, it would be interesting to see to what degree people manage to build bridges between the IndieWeb and the ActivityPub web.

MicroPub and ActivityPub grew out of the same working group, because the two camps couldn't find shared ground.

I don't know if they managed to get a decent mapping between ActivityStreams2 and Microformats2 at least.

Post reply on HN