Live data from Hacker News

Interoperability Can Save the Open Web (2023)

spectrum.ieee.org

31–40 of 66 posts

Re: Interoperability Can Save the Open Web (2023)

#31
post #16

Earlier quoted context omitted.

There are the openstreetmap mapping apps (OSMand, organic maps)

Organic maps should be used instead of OSMand, https://news.ycombinator.com/item?id=42343121 Or maybe Comaps, https://news.ycombinator.com/item?id=43961908

I share your preference for Organic Maps over OsmAnd, and while I haven't been daily-driving CoMaps for long (nor has anyone, really) I already significantly prefer it over Organic Maps. I need to use it long enough to see what the edge cases are like, but after using it three time zones worth of rural places and dense cities, it has worked well.

Re: Interoperability Can Save the Open Web (2023)

#33

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.

Re: Interoperability Can Save the Open Web (2023)

#34
post #33

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.

1) so how do you validate the http the client receives is the http you sent?

Re: Interoperability Can Save the Open Web (2023)

#35
post #34
post #33

Earlier quoted context omitted.

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.

1) so how do you validate the http the client receives is the http you sent?

Validate it yourself with hashing and PKI. Yes, it needs bootstrapping, just like centralized HTTPS needs bootstrapping.

Re: Interoperability Can Save the Open Web (2023)

#37

Earlier quoted context omitted.

> 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? If you're only talking specifically about your program that no one else has access to, I don't think there is any battle? Do whatever you want, no one cares nor would even know about it. If you're talking about m…

> If you're only talking specifically about your program that no one else has access to, I don't think there is any battle? Do whatever you want, no one cares nor would even know about it. Can I do it on my phone?

No because a phone, despite being made from the same parts as a computer is actually a completely different thing.

You can't just run programs on your phone. You have to run apps, which require approved by the government and the company that made the phone, which tacks on additional fees as well. The phone also has constant cellular/GPS/wifi/bt-mesh location tracking, and it can never be completely turned off by the user without destroying the phone because even the batteries are glued in.

It's basicially the perfect slave device for your average goy. And everyone will need one to to access your bank account, recieve insecure SMS authentication, talk to other NPCs, and generally participate in the neo-economy.

If you don't think this is right, you are literally going to empty the bank account of my dumb ass grandma who can't stop installing malware, and in every way is better served by a flip phone from the early 2000's.

Re: Interoperability Can Save the Open Web (2023)

#38
post #34

Earlier quoted context omitted.

1) so how do you validate the http the client receives is the http you sent?

Validate it yourself with hashing and PKI. Yes, it needs bootstrapping, just like centralized HTTPS needs bootstrapping.

Wow, thanks!

Also if people need more food for (decentralized) thought:

https://datatracker.ietf.org/doc/html/rfc2289

Re: Interoperability Can Save the Open Web (2023)

#39

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…

[deleted]
Post reply on HN