The RPI is sort of the exception; I have a couple of them doing odd tasks around the house like displaying security cameras, but that's an outlier due to the massive amount of support it gets.
In boxes in the basement are all sorts of SBCs, from the original A10 Cubieboard from 2012, to many Hardkenel boards, to all sorts of bizarre barely operational SBCs from various sources. They all had the same issue of being basically unsupported unless you made it your life goal to dig through obscure datasheets and compile kernel patches from some forum post you found.
A good holistic replacement for the RPI is the APU2, a x86 board of similar cost that has a bunch more peripherals, real support for booting from SATA, ECC memory, and that sort of thing. Absolutely no video support, but I have years of uptime on the things with no issue.
They usually perform well, but get put in a drawer and forgotten about because the software compatibility is generally atrocious. Peripherals advertised generally never work, but you know, might in a future kernel. I've been burned enough that I've sworn to never buy a SBC no matter the specifications.
The website linked, and it's associated information all absolutely scream red flags and is functionally similar to a hoard of other schemes. It's a technically simple product (distribute binaries from a webserver) with a completely arbitrary cryptocurrency stuffed onto the side, allowing for bombastic, buzzword filled claims which just defy reality. It attempts to promote itself by driving users who will get some form of profit sharing as part of their participation, promising some sort of rewards paid by the creator.
> Package maintainers will publish their releases to a decentralized registry powered by a Byzantine fault-tolerant blockchain to eliminate single sources of failure, provide immutable releases, and allow communities to govern their regions of the open-source ecosystem, independent of external agendas.
It's existence is an attempt to justify the creation of yet another cryptocurrency, not as a serious solution to any problem that exists in distributing software.
> Upon successful submission of a package, the package maintainer will receive an NFT to evidence their work and contribution. The holder of this NFT will automatically receive all rewards associated with the package. Package maintainers may transfer maintenance ownership over a package to another package maintainer by simply transferring the package’s NFT. Successful transfer of the NFT will lead to the new owner automatically receiving future package rewards.
I want literally nothing to do with a cross between a binary distribution tool and a cryptocurrency pump and dump.
GNOME isn't even a fraction of the problem, desktop linux is absolutely unsuitable for day to day use and that's nothing to do with the desktop environments. The foundational design decisions of the way applications are rendered in linux means that every experience is inconsistent, nothing even has the same file picker and it's always a surprise to see which one is thrown in your face in any given situation. This sort of inconsistency is ripe throughout every part of linux, everything works so long as you make it your full time job to work out what the incantation is to enable basic convenience features.
Feels sort of nonsensical honestly. Credit card anti fraud is entirely reactionary, there’s no magic bullet, you’re just papering over the cracks of an absolutely broken payment system. Every service will see different fraud, it will always be changing, there’s no one fits all solution. Very frequently the “rules” of the systems aren’t solid and everybody trying to exploit them knows that.
There's ways around medical inadmissibility, you can absolutely get around the cost threshold by proving your ability to cover the cost- so long as it isn't a personal guarantee. It's sort of a nightmare, you have to apply for PR, be denied, and then there's a one time appeal process. Talk to a lawyer about it if this is your actual plan, because they know more than I ever will.
You don’t see that because it just isn’t supported by what people make. No laptops are going to provide PD power outputs at relevant voltages because they would need to have a huge amount of switching circuitry for a situation that is not strongly user demanded. Spotty support means products are never built to expect it to exist, and we continue with all the problems of USBC being borderline unusable for what you would expect to be simple tasks. PD is a bag of hurt at the best of times unfortunately.
It’s something akin to a layer violation to have a database server running openssl and encrypting its own communication. It isn’t it’s business at all.
Who cares though? All connections to SQL servers are going to be localhost or over a VPN, if your setup for postgres has a SSL certificate you're doing something terribly wrong to begin with. I'm not even sure why the option exists to begin with, there's no use case.
In boxes in the basement are all sorts of SBCs, from the original A10 Cubieboard from 2012, to many Hardkenel boards, to all sorts of bizarre barely operational SBCs from various sources. They all had the same issue of being basically unsupported unless you made it your life goal to dig through obscure datasheets and compile kernel patches from some forum post you found.
A good holistic replacement for the RPI is the APU2, a x86 board of similar cost that has a bunch more peripherals, real support for booting from SATA, ECC memory, and that sort of thing. Absolutely no video support, but I have years of uptime on the things with no issue.