News for hackers. Stuff that matters.
Re:Bluesky announces data federation for self hosters by jakebsky on Thursday February 22, 2024 @01:57PM (#39471437)
Hey HN, the engineering team at Bluesky is especially excited to get to this point! We're happy to help answer questions and help anyone trying to run their own PDS host. Things should work pretty well for self-hosters right now, but we're standing by to help if there are any problems.

Technical details and the installer are in the GitHub repo https://github.com/bluesky-social/pds

And we're on Discord available to help: https://discord.com/invite/UWS6FFdhMe

Re:Bluesky announces data federation for self hosters by lolinder on Thursday February 22, 2024 @02:13PM (#39471637)
It would probably be worth clarifying in that repo what the license is for both the code in that repo and the code that it's actually running. It looks like it's just a very thin wrapper around @atproto/pds, which is MIT/Apache 2.0 [0], but the repo you link to has no license.

Edit: now it has one! Thanks!

[0] https://www.npmjs.com/package/@atproto/pds

Re:Bluesky announces data federation for self hosters by jakebsky on Thursday February 22, 2024 @02:17PM (#39471681)
Yup, it's MIT/Apache 2.0. We'll fix that. Thanks for the heads up.
Re:Bluesky announces data federation for self hosters by mholt on Thursday February 22, 2024 @04:11PM (#39473307)
Awesome! Why did you choose Caddy as a proxy for PDS? (Caddy creator here.)
Re:Bluesky announces data federation for self hosters by jakebsky on Thursday February 22, 2024 @04:54PM (#39473825)
Thanks for Caddy, Matt! Some of us on the team have been using Caddy for years, for many of our projects. Because it's so simple, sufficiently high performance, and has lots of nice features.

The on-demand TLS certificates with an "ask" endpoint is especially useful for the PDS use-case. Because there's generally a wildcard DNS name that is used to give each new user a domain handle (@alice.example.com) but we don't want to be vulnerable to a TLS certificate DoS/rate limit situation.

Re:Bluesky announces data federation for self hosters by mholt on Thursday February 22, 2024 @05:13PM (#39474052)
Great reasons -- glad to hear that! Let me know if you encounter any hiccups or have feedback.

Love the fresh federated model btw!

Re:Bluesky announces data federation for self hosters by charcircuit on Thursday February 22, 2024 @05:48PM (#39474419)
Even if it may be simple in some areas, it doesn't handle edge cases such as https://github.com/caddyserver/caddy/issues/1632 in other areas out of the box unlike other server software.
Re:Bluesky announces data federation for self hosters by nyolfen on Thursday February 22, 2024 @08:00PM (#39475543)
you have been repeatedly posting this incredibly niche complaint for years at this point
Re:Bluesky announces data federation for self hosters by charcircuit on Thursday February 22, 2024 @08:23PM (#39475728)
I have only brought this up once before on HN and it was over 2 years ago. Not adopting a new project because it is missing something niche is an extremely common reason why people stick with tried and true, mature software. I do not see anything wrong with pointing out niche issues because to some people these issues are important. Because it's broken out of the box it is allowing people who aren't aware of this problem to continue to setup broken sites. Even caddyserver.com. is broken.
Re:Bluesky announces data federation for self hosters by napkin on Thursday February 22, 2024 @10:25PM (#39476597)
Curious. What is the use case here? I’ve spent tens of thousands of hours of my life on the Internet and a lot of that as a sysadm and I’ve not once heard of people accessing or linking to sites this way.
Re:Bluesky announces data federation for self hosters by charcircuit on Thursday February 22, 2024 @11:14PM (#39476895)
Personally, I just want to properly handle this edge case and it would bother me if my sites didn't handle it correctly. There are advantages for using FQDNs since they are not ambiguous there are extra optimizations that can be done. I don't want my sites to be problematic for people who want to use them so I make sure my sites properly handle them. Usually handling FQDNs is easy as it just works out if the box on most server software.
Re:Bluesky announces data federation for self hosters by napkin on Thursday February 22, 2024 @11:52PM (#39477123)
Can you provide a URL to a page containing a link of this style? I’ll concede that it’s useful to someone if I see it! The term ‘FQDN’ does not always imply the dot at the end?
Re:Bluesky announces data federation for self hosters by charcircuit on Thursday February 22, 2024 @11:59PM (#39477167)
Do you just want a link?

https://news.ycombinator.com./

If you want a link to a page with a link like this you can click on the github issue I referenced in my original comment as there are links there like that.

>Also, the term ‘FQDN’ does not always imply the dot at the end?

Yes, but if there is not a . at the end then there is ambiguity of if it is a FQDN or not.

Re:Bluesky announces data federation for self hosters by kuschku on Thursday February 22, 2024 @09:12PM (#39476090)
Is it possible you're vonfusing that user with me? I used to be relatively vocal about this issue on HN. For reference, that's not me.

And it's probably not niche if dozens of users are posting about it for years.

Re:Bluesky announces data federation for self hosters by nativeit on Thursday February 22, 2024 @06:34PM (#39474855)
Not for nothing, but when accessed from this HN app on an iPhone, Apple’s website with a trailing dot does not render correctly.
Re:Bluesky announces data federation for self hosters by Lutger on Friday February 23, 2024 @04:44AM (#39478742)
That is a bit unfair, as it is intentionally not doing so. You may disagree with it, sure, but as it stands I think your comment implies oversight or immaturity, which is evidently not the case reading the discussion on the issue you linked.
Re:Bluesky announces data federation for self hosters by charcircuit on Friday February 23, 2024 @02:08PM (#39484846)
>That is a bit unfair, as it is intentionally not doing so.

That doesn't change my point. I am pointing out a an easy pitfall Caddy users can fall in since it is not automatically handled for them as it is with other server software, nor is it pointed out in the documentation fkr Caddy. Simple server software would avoid these pitfalls automatically for users. So while it now be simple to get https working, properly configuring the server is now more complex to get right.

An intentional pitfall doesn't mean it isn't a pitfall.

Re:Bluesky announces data federation for self hosters by myaccountonhn on Thursday February 22, 2024 @04:11PM (#39473316)
Hey! Congrats on the release.

Does the AT Protocol only optimize for Twitter-like flows, or does it allow for other types of social applications to be built like Activitypub? For example a reddit-like social media.

Re:Bluesky announces data federation for self hosters by jakebsky on Thursday February 22, 2024 @05:15PM (#39474079)
Currently, atproto works probably best for public social apps, like microblogging, forums, etc. So yes, it's definitely possible to build a reddit-like social app on atproto.

Part of the change today is that the PDS and Relay[1] now support non-app.bsky record types. This is quite new, so there could be issues, but we're prepared to fix any issues that crop up.

1. https://bsky.social/about/blog/5-5-2023-federation-architect...

Re:Bluesky announces data federation for self hosters by cabalamat on Thursday February 22, 2024 @05:18PM (#39474106)
> microblogging

Would it be possible to use it for macroblogging, i.e. long posts with markdown markup, embedded images, etc? If so is there a python library tghat implements atproto?

Re:Bluesky announces data federation for self hosters by jakebsky on Thursday February 22, 2024 @06:47PM (#39474972)
Yes, it should be totally possible to build a blogging system on atproto. And the "app.bsky" API should serve as an example for almost all of the functionality required.

Another really neat aspect of atproto, is that apps can interact theoretically. So you might create a blog system but use "app.bsky" (Bluesky) for comments.

OAuth support is coming soon as well, which is a big step in simplifying auth.

Re:Bluesky announces data federation for self hosters by mightyham on Thursday February 22, 2024 @03:26PM (#39472682)
I'm a little confused why the PDS server is both dockerized and has an installation exclusive to Ubuntu/Debian.
Re:Bluesky announces data federation for self hosters by jakebsky on Thursday February 22, 2024 @04:08PM (#39473266)
Yeah, there's nothing preventing someone from running the PDS server on other distributions. The installer just does a few convenient things for you (like install Docker, opens port 80/443 using ufw, etc) and we haven't added and tested support for other distributions.

There is a Docker compose file in the repo, and advanced users shouldn't have any problems running the code on another distribution or even without Docker if they prefer.

Advanced users can just view the installer script as documentation.

Re:Bluesky announces data federation for self hosters by xelamonster on Thursday February 22, 2024 @05:09PM (#39474013)
Why do you need to open ufw if it runs in Docker? Docker does its own routing magic and will happily blast right through any ufw rules.

Very cool to see this available though, I might have to try it out later this week!

Re:Bluesky announces data federation for self hosters by jakobdabo on Thursday February 22, 2024 @02:07PM (#39471554)
Congratulations on the release! If I may ask a question - is it possible to register an account without a phone number on a 3-rd party server?
Re:Bluesky announces data federation for self hosters by jakebsky on Thursday February 22, 2024 @02:09PM (#39471580)
Thanks!

Yes, it's totally up to a PDS operator to decide how they create user accounts. It's also not required on the Bluesky PDS service any longer, in most cases.

By default the self-hosted PDS requires an invite code, to prevent random people from creating an account. Later other options will exist, including OAuth support which is coming soon.

Re:Bluesky announces data federation for self hosters by jakobdabo on Thursday February 22, 2024 @02:15PM (#39471663)
That's great, thanks!

> It's also not required on the Bluesky service any longer, in most cases.

That's also nice to hear - when last time I tried to register an account (shortly after the free registration launch) the phone number field in the registration form was marked as required, if I am not mistaken.

Re:Bluesky announces data federation for self hosters by jakebsky on Thursday February 22, 2024 @02:20PM (#39471719)
Yeah, you're right, it was. That was temporary measure during the public launch to prevent spam/abuse. We've made some improvements here recently.
Re:Bluesky announces data federation for self hosters by mariusor on Thursday February 22, 2024 @02:58PM (#39472241)
Are there any independent projects implementing the AT protocol?
Re:Bluesky announces data federation for self hosters by jakebsky on Thursday February 22, 2024 @04:11PM (#39473317)
There are a number of independent projects using atproto in various ways.

There's an (incomplete) list here: https://docs.bsky.app/showcase

And the protocol is documented here: https://atproto.com

Re:Bluesky announces data federation for self hosters by mariusor on Friday February 23, 2024 @02:19AM (#39477824)
Thank you, I might be searching for the wrong things, but I don't see any independent servers. There's clients, libraries, bots, but no servers, am I missing something?

My question was motivated by the fact that from the outside the AT proto ecosystem looks pretty monocultural, and personally I don't trust that. :)

Re:Bluesky announces data federation for self hosters by steveklabnik on Friday February 23, 2024 @12:17PM (#39483381)
Federation was just opened up with this announcement. I don't think there was a lot of energy for working on independent PDSes until after this has happened. In the past day, a bunch of copies of this reference PDS have been deployed. We'll see how things change in the future.

Basically, you're right, but just because you're asking early on. This is about to change real quick.

Re:Bluesky announces data federation for self hosters by mariusor on Saturday February 24, 2024 @04:54AM (#39490422)
Sorry to be dismissive but if people need a reference PDS to implement a protocol, I kinda lose faith in its expressiveness.

I'm contrasting this through the prism of having seen people implementing ActivityPub software as early as 2017, when it was merely a draft and everyone was complaining about how many things had been left out.

Re:Bluesky announces data federation for self hosters by steveklabnik on Saturday February 24, 2024 @10:13AM (#39492055)
There are dozens of things being built on the protocol. Just not PDSes. And it’s not because it’s difficult, but because there’s no point until there are others to try and connect to.
Re:Bluesky announces data federation for self hosters by mariusor on Saturday February 24, 2024 @01:06PM (#39493692)
Sorry, I feel like I'm not getting my point across: if building independent software that implements a "federated" protocol doesn't give you a "PDS" then the protocol has failed. You shouldn't need a reference implementation to do it, you should be able to federate with multiple instances of your own software or with other independent implementers.
Re:Bluesky announces data federation for self hosters by mdaniel on Friday February 23, 2024 @05:27PM (#39486948)
I've also had pretty good luck using the GH topics for finding obscure projects https://github.com/topics/atprotocol https://github.com/topics/bluesky https://gitlab.com/explore/projects/topics?search=atprotocol (empty, but I usually check there, too)
Re:Bluesky announces data federation for self hosters by clot27 on Thursday February 22, 2024 @02:13PM (#39471635)
Hi, what is the status of integration with the activitypub protocol? as its currently the most popular protocol in federated social media
Re:Bluesky announces data federation for self hosters by Arnt on Thursday February 22, 2024 @02:24PM (#39471766)
Re:Bluesky announces data federation for self hosters by kstrauser on Thursday February 22, 2024 @04:45PM (#39473727)
That was quit the mess. Ryan Barrett is a smart guy and seems quite nice, but it was very ill-advised to unilaterally decide to build an opt-out bridge. In general, if users one platform A want their stuff to be on platform B, they'll find a way to make that happen. If someone else takes it upon themselves to copy everything from A to B, people understandably get pretty bent about it.

If it had been an opt-in system, the response would probably have been far different.

Re:Bluesky announces data federation for self hosters by CaptainFever on Thursday February 22, 2024 @07:45PM (#39475441)
I'm surprised that the tool in question is Bridgy Fed. Bridgy Fed has existed for a long time and is a very useful tool. Its alternative, Bridgy, has also been used to bridge between closed social networks and the open IndieWeb.

Why are Fediverse people only angry about it now? It's an open protocol. If you want privacy, don't publish something for the entire world to see. At the very least, use Mastodon's privacy controls. The Fediverse is not special here, it doesn't get to destroy the open Web for everyone else.

Re:Bluesky announces data federation for self hosters by jeromegv on Thursday February 22, 2024 @09:56PM (#39476429)
Well first not everyone on the fediverse is opposed to the bridge. I agree that public is public. But there are concerns about moderation being incompatible, it’s normal to voice them.

As for the fediverse destroying the open web for everyone else, I think you’re hyperboling quite a bit, the fediverse has done mountains to make social media more open, probably more than everyone else.

Re:Bluesky announces data federation for self hosters by CaptainFever on Thursday February 22, 2024 @11:32PM (#39477005)
Yeah you're right, I think I did overgeneralise there. I was meaning more of the culture of "Mastodon users"; Mastodon itself has done a lot to help the open Web too.

Though I think "voicing concerns" is a bit of an understatement. I feel really bad for the developer of Bridgy Fed, working on their passion project and just getting caught up in all this heat and harassment.

Re:Bluesky announces data federation for self hosters by rakoo on Friday February 23, 2024 @09:12AM (#39480774)
I'm one of the persons who blocks the bridge, not because of privacy concerns but because it bluesky, specifically. I do not like the idea of for-profit, vc-backed entities being given data, or any kind of decision. We all know exactly where that leads, a term has been coined, mountains have been wrtten about it and yet it still happens.

It's the same situation with Threads.

As for privacy I disagree with you. There's nothing because nothing has been discussed, but the technical feasability should never dictate what we want as a society. When a family member dies, even though the news is known you know how to behave, who to share that information with, what to say. Would you be okay with a company coring up to you and saying "hey we learned your mother died, would you like to tweet it ? It is free !"

Re:Bluesky announces data federation for self hosters by CaptainFever on Thursday February 29, 2024 @12:42AM (#39546678)
I half agree that technical feasibility isn't everything. For example, I can murder someone with a knife. But it's not what we want as a society.

But it's not never. For example, I can see your post. So I can send a screenshot of your post to my friends to dicuss it. I can't see your hard drive contents. So I shouldn't hack into it and send a screenshot of your hard drive to my friends to discuss it.

So technical feasibility influences what is reasonable to do as a society. It's not "feasible = reasonable", or else murder would be reasonable, but it definitely does influence it.

And in this case, I believe what the Fediverse people commenting in the GitHub issue want to be unreasonable. It is unreasonable to publish something publicly, on a federated network, where privacy controls exist (but are not being used), and then claim to have an expectation of privacy in a public space, especially when such bridges provide utility and benefit to others that just can't happen if it's opt-in.

It is reasonable to block it. It is unreasonable to expect everyone else to restrain themselves from using public data in the spirit of the open Internet. It is especially unreasonable to harass non-profit bridge developers in this case. That's not a social solution, just harassment.

Note about copyright: that's not a path one should go down, because it'll make the Fediverse illegal as a whole. It's probably fair use, anyway.

Note about AT protocol: yes it's designed by a for-profit, but it's good. Just because something is for-profit and VC-backed does not mean it will enshittify; take Element for example. It solves a lot of issues that people were having with Mastodon such as global full text search and a global feed. I would use it if it only had more relays to spread out the control.

Re:Bluesky announces data federation for self hosters by NoGravitas on Friday February 23, 2024 @09:33AM (#39481004)
In general, people on the Fediverse want to be able to make local moderation decisions; the way that extends to other federated sites is by not federating with them. Most Fediverse sites will not federate with sites that have bad or nonexistent moderation (or simply incompatible moderation policies). Bluesky's architecture basically means that it is one big unmoderated site. The normal reaction of Fediverse admins is then to block it.

As a controversy, it's been blown out of proportion. It's just Fediverse admins setting the moderation policies for their own sites, as always.

Re:Bluesky announces data federation for self hosters by CaptainFever on Thursday February 29, 2024 @12:32AM (#39546648)
I agree that they should block it, I just don't think they should be harassing Bridgy Fed developers. The GitHub issues were pretty insane.
Re:Bluesky announces data federation for self hosters by Repulsion9513 on Thursday February 22, 2024 @04:48PM (#39473762)
Public is public.

And someone else will just go build an opt-out (or maybe even no opt-out!) bridge.

Re:Bluesky announces data federation for self hosters by kstrauser on Thursday February 22, 2024 @04:55PM (#39473848)
Nah. Consent is a thing and this wasn't consensual. Yes, the posts were publicly accessible, but the intent of posting to Mastodon isn't to have it show up automatically on another network. It's technically possible, yes. It's still a dick thing to do and it pissed people off.

And again, it wasn't about Bluesky in particular. If Google announced that they were going to ingest all Mastodon content and post it in a new Google Groups kind of thing, they'd be pretty understandably upset about that, too.

In general, "if I wanted my stuff on Bluesky, I would have put it there". It wasn't the bridge creator's decision to make.

Re:Bluesky announces data federation for self hosters by Repulsion9513 on Thursday February 22, 2024 @05:14PM (#39474066)
Public = consent for the public to see it. That includes the public on Bluesky. It was consensual. And the ruckus was in fact about Bluesky in particular. That's why the same project already supported other protocols without a big ruckus.

In general, "I want my stuff on Bluesky but don't want to deal with cross-posting to multiple different platforms and keeping up with responses on all of them"

And, "I want my stuff on whatever platform people want to read it on without having to individually approve each one" (which is quite literally the entire point of public posts on Mastodon).

OH - and it wasn't the bridge creator's decision anyway; it was the decision of people on Bluesky to follow you that would trigger your posts to be federated, so...

Re:Bluesky announces data federation for self hosters by kstrauser on Thursday February 22, 2024 @05:21PM (#39474129)
It was meant for the public to see, not to bulk copy it en masse to somewhere else.

Similarly, I don't want my blog posts used to train LLMs. I know they're likely to be since they're published right there on the Internet for anyone to see and read. But my intent was for other humans to see and read them, not for someone to feed them into a regurgitator. There aren't technical means that let me allow humans to read my stuff without allowing LLMs to ingest it, and someone could make the (bad) case that if I didn't want my work to be used to train an LLM, I shouldn't have made it public. Maybe. However, I reserve the right to think someone's an ass for doing it.

Well, no technical hurdles kept the person from copying data out of the network people meant to post it to. It's probably not illegal. It's not a nice thing to do, though.

Re:Bluesky announces data federation for self hosters by Repulsion9513 on Thursday February 22, 2024 @05:25PM (#39474185)
> It was meant for the public to see, not to bulk copy it en masse to somewhere else.

Except literally the entire design is for other Mastodon servers to bulk copy it en masse to somewhere else.

> There aren't technical means that let me allow humans to read my stuff without allowing LLMs to ingest it

Yes there are. Don't make it public.

> However, I reserve the right to think someone's an ass for doing it.

Of course! You can think anyone is an ass. You can think anything you want. That doesn't mean that person did anything wrong.

Re:Bluesky announces data federation for self hosters by 15457345234 on Thursday February 22, 2024 @05:19PM (#39474121)
> Public = consent for the public to see it. That includes the public on Bluesky.

What? No.

If I put stuff on _my_ server you aren't automatically allowed to rehost it on _your_ server. Pretty much automatically a copyright violation in just about every viable jurisdiction.

Basic stuff here

Re:Bluesky announces data federation for self hosters by rglullis on Thursday February 22, 2024 @06:03PM (#39474567)
No, not "basic" stuff at all. It's not only "allowed", federation works exactly by replicating all the activities from the remote servers and even the images you share. If you don't believe it, just go ahead and see what happens when you repost a message from someone's server. The repost will come from your server, not the original creator. Or try deleting a conversation on your server and notice how the other instances will still keep everything intact.

Also, what would be the problem if you put content on your server and someone downloads it and holds a copy? No one is redistributing your content trying to pass it as their own. Attribution is still preserved. What is the copyright violation here?

Re:Bluesky announces data federation for self hosters by Repulsion9513 on Thursday February 22, 2024 @06:23PM (#39474764)
> If you don't believe it, just go ahead and see what happens when you repost a message from someone's server

It's not just reposts. The original post itself is served to viewers by their instance, which is redistribution. (To do otherwise would actually be a massive privacy - and security - concern.)

(To be clear, media - but not the post itself - can be requested directly from the original instance, but any reputable instance will be running a proxy so that random strangers can't trivially get your IP address...)

Re:Bluesky announces data federation for self hosters by Repulsion9513 on Thursday February 22, 2024 @05:24PM (#39474174)
When you share a public post on Mastodon, you are by implication licensing that content for redistribution. Because other Mastodon servers have to redistribute it in order for anyone on another instance to see it. Hope that helps you understand the basic stuff here.

(Either that or every Mastodon server in existence is a massive copyright violation, which is frankly quite possible given how bad copyright law is)

Re:Bluesky announces data federation for self hosters by Angostura on Thursday February 22, 2024 @07:41PM (#39475407)
> When you share a public post on Mastodon, you are by implication licensing that content for redistribution….

… on Mastodon

Re:Bluesky announces data federation for self hosters by icehawk on Thursday February 22, 2024 @08:14PM (#39475655)
...on a server that speaks ActivityPub. Mastodon is one such piece of software.
Re:Bluesky announces data federation for self hosters by Angostura on Saturday February 24, 2024 @05:26PM (#39495689)
Yup, thank you for the correction
Re:Bluesky announces data federation for self hosters by Repulsion9513 on Friday February 23, 2024 @03:43AM (#39478336)
The common term for the network formed by software speaking ActivityPub is "Mastodon", despite that formally being the name of a single piece of that software. Do you also have a problem with Pleroma or Akkoma or whatever? If not then this isn't relevant.
Re:Bluesky announces data federation for self hosters by kstrauser on Thursday February 22, 2024 @06:01PM (#39474550)
I’m a sucker for a particular mix of condescending plus wrong.
Re:Bluesky announces data federation for self hosters by rglullis on Thursday February 22, 2024 @06:12PM (#39474647)
Except they are not wrong. Maybe not in the specifics but in general this is exactly how AP-servers work. If you are on server A and follow someone on server B, then the posts from B will be on your server and there is absolutely no way that the "original owner" of the post on server B to remove the post from A.
Re:Bluesky announces data federation for self hosters by Repulsion9513 on Thursday February 22, 2024 @06:21PM (#39474742)
So am I, that's why I replied to the people who were condescending plus wrong :)
Re:Bluesky announces data federation for self hosters by TylerE on Thursday February 22, 2024 @08:49PM (#39475901)
This is more like when you send an email to gmail.com, Google is allowed to forward the message to its intended recipient.
Re:Bluesky announces data federation for self hosters by rglullis on Thursday February 22, 2024 @05:15PM (#39474077)
> "if I wanted my stuff on Bluesky, I would have put it there"

How about "If I wanted my stuff on the your Mastodon server, I would have put it there"?

"If I wanted my Mastodon content on your RSS feed, I would have put it there".

How about "If I wanted my stuff on the Internet, a publicly available internet, I would have put it there".

This tribalism around network/brands/protocols is beyond stupid. The thing that is killing Twitter is its closedness and the assumption that the means of communication is what matters. It's not. Let open protocols be open.

If people want privacy, then they should use a secure communication protocol and not a social media network.

Re:Bluesky announces data federation for self hosters by mulmen on Thursday February 22, 2024 @05:39PM (#39474319)
> Yes, the posts were publicly accessible, but the intent of posting to Mastodon isn't to have it show up automatically on another network.

I thought that was the point of activitypub.

Re:Bluesky announces data federation for self hosters by ehPReth on Thursday February 22, 2024 @05:34PM (#39474271)
>If Google announced that they were going to ingest all Mastodon content and post it in a new Google Groups kind of thing, they'd be pretty understandably upset about that, too.

exactly like they did with usenet without any issue?

Re:Bluesky announces data federation for self hosters by pests on Thursday February 22, 2024 @08:32PM (#39475780)
Well, at least they paid money for Deja. Slight difference no?
Re:Bluesky announces data federation for self hosters by nl on Thursday February 22, 2024 @11:14PM (#39476899)
I'm completely confused under what moral framework the fact that Google paid to buy the Dejanews archive makes a any difference.

To make it clear, for people who don't know:

Google Groups was originally Dejanews, which was a web based archive and front end to Usenet. Google started searching Usenet, but didn't have historical archives so they bought Dejanews.

Obviously no one who posted on Usenet got paid under this transaction.

It's like if Google bought a Mastadon archive off someone now: this argument seems to indicate that would be better somehow than Google archiving Mastadon posts themselves.

I don't understand why at all?

Re:Bluesky announces data federation for self hosters by Repulsion9513 on Thursday February 22, 2024 @06:26PM (#39474784)
I’m a sucker for a particular mix of condescending plus wrong.
Re:Bluesky announces data federation for self hosters by cabalamat on Friday February 23, 2024 @12:53AM (#39477424)
> Consent is a thing and this wasn't consensual

The whole point of a fediverse is it's a federation. Therefore there is implied consent to copying from one instance to another.

> but the intent of posting to Mastodon isn't to have it show up automatically on another network

Mastodon isn't a network, the network is the fediverse. Mastodon is some software that runs on the network.

Re:Bluesky announces data federation for self hosters by Arnt on Friday February 23, 2024 @04:19AM (#39478578)
What thing is consent?

Mastodon is an odd sort of network, there's more blocking than I expected and it somehow seems as if blocking is an intrinsic part of the design. In Mastodon, blocking looks like a choice one makes for whatever reasons, not an unloved measure needed for fighting abuse.

As if the design doesn't tell users "you can follow people in the fediverse" but rather "your ability to follow people in the fediverse is limited by you and three other parties and the software isn't among the three".

So… if the mastodonish idea of consent doesn't extend to all of the fediverse, what makes bluesky different from some unvetted mastodon site run by weird people? If the poster's/follower's/would-be follower's consent isn't taken for granted in one case and isn't taken for granted in the other, what makes the two cases different? There obviously is a technical difference, but what is the difference wrt. consent?

Re:Bluesky announces data federation for self hosters by NoGravitas on Friday February 23, 2024 @09:40AM (#39481086)
> what makes bluesky different from some unvetted mastodon site run by weird people?

Absolutely nothing! Fediverse admins block unmoderated sites all the time, for being unmoderated. Bluesky is just, effectively, one unmoderated instance that everyone will block by default.

Re:Bluesky announces data federation for self hosters by Repulsion9513 on Monday February 26, 2024 @01:57AM (#39508307)
Assuming your assertions are correct (they're not, but let's assume they are) - what's the problem with the bridge being opt-out if everyone will block it anyway?
Re:Bluesky announces data federation for self hosters by psionides on Tuesday February 27, 2024 @02:46PM (#39528771)
> If Google announced that they were going to ingest all Mastodon content and post it in a new Google Groups kind of thing, they'd be pretty understandably upset about that, too.

Except that's not what the bridge does, at all. It only follows you on someone's behalf when someone on Bluesky specifically requests to follow you through the bridge.

Re:Bluesky announces data federation for self hosters by NoGravitas on Friday February 23, 2024 @09:37AM (#39481051)
And Fediverse admins will block that bridge, just like they would any other site with bad/nonexistent moderation, and will advise each other to block it. That's just how moderation works in the Fediverse. I guess it's sad that, unlike the admin of an instance with bad moderation, the bridge operator can't do anything to fix the problem, but in the end, that's their problem.
Re:Bluesky announces data federation for self hosters by doublerabbit on Thursday February 22, 2024 @02:41PM (#39472008)
Will this work for bare metal?

I use BSD, and all I see is a installer for Debian/Ubuntu.

No guide in sight for bare metal nor telling you what services/software are required.

Re:Bluesky announces data federation for self hosters by whyrusleeping on Thursday February 22, 2024 @02:49PM (#39472117)
yeah it works fine on bare metal, you'll just have to do a bit more set up work yourself (https terminating and such). The installer script should be instructive in how to run it but you'll have to figure out the BSD specific stuff
Re:Bluesky announces data federation for self hosters by lolinder on Friday February 23, 2024 @10:03AM (#39481367)
Look into the service folder in the repo—this repo is just a very thin packaging wrapper for a JS library, which you should be able to run anywhere you can run Node.
Re:Bluesky announces data federation for self hosters by hnbad on Thursday February 22, 2024 @04:57PM (#39473878)
Hi. If the protocol is open, the software is free and the main instance openly federates with self-hosters, what's the monetization strategy here? Clearly it's not "harvest all the data and figure it out later" as that avenue seems to be shut down internationally by strengthened privacy laws and ads don't work well with federation and third party clients. Is "grow first, figure out how to make money later" still a viable strategy in this economy?
Re:Bluesky announces data federation for self hosters by riffic on Thursday February 22, 2024 @05:24PM (#39474171)
managed hosting perhaps? It works in the email industry at least (Google and Microsoft nearly dominate the email biz)
Re:Bluesky announces data federation for self hosters by hnbad on Thursday February 22, 2024 @05:50PM (#39474434)
Yeah but that assumes ATP reaches anything even remotely approximating the ubiquity of email rather than ending up like Google Wave (not literally by being handed off to Apache - which took Wave behind the barn in 2018 in case you're wondering what happened to it).
Re:Bluesky announces data federation for self hosters by paulgerhardt on Thursday February 22, 2024 @05:16PM (#39474086)
Unrelated to engineering but the recent rebrand to a dead butterfly logo[1][2][3] may be off brand for a platform wishing to communicate a more open, social Internet built on first principles and scientific rigor.

[1]https://www.emilydamstra.com/please-enough-dead-butterflies/

[2]https://news.ycombinator.com/item?id=14460013

[3]https://bsky.social/about/blog/12-21-2023-butterfly

Re:Bluesky announces data federation for self hosters by DinaCoder99 on Thursday February 22, 2024 @08:40PM (#39475840)
> built on first principles and scientific rigor.

Are you joking? This is private enterprise we're talking about. We'll all die before this company or anything similar is built on "scientific rigor" unless it directly relates to their profit margins.

Re:Bluesky announces data federation for self hosters by ethbr1 on Thursday February 22, 2024 @05:25PM (#39474184)
Pedantic lepidopterists of the world, unite!
Re:Bluesky announces data federation for self hosters by mehdix on Friday February 23, 2024 @04:59AM (#39478835)
> If you hadn’t previously noted the difference between a living and a dead butterfly, I’m afraid you will now begin to see dead butterflies EVERYWHERE, as I do.

I didn't know this (as most of us I'd guess). It was an interesting read though, thanks.

Re:Bluesky announces data federation for self hosters by miramba on Friday February 23, 2024 @04:02PM (#39486044)
It's true. I read it some time ago...they're everywhere. You can't unsee it.
Re:Bluesky announces data federation for self hosters by idiotsecant on Friday February 23, 2024 @08:28PM (#39488287)
I think the value of a symbol is in the idea it communicates. Most people don't see a dead butterfly. They just see a butterfly. The reality of whether it is more or less like a dead butterfly doesn't especially matter unless a significant amount of people interpret the symbol that way.
Re:Bluesky announces data federation for self hosters by daredoes on Thursday February 22, 2024 @06:03PM (#39474565)
Gonna be that guy!

Any chance the team could create a Home Assistant add-on for this? https://www.home-assistant.io/addons/

I think the Home Assistant community would go WILD for being able to self-host their Bluesky data straight from home with just a few clicks.

It's a pretty big crowd of people. https://analytics.home-assistant.io/ 327k willing to opt-in to analytics.

Re:Bluesky announces data federation for self hosters by floren on Thursday February 22, 2024 @06:12PM (#39474645)
we need a new version of Zawinski's Law: every system capable of deploying plugins will eventually expand until it is a full hosting solution.

I know if there's one thing I'm eager to do it's to host even more stuff in that clunky piece of shit that has half a dozen main menu items for nonsense and buries everything of interest or value under "Settings"

Re:Bluesky announces data federation for self hosters by daredoes on Thursday February 22, 2024 @06:33PM (#39474850)
The add-ons are just docker containers?

It's wasteful to get an entire second machine for something that can use the resources available on the machine running Home Assistant OS

Re:Bluesky announces data federation for self hosters by remram on Friday February 23, 2024 @08:51PM (#39488416)
How would it interact with or extend home assistant?
Re:Bluesky announces data federation for self hosters by throwaway828 on Thursday February 22, 2024 @10:32PM (#39476640)
Given the PDS server works on ports 80/443 and I'd like to use a domain (@nytimes.com in the documentation, but say @example.com), how does it interoperate with existing services that already operate on @example.com , for example a website, blog, cloud.

I'd imagine this use case is quite common for self hosters. If it can't operate alongside an existing, say, nginx on this port, are there recommended alternate practices?

I'm excited at separating identity from hosting, of which self hosting identity gets us closer.

Re:Bluesky announces data federation for self hosters by KerrAvon on Friday February 23, 2024 @01:09AM (#39477503)
Hi jake lovey! Could you fellows stop borderline gaslighting people on how ActivityPub/Mastodon works? You’re not isolated to the server you join on mastodon. Lies do not become us. Thank you.
Re:Bluesky announces data federation for self hosters by CaptainFever on Friday February 23, 2024 @04:12AM (#39478539)
This is incredibly rude, irrelevant (I could not find your claim anywhere in the article posted) and not the way to behave on Hacker News. "Be kind. Don't be snarky." Please be better.
Re:Bluesky announces data federation for self hosters by KoftaBob on Friday February 23, 2024 @07:53AM (#39479943)
Now that individual posts can be viewed without logging in, is there a way to view/load a feed without authentication?

I'm working on a client and there's a specific scenario where I want to be able to show a feed like "Top 20 - Past 3 Hours" before a user has logged in to their Bluesky account.

Re:Bluesky announces data federation for self hosters by nivenhuh on Friday February 23, 2024 @01:24PM (#39484260)
If I wanted to create a consumer hardware product that packages the PDS host in a user-friendly interface, does the software license permit that?

Also, services like Twitter started off with a developer friendly open API, and then it got closed off when the business needed to make money off the platform. What's the difference with Bluesky?

Re:Bluesky announces data federation for self hosters by steveklabnik on Friday February 23, 2024 @02:49PM (#39485266)
(I don't work at bluesky)

It's MIT/Apache 2.0 licensed, so yes. However, because it's also an open protocol, even if it wasn't, you could write your own under whatever license you want.

> What's the difference with Bluesky?

BlueSky is built off of an open protocol, called AT. https://atproto.com/ BlueSky is a particular app built on the protocol. As such, there's no way to "turn off the API," as BlueSky itself is a participant in the open protocol.

They could like, re-write everything to be a central service, port the user data over to it, and then pull out from the network, but then two things would happen:

1. stuff would break, as it's no longer part of the network.

2. since there is true account portability, users could simply swap to a different PDS and client, and re-route around the damage.

Also given that it's against their entire stated mission and goals, it would be social suicide.

Re:Bluesky announces data federation for self hosters by nivenhuh on Saturday February 24, 2024 @08:44AM (#39491432)
Ok, I think I understand the hype now — this is sweet? Thanks for the reply.

When I was thinking about rolling my own federated social service (during the whole Twitter / Mastodon shuffle), I started thinking about the negative impacts of federation. “How can I build a kill switch into this thing in case bad actors start to participate?”

Of course, that means a central authority having moderation control.

But then, part of me thought.. does there need to be a kill switch? Do we want centralized moderation control? If laws are being broken, or social issues are being pressed to the fringe (*lons X), then the ISP would intervene. Or… the responsibility of moderation shifts elsewhere than the provider of the software. (To where do moderation responsibilities shift, if anywhere? I think is still a question.)

I personally landed at the spot of: it’s really no different than what the WWW provides — it’s just easier access. But, is that easier access to self host content and media dangerous? (lol I guess I’m still conflicted about what could happen with wider ease-of-access to self hosting.)

… back to sleep. This stuff literally keeps me up at night lol

(I didn’t get to the other comments further down in this post that talk about content moderation .. but I’m seeing them now!)