I live in Brisbane, Australia, the third most populous city. I can confirm that there are areas in Brisbane (not even "Greater Brisbane") that barely have mobile phone reception, such as Burbank on the eastern side.
DAI isn't so much a derivative of Ethereum, rather it is a dApp (decentralised app) that runs on the Ethereum smart contract technology.
ERC-20 tokens are the magic that enable second-layer "currencies" such as DAI and others to work on top of Ethereum. There are other tokens, even WBTC (Wrapped Bitcoin).
DAI itself is backed by a basket of token-based assets such as WBTC, WETH, USDC, USDT etc.
The Ethereum dApps are definitely a fun rabbit-hole to dive into, e.g. UniSwap, Synthetix and other DeFi applications.
The main problem as I see it is the transaction costs are very high (I looked into using UniSwap but it was going to cost > $50 to transact what I wanted). However, in the next few years the Eth2 improvements will help scale the network and hopefully see transaction prices fall.
Depends on your use case. XML and JSON are great for applications with simple data stores, having done this myself. But if you foresee a need for complex queries or locking and threads then SQLite might be a good choice.
Elasticsearch is now being released under a proprietary license. The last FOSS version got forked by Amazon. This is a good thing if you care about software freedom. Sure, under Amazon it may be a "throw over the wall" model but at least there are open opportunities for the source code to be forked again, and in the meantime at least it's being maintained under an FOSS license.
Really? Most people who use Firefox are still exposed to tracking. Google is still the default search engine and promoted via Firefox Home, and continues to track the large majority of users who don't change their default. Pretty sure Facebook and Twitter are promoted via the default home page as well. Third party cookies, browser profiling and other tracking mechanisms have barely been addressed. Mozilla seems more focused on lip service, shameless self-promotion and double speak than addressing the problem. The so-called free web is a joke, it's a web of giants, and companies like Mozilla who are mere pawns in their protection racket.
Some of us believe that the client-server model has led us to the current situation, ruled by internet giants. A future where people are less reliant on giants is within our reach, the biggest hurdle is making it available to the masses.
Hopefully uptake by non-mainstream browsers like Brave will increase the exposure, attract developers, increase the network and get us closer to having IPFS, Hypercore or some other protocol available to the mainstream, whether that be in Firefox or by some other means.
Besides, you could argue that browsers have added plenty of fad technologies over the past few years, DRM comes to mind.
> IPFS, Hypercore or some other protocol available to the mainstream, whether that be in Firefox or by some other means
TIL about hypercore! Looks like an interesting concept based on append-only logs. It reminds me of this work being done at VMware: https://github.com/vmware/node-replication
Debian Buster LTS is supported until 2024 and then probably ELTS until 2026. Also how many of these 32-bit Atom CPUs are actually in use anymore? It's a pretty edge case.
I run my home automation on atom. Considering that cost of asus eee pc is around $70 it still is a lucrative option of a complete system compared to raspberry.
Debian is (or at least used to be) popular for old hardware - e.g. they supported m68k for longer than most distros. I had an i386 Atom netbook that I was using up until about a year ago, and if I hadn't moved internationally I'd probably still use it.
Some of the highlights (from my point of view) that have been frozen, according to the packaging website:
Linux kernel 5.10
gcc 10.2
libc 2.31
Perl 5.32
And some non-essential packages that look to being included in the upcoming release (I'm sure there's plenty of other exciting inclusions that I've missed):
Which website are you looking at? The release notes I saw said Bullseye would use the 4.19 kernel. I expect them to use a LTS kernel, so I'd be a bit surprised if they choose 5.10.
