11–20 of 151 posts
I'm pro decentralizing the internet, but these movements really need some marketing chops. ".onion" TLD? (Yes I know it has been around for awhile) Think of how a normal person will view a ".onion" domain name. It's nonsensical to the uninitiated.
What’s the advantage of accessing an onion service (as opposed to accessing a normal https website over tor)?
What’s the advantage of accessing an onion service (as opposed to accessing a normal https website over tor)?
The website cannot identify who they are, what ISP they use, or where they live. Similarly, middleboxes such as their ISP cannot find out what websites they are browsing, which is still easily possible even with TLS via many methods (DNS, SNI, IP correlation, many others)
I'm pro decentralizing the internet, but these movements really need some marketing chops. ".onion" TLD? (Yes I know it has been around for awhile) Think of how a normal person will view a ".onion" domain name. It's nonsensical to the uninitiated.
Last century "network" and "web" were metaphors that meant nothing to the uninitiated -- I feel that ".onion" has a shot.
Earlier quoted context omitted.
What about http, ://, www and other TLDs like .co.nz or .ac.uk? All of these were pretty meaningless to initiates of the internet. In this new age of ".pizza" and suchlike, ".onion" doesn't seem much different or weird tbh. (To be clear: I don't think these new tlds are especially good either, but it's the world we live in now.)
To me, .onion reminds me too much of The Onion.
I thought it was going to be some random "AI" project that could rewrite your prose in The Onion humour ala:
https://www.theonion.com/fuck-everything-were-doing-five-bla...
I'm pro decentralizing the internet, but these movements really need some marketing chops. ".onion" TLD? (Yes I know it has been around for awhile) Think of how a normal person will view a ".onion" domain name. It's nonsensical to the uninitiated.
Earlier quoted context omitted.
The website cannot identify who they are, what ISP they use, or where they live. Similarly, middleboxes such as their ISP cannot find out what websites they are browsing, which is still easily possible even with TLS via many methods (DNS, SNI, IP correlation, many others)
What I mean is, how is a .onion website over tor better than an https website over tor? I edited my comment to clarify.
* You don't need a TLS certificate from a public certificate authority, as it is already encrypted end to end
* The exit node cannot attempt to snoop on your traffic (via TLS SNI) or inject content/ads/exploits into your unencrypted traffic
* It reduces load on the exit nodes so they can work on serving traffic to sites that don't have an .onion endpoint
Earlier quoted context omitted.
The website cannot identify who they are, what ISP they use, or where they live. Similarly, middleboxes such as their ISP cannot find out what websites they are browsing, which is still easily possible even with TLS via many methods (DNS, SNI, IP correlation, many others)
What I mean is, how is a .onion website over tor better than an https website over tor? I edited my comment to clarify.
What’s the advantage of accessing an onion service (as opposed to accessing a normal https website over tor)?
Computerphile did an interesting video series on this!
I operate a few websites that host static content only. Is there any benefit to setting up onion services for these sites? Or are onion services more valuable for providing interactivity/logins?