hmm I’m not sure I understand you. qbittorrent allows you to set whether you want to also use I2P or only that, globally for all torrents. but I2P peers who are in mixed mode, they can work as a bridge, getting the pieces from internet peers and redistributing it on the I2P network
And in terms of torrenting specifically, torrents have to explicitly support I2P. You can’t just take any clearnet torrent and expect it to work on I2P.
are you sure about that? for public torrents you just add the postman tracker and done. if libtorrent gets support for DHT over I2P, even that won’t be needed
why not codeberg? kind of lightweight on JS, but especially compared to gitlab.
that would probably work. I think the IP does not need to be static, but there can be problems if your IP changes often, and it’s not updated quickly in DNS.
the only hard requirement for a local headscale (for usage over the internet) is that you are not behind a CG-NAT, and you can forward a port to your server in your router
but for the love of god and your own benefit, put a name constraint directly on the root cert
you don’t strictly need a VPS, what you need is a (mostly?) static IP address, that is especially not behind CG-NAT. if your ISP won’t give that to you, you get a VPS, because one of the most important jobs of headscale is NAT hole punching and patching your devices in
the first paragraph is not like in the post. did they rephrase it because of the “as it does” part?
this is the current version:
Tailscale recently announced our Series C fundraise. We were grateful for all the community support, but the Internet also raised a few of its collective eyebrows, wondering whether this meant the dreaded “enshittification” was coming next.
the internet archive does not show your version either: https://web.archive.org/web/20250702140430/https://tailscale.com/blog/evitability-of-enshittification
where did you get that quote from?
This theory is based on my understanding that computers don’t go all the way to sleep anymore and reenabling S3 restores normal sleeping.
yeah, now that you say that is probably most laptops in the last few years. but I don’t think desktops do it. wrong, even my 4+ years old pc motherboard supports it according to /sys/power/mem_sleep
I wanted to say this is not how it works:
My pet theory is that a lot of systems are constantly looking at what is active on the network and those pings are keeping the machine awake.
or if you meant that, computers are normally not pingable when they are asleep. net adapters only wake the computer when seeing a magic packet with their mac address in it, and it is the operating system that receives the ping request and decides to send back a ping response.
an exception is when it is set up to wake on some network traffic pattern, but few net adapters support that mode of operation
https://wiki.archlinux.org/title/Wake-on-LAN#Enable_WoL_on_the_network_adapter
as I heard that’s pretty common at oracle, but it’s good to spread the word
its not the system that handles wol, it doesn’t need to ping anything. even the net adapter doesn’t need to do that
the config and databases or the media, you mean?
if so, the former, but I mount the meadia with a read only docker volume just to be sure, because chances are I would never notice it
well there’s lots of wasted space where the vacuum bag is empty
I have a satellite tracker for when I want to contact radio sats,
which one do you use? can it show where is it on a camera background?
you must have lots of LoTs
wpa2, but password limited to 10 characters. letters and numbers only, trying anything else crashes it, and you have to figure this out yourself
ok, a backdoor then. can they overwrite any file with it?
with properly limited access the breach is much, much less likely, and an update bringing down an important service at the bad moment does not need to be a thing
it’ll still cause downtime, and they’ll probably have a hard time restoring from backup for the first few times it happens, if not for other reason then stress. especially when it updates the wrong moment, or wrong day.
they will leave vulnerable, un-updated containers exposed to the web
that’s the point. Services shouldn’t be exposed to the web, unless the person really knows what they are doing, took the precautions, and applies updates soon after release.
exposing it to the VPN and to tge LAN should be plenty for most. there’s still a risk, but much lower
“backups with Syncthing”
Consider warning the reader that it will not be obvious if backups have stopped, or if a sync folder on the backup pc is in an inconsistent state because of it, as errors are only shown on the web interface or third party tools
what? these are non-existent. jitsi works fine. webaudio api was disabled by default a few years ago, but not anymore.
but I have no idea what do you mean with images