Actually you can… I do that with my setup. Just point your domain to the new ip assigned by tailscale to your server. Thats all. Recently they started supporting the https certificate also… Even though it’s not needed, for internal only communication.
It’s the github username
Some search turned this up. Still I have no clue what the comic means
Am I too old to understand this? Or am I too young?
Well… I think you are putting too much expectation on a common person. I’m pretty sure a lot of people are going to be ‘mind blown’, by the ability of the new Recall feature. They will hail it as a technological marvel. Very few people care about privacy, and even in that, very few people really understand how they can have some privacy. Complete privacy is near to impossible.
Come on… don’t be so pessimistic!!
The last part about the stack overflow account and forum account is about the infamous silk road admin, Ross Ulbricht
Aamm… What?
I actually use Nginx. The major advantage is if you have to access something directly. For example a client app in your device wants to access a service you host. In that case Heimdall won’t be enough. You can still use ip with port, but I prefer subdomains. I use Nginx Proxy Manager to manage everything.
Regarding the network going down, the proprietary part of the tailscale is the coordination server. There is an open source implementation of the same, called headscale. If you are okay with managing your own thing, this is an alternative. Obviously the convenience will be affected.
Apart from that, if you haven’t already read this blog post on How tailscale works? I highly recommend reading this. It gives a really good introduction to the infrastructure. Summary is your connections are P2P, using wireguard. I don’t think tailscale will have a failure scenario that easily.
I hope this helps.
The exact setup can be achieved by tailscale, a not really known feature is you can point your domain to the, tailscale IP (new ip assigned by tailscale), and it will act just like a normal hosting setup.
Advantage, any device or someone who you do not pre approve can’t see anything if they go to the domain and subdomain. They only work if you are connected and authenticated to tailscale network. I have a similar setup, if you need more pointers please ping me.
If you have used AnyDesk in the past, this gives the same experience. Recently used it and has a lot of features, including unattended access.
They recommend self hosting an instance for better performance.
What I understood is they don’t release it on the public internet as we do, but it is accessible for others inside China. How exactly it is achieved is still I have no clue of. I heard this in some podcast.
Yes it is not in alignment with the spirit of open source. In the “industrial districts” there is no validity for copyrights. Means if one company developed something, any other can adapt it without any restriction, even without a license. This is very counter intuitive to our capitalistic rules. But this policy essentially forces you to make progress as quick as possible, else someone else will adapt it and make a product out of it. Then you lose all the market.
China is forcing companies to make money out of capitalistic economies, but restricts the “knowledge” or “technology” accumulation into a few mega corporations.
At least this is the theory. But as everywhere else corruption and hunger for power screws up things in China also.
Syncthing is used if it is not a one time transfer. LocalSend is mainly for one time transfer. LocalSend needs things to be in the same network. The same WiFi router is enough. Syncthing can send files over the internet also.
There are browser based alternatives like ShareDrop . These tools are not as reliable as Syncthing and LocalSend, especially when it comes to single large files (more than a few GBs), like ISOs.
For one time transfer over the internet, another handy tool is Croc . This one also suffers from the large file related issues.
Hmm… Machine learning on a dataset with images?
Recently they officially added a module to censor stuff on an individual instance basis…
The what?? Is it a condition?
One thing you can try out, if you haven’t done already, is configuring 2 different ports for the two users here. GUI has an option to adjust the ports, also you can configure two different services to start depending on the logged in user. I haven’t done it myself on Linux, but it looks like people had success. One R*ddit thread for example,
IP should not cause any issues. IDs are just a hash of certificate used by Syncthing. Can you elaborate a little on the current setup? Device, OS, User, etc. Also if possible can you explain your use case? As I mentioned, Syncthing is very specific to what it can do, so it may not be the best solution for your case.
git commit --amend --no-editThis helped me countless times…