Hacker Newsnew | past | comments | ask | show | jobs | submit | indianets's commentslogin

P2P within LAN?

For anything outside your LAN, 2 nodes must need a negotiator(over internet) to know each other unless the nodes already have public dedicated IPs in which case they can talk to each other securely without the need of a negotiator.


For rsync, you need to have 2 nodes on "internet" publicly reachable.

The USP of wush is to create a Virtual LAN like point-to-point secure network for your devices behind NAT or CG-NAT and then use rsync or cp or ssh.


I own 2 of the 2-character ccTLDs, it was a thing to boast around 10 years ago. Today no one cares, all they know are apps and google.


What cctlds?


Because of exorbitant price set by the registry. After the apps boom, domain name has lost half of it’s value. And, rest was messed up by the new TLDs.

I strongly believe if there was original gTLDs and ccTLDs, internet would be a better place.


This sounds like a good thing though. The high price makes squatting unviable so domains are left unregistered and available for someone who will actually use them.

All the new TLDs removed scarcity from the system which didn’t provide any value.


Did you see the last reply on the thread you linked. The guy messed up ENV variable in borg and was doing too many account backups as new archives killing the cache when the same account was backed up next day. Borg will always be faster than rsync while doing incremental backups, but of course has a learning curve coming from the simplicity of rsync.


Also other apps.


I had a similar issue with VoWiFi on my network due to EDNS, and it's rightly pointed out by msilverlock in forum.

  # dig vowifi.jio.com @1.1.1.1 A
  ;; ANSWER SECTION:
  vowifi.jio.com. 5 IN A 49.45.63.1
  vowifi.jio.com. 5 IN A 49.45.63.2
  ;; SERVER: 1.1.1.1#53(1.1.1.1)

  # dig vowifi.jio.com @8.8.8.8 A
  ;; ANSWER SECTION:
  vowifi.jio.com. 4 IN A 49.44.59.36
  vowifi.jio.com. 4 IN A 49.44.59.38
  ;; SERVER: 8.8.8.8#53(8.8.8.8)

https://community.cloudflare.com/t/vowifi-issues-due-to-poss...

As the article links to and says "privacy versus convenience", and I am happy that CloudFlare chose the former.


That million Firefox users who chose Cloudflare DNS must know that chose "privacy versus convenience" too and be happy with that.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: