Coffee. Caffeine doesn’t really work for me in terms of giving me energy, but I like the taste of a nice cup of cortado.

I like tea as well, but can’t stand the herbal stuff. Only Camellia sinensis for me.

Ok

It’s Lemmy, you’re anonymous, of course I don’t know shit about you. You may be the most wonderful person in real life, but I’ll only respond to what you say here. So this defense is utter bullshit. Don’t post on anonymous forums and then complain that people don’t know anything about you before replying to your comments. That’s the whole point of anonymous forums. That people only reply to what you explicitly post, and nothing else.

Also, I’d suggest not taking any of this personally. None of us are properly represented online. All this criticism is just about your opinion on this one topic, and do not reflect our (at least mine) opinion about you as a person. (Because we have no idea about you as a person.)

When it’s the software that’s actually faulty. As others have mentioned, Firefox usually sticks to the standards. You’re just using some peculiarities of Chromium, which is why you might be having issues. Anyway, this actually seems irrelevant to your stance, since you care more about the market share. Which is fine, being profit driven and all. But then you shouldn’t get annoyed when people like me call you lazy.

You do realize that you had the experience due to lazy developers such as yourself?

I can attest to that. I was born and brought up in India, and right now in the US for education. It’s kind of the same here as well, just expressed differently due to cultural differences. The fact that the US is actually the world leader at this time makes these people much more dangerous imo.

In any case, I’m more hopeful about my country after the last election. They seem to be rejecting religious fundamentalism to some degree. It’ll take time, but I think we’re finally starting to see through BJP’s lies. I hope I can go back to India soon enough. (It’s hard to get good jobs in my field there at the moment. Counting on it changing at some point.)

Don’t you think that it may be because Firefox is pretty much the only browser using a different engine that Chromium? There are literally two major browser engines, and you’re developing for one them. Ofc everything else will act like Chromium, because they are Chromium for the most part.

Honestly, I’d be fine and understand that he cannot but be complicit in this due to powers beyond his reach. I’d eat my words if he says that he doesn’t like it, but has to comply. But he seems like he’s pretty happy with it. (Again, from that one comment.) I will blame the sandwich artist if he defends shitty sandwiches. Because one has to be responsible for their own work. They’re free to not give a fuck about what anyone thinks. But they are complicit.

I never said he alone did it. I’m sure he’ll be happy to share credit for any great product his company makes. Why not take some of the blame too? (I’m not sure if he does think that way though. He hasn’t replied since. I’m just replying to other people.)

Do you think that this workflow is some divine commandment? Developers like him create these. He should totally get some of the blame.

My grandmother. She was 96. She saw India’s Independence, and lived through the Bengal famine of 1943. What a life! She died in peace surrounded by family though.

Thanks, I’ll check it out.

Thanks for the suggestion.

Where are you, if I may ask? Their Intel offers are not based in the US. Most of the time, I’ll access it from inside US, so I’m worried about the latency.

Without anything extra, there are three ways of doing it:

1. Using Tailscale Funnel
2. Direct port forwarding in your router, and pointing to the IP using some DDNS provider (e.g. desec.io)
3. Through Cloudflare tunnel (not recommended due to privacy reasons)

In each case, you’ll need a reverse proxy (e.g. Caddy) if you want secure https connections.

If you’re willing to spend money, the better way would be to proxy through a VPS (using something like a Wireguard tunnel). In that way, you won’t have to open ports on your home router. You can get a very cheap one since proxying doesn’t need much CPU power. Just choose one with enough bandwidth. I personally proxy most of my stuff through a $12/yr RackNerd VPS.

The BSD Conjecture.

• Behind the Bastards
• Dan Carlin’s Hardcore History
• A Podcast of Unnecessary Detail
• Cozy History

My setup looks like the following:

/etc/wireguard/wg-vps.conf on the VPS
-----------------------------------------------------
[Interface]
Address = 10.8.0.2/24
ListenPort = 51820
PrivateKey = ********************************************

# packet forwarding
PreUp = sysctl -w net.ipv4.ip_forward=1

# port forwarding 80 and 443
PreUp = iptables -t nat -A PREROUTING -i eth0 -p tcp --dport 80 -j DNAT --to-destination 10.8.0.1:80
PreUp = iptables -t nat -A PREROUTING -i eth0 -p tcp --dport 443 -j DNAT --to-destination 10.8.0.1:443
PostDown = iptables -t nat -D PREROUTING -i eth0 -p tcp --dport 80 -j DNAT --to-destination 10.8.0.1:80
PostDown = iptables -t nat -D PREROUTING -i eth0 -p tcp --dport 443 -j DNAT --to-destination 10.8.0.1:443

# packet masquerading
PreUp = iptables -t nat -A POSTROUTING -o wg-vps -j MASQUERADE
PostDown = iptables -t nat -D POSTROUTING -o wg-vps -j MASQUERADE

[Peer]
PublicKey = ********************************************
AllowedIPs = 10.8.0.1

/etc/wireguard/wg-vps.conf on my home-server
---------------------------------------------------------------
[Interface]
Address = 10.8.0.1/24
PrivateKey = ********************************************

[Peer]
PublicKey = ********************************************
AllowedIPs = 10.8.0.2
Endpoint = <VPS-DDNS>:51820
PersistentKeepAlive = 25

Now, just enable the tunnel using sudo systemctl enable --now wg-quick@wg-vps. Make sure that the port 51820, 80, and 443 are open on the VPS. Now, allow 80, 443 through the firewall on the home-server (not on the router, just allow it locally), and it should work.

I’m afraid that I don’t have any guides. But, you’re halfway there anyway. Which one of these methods do you prefer? I can maybe give you some pointers.

I have a wireguard tunnel set up between my home server and the VPS, with persistent keepalive. The public domain name points to the VPS, then I have it set up (simply using iptables) so that any traffic there in port 80 and 443 is sent back to my honeserver and there it’s handled by caddy, and sent to the actual service.

The only ports I need to open are 80 and 443 on my VPS to make this setup work. So, no open ports on my local machine. This does however require you to pay for VPS. Since you aren’t doing much on it though, you can get away with a cheap one. I have a $12/year VPS from Rack nerd that I use for this job.

For completely free options, you can do one of three things. (That I can think of. There are probably more ways.)

1. Either open up some ports on your machine. You’ll need to make sure that you aren’t behind a CGNat for this. I simply don’t like opening ports to the internet, though.
2. You can use a VPN. Tailscale works great for this. I use it personally for sshing remotely into my machines.
3. You can use cloudflare-tunnels. Potentially bad privacy-wise since they can technically access the data. So don’t use it for sensitive stuff. Also, their policy doesn’t allow traffic that’s not mostly HTML. So something like a Jellyfin server would violate this. But you do get to use their firewall which is great for protection against DDOS attacks.

P.S. If you need help setting any of these up, lmk.