• 0 Posts
  • 12 Comments
Joined 5 months ago
cake
Cake day: July 25th, 2025

help-circle

  • One reason I would give is that apple and google makes it incredibly hard to leave. I had to use some third party script (and give it my credentials or token…) Just to export pictures with the exif metadata from iOS. Even Google’s obnoxious “select a few thousand pics at a time” was easier (Google takeout puts the metadata separately, so it was also not an option).

    Another reason is that big tech companies are complacent with kidnappings and oppressors and don’t want to give them money.

    I could see apple breaking the tool or throwing their legal team around in the future if it keeps some people on their platform, why not leave while you can more easily.



  • For new people, for ongoing domain registrations people should also consider the renewal costs. There are some registrars with somewhat predatory pricing schemes that end up being very expensive long term (e.g. the trendy .io TLD).

    Dot com and dot net are some of the most stable ones, even though they might not appear as such at first glance. Almost anything less costly on initial costs will cost you in some other way (might not offer whois privacy (.us iirc) or be limited to residents or people with legit business on that country (.ca) or have a mixed reputation with being labeled spam (.xyz - although I believe this last one has been kind of proactive in clearing that up).

    Sorry to highjack the comment, but I wish someone had warned me to look, not all TLDs are administered the same.


  • There’s something called NAT reflection that does a local lookup if the request originated in the internal network and avoids going via the external route. Some software for routers like ONPSense and/or PFSense support it (but I wouldn’t be surprised if DD-WRT, Tomato, etc supported it as well (its been a while since I used them)).

    It might work better of your DNS provider supports API based challenges vs traditional ACME challenges that might require you to still expose your IP/challenge ports with public DNS to get your certificates.

    All my internal DNS has the option of SSL certs while my IP is not on any public DNS and it routes to the internal IPs with the above. Not sure how that would work with wireguard or tailacale/headscale, but I’m assuming they probably could complement nicely.



  • On the other hand, there are people wasting our time (relatives) and have no data in the machine which is a glorified browser.

    For them I installed Linux mint, left a 200x200 Firefox icon on the desktop (which they already used) and called it a day.

    If they accidentally hit the mute button on the YouTube page, that was going to happen regardless and I’ll get to it when I get to it next time I visit (if I have time). It’s kind of amazing how they can resolve it themselves when you don’t solve the issue for them quickly.

    Edit: my point was: their desire doe no change does not come before my desire to have an up to date secure OS for them to use (even of it’s just YT browsing)