News for hackers. Stuff that matters.
Re:Creating your own federated microblog by rglullis on Thursday April 24, 2025 @09:55AM (#43782877)
> if I'm writing to a blog or a microblog I just don't really care who follows me or even who reads it.

- if you want to have comments or backtracks, you can do it with ActivityPub without having people signing up to your site (directly or through some OAuth system)

- If you want to mitigate spam, you can set up your AP blog to only accept messages on the inbox from actors who you whitelist.

- You could have your own Substack where you only send the updates to actors who are paying subscribers.

Re:Creating your own federated microblog by _heimdall on Thursday April 24, 2025 @10:17AM (#43783111)
The OP here specifically wasn't including any auth features, which I was pretty sure would mean backtracks and comments aren't supported but maybe that's wring. It is possible with ActivityPub, but I'd personally be hesitant to run my own OAuth server just for a microblog.

Regardless, my underlying point really is about what I expect of a microblog. If I'm hosting it myself I just want it to be my little corner of the internet, not a full fledged social media site that I have to maintain. That doesn't mean I'm right or that others don't expect more.

Re:Creating your own federated microblog by rglullis on Thursday April 24, 2025 @10:44AM (#43783450)
> If I'm hosting it myself I just want it to be my little corner of the internet, not a full fledged social media site that I have to maintain.

I think the problem is that OP is focused on developing a framework for AP, and he is dogfooding it by developing an application that other people can understand without too many new concepts.

This is good if you want people to get experiments, but it is terrible as a way to present the true potential of the protocol: https://cosocial.ca/@evan/113143389340566731

Re:Creating your own federated microblog by apitman on Thursday April 24, 2025 @01:18PM (#43785134)
> if you want to have comments or backtracks, you can do it with ActivityPub without having people signing up to your site (directly or through some OAuth system)

You can do the same thing with RSS+We mention, which is a way simpler stack and predates ActivityPub by years

Re:Creating your own federated microblog by rglullis on Thursday April 24, 2025 @01:50PM (#43785501)
Webmentions are a spammer's wet dream. There is a reason they were adopted only by the Indieweb crowd.

Anyway, my point was less "ActivityPub can do everything people can do with RSS" and more "having a mechanism to for bidirectional authenticated messages opens up the possibility of new applications".

The real interesting part will happen when/if more developers realize that ActivityPub can do more than "federated versions of popular social media platforms".

Re:Creating your own federated microblog by apitman on Thursday April 24, 2025 @02:20PM (#43785818)
I might be misunderstanding what you're saying here. How is ActivityPub more authenticated than Webmention? WM requires the poster to host their content on a website. This is exactly what the AP spec says to do. Now, since the spec was published, most AP implementations also support HTTP signatures[0], but this doesn't provide additional guarantees that you can't get with WM. The authentication is still tied to a URL.

As far as spamming goes, I don't see how WM is any worse than AP. In both protocols your only options are passlists and/or blocklists.

[0]: And an old version that doesn't have an official spec. ActivityPub's issues with spec stagnation and de facto standards is a whole other thing.

Re:Creating your own federated microblog by johnmaguire on Thursday April 24, 2025 @02:42PM (#43786034)
I haven't dug into these, so apologies for the naive question, but for a multi-tenant service like WordPress.com, can you effectively limit which WordPress blogs can WebMention you? If the allowlist is formed on the domain, this seems limiting.

Perhaps more advanced URL regex can achieve more fine-grained control but I do still see advantages in pubkey auth (especially if people want to move their content.)

Still, I do find myself wishing for a lighterweight-than-ActivityPub middleground.

Re:Creating your own federated microblog by apitman on Thursday April 24, 2025 @03:00PM (#43786209)
You're right, in default configurations ActivityPub definitely has an advantage here, since HTTPsigs are tied to users, not instances, which gives finer grained blocking. I'm not aware of anything like this for Webmention.

I suspect this is because WM is used far less than AP. It also grew out of a community (IndieWeb) where having your own domain is a core tenet.

I think something like Mastodon could work with WM though, since all URLs hang off of user URLs, so you could block by URL prefix, ie "block https://example.com/user1/*".

Re:Creating your own federated microblog by freosam on Thursday April 24, 2025 @09:08PM (#43789239)
Webmention receivers can filter on whatever parts of a URL they want to. Maybe a WordPress implementation limits this to the domain? But as far as the spec goes, the receiver just gets a `source` parameter that's a URL. They can then decide to allow that (based on the domain, or any other characteristic they want) and at that point they check that URL to see if the document there contains the link that it's supposed to.
Re:Creating your own federated microblog by freosam on Thursday April 24, 2025 @09:13PM (#43789261)
Spammers would have to host a page (permanently) that links to your post, and even then they don't get to control what (if anything) from that page gets displayed on your site.

I guess one danger is that they only serve the page that contains your link to the webmention-validating request. That way they get a backlink but don't have to keep a public outgoing link. They'd have to know that a given request is that validation though, and I'm not sure that'd be very easy.