• 0 Posts
  • 49 Comments
Joined 2 years ago
cake
Cake day: July 1st, 2023

help-circle


  • I just laughed and said oh well that’s what you get when you moved from on prem to cloud.

    Our Techs said that you couldn’t buy on-perm exchange anymore. You needed to go with the cloud subscription, which “includes” all the crap you don’t want: like Teams.

    Atleast, they said didn’t make financial sense to pay for Google Workspace + Slack + Cloud Exchange, when MS offered their (lesser) services as a bundle (but the human suffering is real) :(




  • In my mind, introducing Rust would only make sense if:

    1. There was a serious lack of current kernel developers (which I don’t think there is)
    2. New hardware and tech was evolving at a rate that the Linux Kernel could not keep up (again, I don’t think this is am issue)
    3. The end goal is to migrate the entire Kernel to Rust.

    Regarding point 3, having both C and Rust really only makes sense as a transition phase (measured in years) - as it would require kernel developers to be savvy in both C and Rust, or would force developers to stay within whatever domains were implemented in C or Rust.


  • It’s more than needing a reminder: Let’s Encrypt Certs are valid for a maximum of 90 days before they need to be reissued. Doing this 4 times (or more) a year, for years on end will be tedious and error prone.

    Most tools that request and install Let’s Encrypt Certs automatically do this without the need for human interaction (30 days prior to the expiration) . Actually, they work so well you don’t notice the “behind the scenes work” that’s happening.

    The problem is when this renewal process “stop working”. I’d been using Let’s Encrypt for years w/o problems, but eventually the client I was using wasn’t updating and it was using a deprecated Let’s Encrypt API. Ultimately, the cert stopped updating, but I got the email reminder from Let’s Encrypt and I was able to fix it w/o a disruption.

    Now, this was just a server for personal use. So if the SSL cert expired, it would not be the end of the world. Plus, I would have gotten a bunch of SSL errors the next time my client was trying to sync data, and I probably would have dropped everything to fix it. But the email reminder was a convenient feature, which allowed me to fix it whenever I had time.

    That said, if Let’s Encrypt wants to save some money for their free service, I’m certainly not going to complain (although I will miss it).


  • Fantastic! Thank you for sharing this.

    I have it installed, I’m curious how effective it will be.

    Lately, I’ve been reporting AI generated cruft as “spam” to duckduckgo. In fact, it’s not really spam - as there are some nuggets of useful information, but so sparse, I’d rather of skipped the article/website entirely. I hope these kind of Blocklists will evolve to include this kind of quasi-spam.



  • If you do opt for OpenVPN, I believe UDP is generally better for performance. TCP support is mainly there for scenarios where UDP is blocked, or on dodgy connections where TCP’s more proactive handling of dropped packets can reduce the time before a lost packet gets retransmitted.

    It’s great that you brought up TCP vs UDP. And you are totally right about TCP being a bit slower, higher overhead, but it’s there for situations where UDP is blocked.

    I’ve used my VPN at all sorts of hotels, coffeeshops, etc. I’d say 1 in 10 places block UDP (or more likely don’t properly route UDP). If you’re using a SIM card, you won’t have any issues.

    However, it’s worth mentioning that WireGuard is UDP only. There are some hacks/workarounds to have it work over TCP, but then you’re going to need to find WireGuard clients that also supports these hacks (which is possible on computers, but harder on cellphones/tablets).

    If you want something that “just works” under all conditions, then you’re looking at OpenVPN. Bonus, if you want to marginally improve the chance that everything just works, even in the most restrictive places (like hotel wifi), have your VPN used port 443 for TCP and 53 for UDP. These are the most heavily used ports for web and DNS. Meaning you VPN traffic will just “blend in” with normal internet noise (disclaimer: yes, deep packet inspection exists, but rustic hotel wifi’s aren’t going to be using it ;)






  • It’s the “stringing it all together” that could be problematic.

    If you have multiple clients (desktop/cellphone) modifying the same entry (or even different entries in the same “database” ). You need something smart enough to gracefully handle this or atleast tell you about it.

    I did the whole “syncing” KeePass and it was functional, but it also meant I needed to handle conflicts - which was annoying. I switched and really appreciate the whole “it just works” with self-hosted bitwarden.




  • In addition, you can force your cellphone to GSM/2G (ie: super slow internet).

    Depending on what your TV does when it “activates”, if it just needs to “activate/register” - it should be fine. If it needs to “update/upgrade/add a bunch of crapware” - Your internet will be so slow, you can turn it off before it’s finished (note: there is a slim chance that, this could also put your TV in a broken state - if it does, simply do a factory reset and try again)