Air quality scientist and data engineer

I make stuff

https://symbol.fediverse.info/

  • 6 Posts
  • 59 Comments
Joined 2 years ago
cake
Cake day: December 27th, 2022

help-circle






  • I’ve been focused, lately, on separation of concerns. Yeah, using FOSS tools is great, but I’m also asking myself how much losing a given tool will impact me if I start to rely on it.

    This past weekend I finally broke away from ProtonMail. After what the CEO has been saying, and because of other annoyances like being unable to use anything but their clients, it was finally time to rip that bandaid off.

    Unfortunately, I made the mistake of using a standard protonmail.com email address, so now I have to tell everyone to stop using that. Also, I was a heavy user of SimpleLogin for creating email aliases for basically every service I signed up for, and now I have to switch all of those.

    I should have learned this lesson when I left Google, but this time I will be using my own domain. I also took this opportunity to leave Cloudflare entirely.

    Now I have a domain for my email address and my website through porkbun, but can transfer that to another registrar if they start to suck.

    I use desec.io for my DNS needs instead of the built-in porkbun DNS tools to make it easier to switch to a different registrar if I need to. They’re a non-profit, and it’s open source software that I could potentially selfhost in the future. This also replaced Cloudflare.

    I use fastmail.com for the actual email service, which let’s me use the apps I like on my phone and PC to interact with email the way I want.

    Fastmail also has a service like SimpleLogin, but instead I went with addy.io (also FOSS; also potentially selfhostable) with another custom domain at porkbun.

    My website is a blog hosted by write.as, which is, again, built around FOSS and selfhostable software.

    All of these pieces can be swapped out without affecting the others if need be, bringing switching costs to near-zero, and making it very customizable in the process.



  • I agree that the guide is VERY unclear. The documentation here is a bit better, but still bad and mentions a monthly cost for DIY devices instead of a one-time dev-level API key cost.

    The gist is that if you want to use their servers and you bought their device, they have an API key built in to the device for their non-dev-level API access, and it’s not supported (maybe also against API TOS, but I’m not sure) to extract the API key and use it when you flash custom firmware. Getting the dev-level API key doesn’t have this issue, though, because they give that to you when you pay for it.

    When modifying the firmware to use on your own server, you don’t have to pay them anything because you won’t be using their API.



  • It sounds like you want more of a read-it-later tool like wallabag that saves the link and parses + saves the page content. Wallabag in particular is open source, self-hostable, has browser plugins and phone apps, and allows for full-text search.

    You could maybe use an AI tool for this, but it would be a massive waste of resources (even with deepseek) and would only approximate a search engine.







  • I love open source.

    On a related note, open source projects that get big without a reliable leadership organizational structure risk burning down just as easily.

    Recently nix, wordpress, and gaggiuino were affected by this kind of thing. Nix seems to be recovering. Wordpress doesn’t look good. Gaggiuino skipped right over source-available and went closed-source.

    Linux is a success story with this structure, but I think we need to be better about building projects with stability in mind.