Half a century of dither and denial – a climate crisis timeline
The physicist Edward Teller tells the American Petroleum Institute (API) a 10% increase in CO2 will be sufficient to melt the icecap and submerge New York. “I think that this chemical contamination is more serious than most people tend to believe.”
Discord post-mortem from a cloud engineer on the outside
Hypothesis is a good idea but it is a centralized service (as far as I can tell).
Haven't looked in depth but dokieli looks to be a worthy replacement:
"Decentralised Authoring, Annotations and Notifications for a Read-Write Web with dokieli"
(Wow that's a big font)
Times I've invoked Google Chrome's "Pull to Refresh" page:
Times I've done so intentionally:
Times I've lost state invoking Google Chrome's "Pull to Refresh Page":
Times I've wished Firefox's Android performance was sufficient to be able to ditch Chrome:
Times I've wished for a viable tablet full-Linux Android alternative:
@alcinnz I mean, Usenet had MMF:
My general view is:
- Focus on *behaviour* rather than *features*
- Recognise that *complexity* enables both more bad behaviour, and can mask it.
- Reputations matter. Rather than identify *content*, track the *creators*, both good and bad.
Effective trust networks tend to be *small*. A few tens, *possibly* hundreds, of actors. Trust scales poorly.
For those who don't know the difference between the different kinds of memory usage on Linux
Virtual memory is a measure of how much memory - real and "virtual" - is mapped into the process space. This can go up without increasing the memory pressure on your system by doing things like mmaping files.
Resident memory is a more accurate measure of your application's use of RAM. The etymology is a little bit dated, but basically this is how much RAM your program takes up when it's not the active task. If you want to know about RAM usage, this is the only thing you need to look at.
Shared memory is that which is currently or theoretically possible to share between processes, such as shared libraries or shm files.
My ideal (and probably impossible) future of tech is a world where everyone (or every household and business) owns their own server(s) (maybe colocated?) that runs all their stuff, like document sharing, IoT/"smart" devices, social networking, Web caching and searching, etc. etc. and everything is federated so everyone can still interact with each other.
There are things we can do to make this more feasible, but I don't expect it to happen easily or anytime soon.
As always fair, insightful, accurate and without necessary hype. Jan, Dalton and Marius from @UBports discuss the #PinePhone on their Q/A. If you have time, watch in entirety, if not click video below:
Seeking refuge in a distributed world. Web, future programming. Building things.
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!