I am nobody. I have little impact. I want my programs to be safe from government intrusions, from age checks, from encryption backdoors, from corporate surveillance. How do I win this battle with big tech? I am deeply in self-host. For the self-host to succeed it needs to be better, unregulated, and free. It needs to be easily distributed. The data should be easily distributed. Import and export should be fast and ea…
I would say: 1) Use HTTP (secure is not the way to decentralize). 2) Selfhost DNS server (hard to scale in practice). 3) Selfhost SMTP server (also tricky). 4) Know and backup your router (dd-wrt or iptables). JSON over HTTP is the way. XML is not bad for certain things too; even if I understand the legacy of abuse.
Interoperability Can Save the Open Web (2023)
51–60 of 66 posts
Re: Interoperability Can Save the Open Web (2023)
#52> When Facebook was born, it gave people who were already using MySpace a tool that would pretend to be you and log into MySpace, collect all the messages that your friends had left for you, and put them in your Facebook inbox. You could reply to them there, and it would send them back to your MySpace outbox, so your friends would see them. And that was what allowed Facebook to take so many users from MySpace so quickly. This is what interoperability is about. But if you tried to do that today, Facebook would use laws that were either enforced differently or did not even exist at the time of MySpace, to ruin you.
> If we were to restore this “noble ancient art” of technological interoperability, the users who are so obviously discontent with the platforms they use would consider the costs low enough to leave and join better spaces. In turn, the companies would be smaller, would pay more attention to user satisfaction, and could not push around the governments that tried to hold them to account.
https://www.greeneuropeanjournal.eu/cory-doctorow-how-to-tak...
Re: Interoperability Can Save the Open Web (2023)
#53If you look at the healthcare space, you will realize interoperability only exists because it was mandated by government programs that the patient owns their data and must be provided timely access to all of that data; and also defines specifies the format of that data (open source definitions). You might also define "exists" in some sort of way that makes sense. And you can also realize that payers are encroaching o…
I know nothing about IT project management for healthcare, but just the other day over here in the local news there was a mention that the all-singing-all-dancing healthcare application that the region (with ~1M inhabitants) has been spending years and around 800 million euros to get into production has been so poorly received that they're considering starting over from scratch. I'm so happy seeing my tax money well…
Even if you don't care about this stuff, FHIR is definitely worth investigating.
Re: Interoperability Can Save the Open Web (2023)
#54Re: Interoperability Can Save the Open Web (2023)
#55One of the things we got really lucky with is that Claude Code and not the ChatGPT app won the war for the defining AI product and it runs on your filesystem. There's a different reality where everything had to go through the API on a closed app layer and we're all begging OpenAI to add XYZ endpoint to their platform. Anthropic is now racing to close this gap because they realize there's no lock-in. If the product is…
That might mean leaning into SQLite or some other open format. My own thought is that a graph-like structure of documents will be ultimately more valuable than either a tree-like structure or a database-like structure.
But if a proprietary implementation of whatever usurps structured text in a file-system becomes popular, that company will have significant leverage.
Re: Interoperability Can Save the Open Web (2023)
#56This explains it best: > When Facebook was born, it gave people who were already using MySpace a tool that would pretend to be you and log into MySpace, collect all the messages that your friends had left for you, and put them in your Facebook inbox. You could reply to them there, and it would send them back to your MySpace outbox, so your friends would see them. And that was what allowed Facebook to take so many use…
Re: Interoperability Can Save the Open Web (2023)
#57One of the things we got really lucky with is that Claude Code and not the ChatGPT app won the war for the defining AI product and it runs on your filesystem. There's a different reality where everything had to go through the API on a closed app layer and we're all begging OpenAI to add XYZ endpoint to their platform. Anthropic is now racing to close this gap because they realize there's no lock-in. If the product is…
I don't think this can last, because whatever advantage structured text files in a file tree provides over an API will be maximized by some format that is better than a file system. That might mean leaning into SQLite or some other open format. My own thought is that a graph-like structure of documents will be ultimately more valuable than either a tree-like structure or a database-like structure. But if a proprietar…
But I also agree that this has limitations. If I were to challenge you and say that Obsidian solves this, or gets close to solving it, what gaps would you say were left unfulfilled?
I am because I'm working on something in this space and your comment touches on my three main ingredients: text files, SQLite, and graphs.
Re: Interoperability Can Save the Open Web (2023)
#58This explains it best: > When Facebook was born, it gave people who were already using MySpace a tool that would pretend to be you and log into MySpace, collect all the messages that your friends had left for you, and put them in your Facebook inbox. You could reply to them there, and it would send them back to your MySpace outbox, so your friends would see them. And that was what allowed Facebook to take so many use…
Re: Interoperability Can Save the Open Web (2023)
#59Earlier quoted context omitted.
Let's Encrypt is a non-profit that defeated the certificate cartel. The main thing you get from using HTTP without it is bad security. DNS can answer thousands of queries per second on a Raspberry Pi and crazy numbers on a single piece of old server hardware that costs less than $500.
No root certificate is decentralized. If your DNS port is closed by your ISP, you can't have people use your DNS server from the outside and then you need Google or Amazon which are not decentralized. Also to be selfhosted you can't just forward what root DNS servers say, you need to store all domains and their IPs in a huge database.
The root certificates are pretty decentralized. There isn't just one and you can use whichever one you like for your certificate. The browsers or other clients then themselves choose which roots to trust.
The main thing that isn't very decentralized here is Google/Chrome being the one to de facto choose who gets to be root CA for the web, but then it seems like your beef should be with people using Chrome rather than people using Let's Encrypt.
> If your DNS port is closed by your ISP, you can't have people use your DNS server from the outside and then you need Google or Amazon which are not decentralized.
It's pretty uncommon for ISPs to close the DNS port and even if they did, you could then use any VPS on any hosting provider.
> Also to be selfhosted you can't just forward what root DNS servers say, you need to store all domains and their IPs in a huge database.
I suspect you're not familiar with how DNS works.
Authoritative DNS servers are only required to have a database of their own domains. If your personal domain is example.com then you only need to store the DNS records for example.com. Even if you were hosting a thousand personal domains, the database would generally be measured in megabytes.
Recursive DNS servers (like 1.1.1.1 or 8.8.8.8) aren't strictly required to store anything except for the root hints file, which is tiny. In practice they will cache responses to queries for the TTL (typically up to a day) so they can answer queries from the cache instead of needing to make another recursive query for each client request, but they aren't required to cache any specific number of records. A lot of DNS caches are designed to have a fixed-sized cache and LRU evict records when it gets full. A recursive DNS server with a 1GB cache will have reasonable performance even under high load because the most commonly accessed records will be in it and the least commonly accessed records are likely to have expired before they're requested again anyway. A much larger cache gets you only a small performance improvement.
DNS records are small so storing a very large number of them can be done on a machine with few resources. A DNS RRset is usually going to be under 100 bytes. You can fit tens of millions of them in RAM on a 4GB Raspberry Pi.
Re: Interoperability Can Save the Open Web (2023)
#60Earlier quoted context omitted.
The problem is obviously that the government shouldn't be regulating private speech. They pass these rules by saying "look how big Facebook is, they need to be regulated" when the actual problem is that they need to be decentralized. But then the rules don't apply only to Facebook, and worse, are designed under the assumption of a centralized service so that they entrench the thing that should be eliminated.
But there is nothing obvious about this? For one, this is speech that can only be done using otherwise regulated means. You couldn't claim "free speech" and build a radio tower that transmits long distances, as an easy example. For that matter, you can't claim free speech to allow concerts at your house. You similarly could not claim free speech to rent or loan out rooms of your house for storage. As has been pointed…
This is the fraud every would-be censor perpetrates to establish their chokepoint. First, invent allegedly "neutral" rules that only large entities can comply with, causing only large entities to remain. Then lean on the large entities to censor whatever you want in exchange for political favors or lack of enforcement of other laws.
> You couldn't claim "free speech" and build a radio tower that transmits long distances, as an easy example.
Which is another great example of them doing the thing. The government couldn't spare a single frequency for unlicensed long-distance directional radio communications?
Moreover, the excuse for censoring the airwaves is that there is finite capacity in a broadcast medium, so how is that supposed to apply to a unicast service whose transfer capacity can be increased without bound by running more fiber?
> For that matter, you can't claim free speech to allow concerts at your house.
So if the government wants to declare that you meeting with two other people for the purpose of conveying information to them is a "concert" and prohibit it from any place that isn't a "concert hall" (which is prohibitively expensive for you to own), that seems fine to you?
> As has been pointed out elsewhere, if you want to take the effort to connect and verify the different parties that are going to communicate with your server, you are almost certainly going to remain free to do so.
All you have to do is the thing which is morally and economically unsound.
> But we already require inspections and other similar activities for things that individuals can do at home without an inspection.
Except that now you want to do it even when they are doing it at home.