This thing just makes it easier to dump the firmware, but it's not a revolution or anything. The STM issues have been known about for a while, and with a bit of effort, you can dump it yourself without this or any expensive tools, as I once did: https://analogic.cz/rs41-rpm411/
Cloudflare does not have any IPv4 blocks in North Korea. Geolocation databases use RIPE as the primary source and then make estimates using various tools.
Running self-hosting email is not problem. There is so much solutions to run easily own server these days. But the main problem is that you need a lot of knowledge to do that properly - software might help but it will never be "run and forget" service type.
For example large part of IT professionals which contacts our support (https://poste.io) don't get difference between SMTP envelope and from/to headers.
Also the term “easy” is a terrible trap for any developer to use as a word. Easy would be flipping a switch, maybe one or two easy to remember credentials tops. Something like turning on your smartphone on for the first time.
Heck, like 95% of open source fails in that regard. Hell, anything Linux fails (even though progress has been made, it falls halfway short still)
> Heck, like 95% of open source fails in that regard.
That's a dubious remark. Even proprietary software most of the time fails at being easy. Easy takes great design and most software out there falls into the average.
Open source more often than not is not quality assessed as some commercial products, and hence the UX and ease of use falls behind. So if open source as an ideal wants to be successful, it needs to step in that regard.
Take Blender which was terrible for years and years, but changed happened because the projects they did allowed them to work with professionals which could point out shortcomings.
Or GIMP, its UX is terrible still afaik.
Or lets install Linux, as long as it takes a considerable expertise and doesn’t come preloaded, people won’t switch.
There's a ton of software that succeeds at being easy. NPM for example is amazing - just write a simple package.json file and 99% of the time you have a perfectly portable project which you can run anywhere with a few simple commands.
I have to wonder, is this satire? package.json is notorious for not pinning dependencies by default, leading to unexpected behavior such as dependencies being updated to new minor versions when you run `npm install`, which fails the principle of least surprise.
You'll usually only learn about this after getting bitten by a bug in an auto-updated dependency and at that point you'll learn to manually pin your dependencies and use commands such as `npm ci` instead of `npm install` in your build pipeline.
As such, navigating around the NPM world is anything but easy. There are razor sharp edges and footguns lying around everywhere, just waiting for you to use them.
Easy for “us” developers. If I mention NPM to my neighbor in construction, I would get a vacant stare. No I mean for adoption to take place, the bar needs to be a lot lower.
I used poste.io for one year and switched to mailcow. Poste.io does not frequently update their containers and I had to wait a long time for crucial security fixes. Looking at the docker container tag history verifies this: https://hub.docker.com/r/analogic/poste.io/tags
For only your personal use sure. If you run stack for more than couple users you will sooner or later hit problems not with software itself but with outer world.
That would be a lot more appealing if it explained where the data is sourced from, included the update scripts, and how it is licensed - the only issue asking that question was closed without a word.
FLARM is very bad example especialy for DIY community. They have proprietary chips, firmware and are running non opensourced protocol. Also they are actively trying to prevent reverse engineering with cryptography and killing old/diy devices with protocol timebombs...
These tutorials are nice but you can just hack https://hub.docker.com/r/analogic/poste.io (shameless ad) or any other containerized solution. You will get fully working solution in couple minutes and it will be somewhat easy to keep mailserver updated...
This. I have been running my own mail server since UUCP bang paths and sendmail. I am slowly preparing to migrate to a containerized solution for exactly this reason. Managing the updates of all the parts going forward is just too heavy a load, while swapping in a new container is easy. The initial configuration is painful, just because there are so many options to decide on, but those decisions are all there anyway, whether you realize them on day one or not. I am planning to use this image[0].
