The general topic was about self-hosting. IPv6 is very useful for self-hosting,… connections.

I’ll admit there is a critical mass problem with torrenting clients, but if you’re trying to set up a wire guard tunnel with your friends, IPv6 is a absolute banger

In most environments ipv6 bypasses cgnat (because, why would you need a nat with ipv6).

Yeah, to me it’s a absolute killer feature for a travel phone. The GOS discussion around it boils down to violating the android profile security model.

E.x., im using a hotel wifi that only allows one device, or I have a esim for one phone only that doesn’t allow “tethering”.

Fair enough on the security model, but at least give me the option… Maybe with a always on notification warning. Being paternalistic about how you think the phone will be used and in which context is overstepping for infrastructure

I travel with a backup phone, and because of this I have calyxos on the backup and not gos.

lineageOS, and CalyxOS both let you share vpn over hotspot connections.

most AVR, automatic voltage regulators, won’t allow for rapid switching on and off.

Actively cooled UPSes, especially the ones that do more active double conversions, absolutely always have the fan on.

PCU: power conditioner unit?

VRU: voltage regulator unit?

While the UPS does have lots of upside, there are some downsides to consider:

Battery is a consumable, off gas venting, perhaps active cooling fan noise

oh interesting, what reasons make the ups safer?

It doesn’t sound like you need a UPS. It sounds like you needed automatic voltage regulator.

It’ll condition the power so it’s clean, and if it’s not clean it’ll cut the power off.

Many good UPS’s have a voltage regulator built in, but then you have the hassle the battery and everything. Up to you depends on what’s easier to find for you locally

I have a, honest to goodness breaks the electron flow, power switch for a reason, the shutdown command was a warning not a request.

https://psdoom.sourceforge.net/

process management intensifies

Assume you’re incapacitated, and somebody gets access to your recovery document. What information do they need to do what you would want them to do. Make sure all of the information is there, and all the steps are written out

https://github.com/cyphar/paperback If having your secrets written out is a little too risky, you might consider a distributed secret sharing approach. So multiple people you trust would have to coordinate to recover the archive

What country are you in? China?

Go to mullvad settings and choose random ports

Try 53, 80, 443 etc

Try mullvad use different ports, use their circumvention approaches.

Use your cell phone mobile data

Talk to the hotel, tell them you cannot connect to your corporate vpn, ask if they have a workaround

I’m just trying to understand the rational. To me I downvote when the comment is against the community, or unproductive.

If I’m being a net negative I should know why! Usually I have a guess as to why, but when I don’t, I reach out so I can understand better. I do want lemmy to be a better place, so feedback is useful.

I get a lot of downvotes. I realize I say things that can be divisive. Why are people downvoting debugging steps? What’s divisive about that…

Are your phones on the same network? Same vlan? Firewall rules? VPN?

Does tcpdump on the server see the request?

https://rss.ponder.cat/post/13668

If you want a ton of fun, you can build it yourself!

Depends on your use case there are multiple factors that guide internet use cases

• Latency - how fast
• Bandwidth - how wide/much
• Loss - how much data is lost, or how much data needs to be sent again

Gaming: latency, loss

YouTube/movies: bandwidth

Video chat/voice chat: latency, bandwidth

Remote desktop/game streaming: latency, bandwidth, loss

Web browsing: bandwidth, latency

DNS latency can be a multiplier for browsing the web, a website can include artifacts from other websites, which then can include other websites, which then can include other websites. Each one of those would require another DNS lookup, and round trip time to the website itself etc. however, DNS was architected for local caching, so only the first lookup should be slow, and then afterwards you should keep that DNS information for future lookups so it’s not going to feel too bad once you’ve warmed up the cache

Rule of thumb: under 100ms feels fine, over starts to feel a little sluggish. Over 300ms and you change your behaviors, and you really feel it.

• a fork of telegram ✅
• Works with some other chat server ✅

You can now use telegram with any matrix compatible client you like

https://github.com/mautrix/telegram