Yes and no. Wasm has no "standard library" so if you wanted to use Dates, your wasm would need to have its own implemation bundled for when the user visits the page. Ditto for everything else including string support! As you can imagine having to ship all this basic functionality can bloat the wasm and slow page loads.
You also can't fully escape JS, as the only way wasm can interact with the page & browser are through the JS functions you write and make available to your wasm. I suppose you could take advantage of this to not have to ship your own standard library & use the JS Date implementation, but at that point why not just use JS?
Wasm has strengths but it's not suitable for replacing JS for everyday websites.
In practice I doubt Americans would end up qualifying for refugee status, at least not yet. I'm pretty sure you have to show there are no safe places in your country, and many US states are more reasonable for LGBT folks than some Canadian provinces are.
I feel like which network depends on what you're advocating for and to which type of person. For example, Mastadon, Lemmy, and Bluesky are fairly left-leaning, so advocating for a well-known liberal idea there could be "preaching to the choir".
Your approach won't work if you're behind carrier grade NAT or you can't open ports. My landlord provides my internet so I use tailscale (with headscale on my long distance vps) to connect everything and it works great. It uses LAN when I'm home, and NAT punches when I'm elsewhere.
Ditto. I use unique passwords for services I care about / someone could exfiltrate sensitive data, and a cheap reused password for services I don't care about and could easily regain access to with a password reset email.
It's not even necessarily the ISPs that are doing it. In many cases they don't like this because their users start getting blocked on websites; it's bad actors piggy-packing on legitimate users connections without those users' knowledge.
There are residential IP providers that provide services to scrapers, etc. that involves them having thousands of IPs available from the same IP ranges as real users. They route traffic through these IPs via malware, hacked routers, "free" VPN clients, etc. If you block the IP range for one of these addresses you'll also block real users.
When I worked for a startup we'd sometimes go out for lunch and everyone would have a drink or two. We also kept beer in the office fridge but that was reserved for more Friday afternoons.
Yes but there are ways to protect against that. For instance you can configure Tailscale clients to only trust nodes that have been signed by trusted nodes, or something like that.
Yes and no. Wasm has no "standard library" so if you wanted to use Dates, your wasm would need to have its own implemation bundled for when the user visits the page. Ditto for everything else including string support! As you can imagine having to ship all this basic functionality can bloat the wasm and slow page loads.
You also can't fully escape JS, as the only way wasm can interact with the page & browser are through the JS functions you write and make available to your wasm. I suppose you could take advantage of this to not have to ship your own standard library & use the JS Date implementation, but at that point why not just use JS?
Wasm has strengths but it's not suitable for replacing JS for everyday websites.