The worse kind of technology is one that promises things and then delivers only 80% of the time. It works enough that it gives you hope that it is usable, but when you need it the most it fails without any way knowing why. Also Bluetooth is a security nightmare, every few months there is some serious problem found and many of them are “by design” so cannot be fixed properly. It is also use for location tracking (beacon).

Wired headphones are like 100x cheaper, don’t require charging and will work for many years if you get one with good cable. There are only few failure modes that are easy to troubleshoot. But cable management can be a pain if you are not tidy.

Good. In the meantime my GP asked me to send my medical data to theirs @gmail.com address… long way to go.

In the mean time 15 Ukrainian Soviet/Russia design reactors were connected to Central Europe grid.

What would also extend life time of smartphones is the ability to replace the battery! But I guess this is just too radical of an idea for present day.

Nice they are able to get the most from the battery lifetime, that also helps to reduce waste.

I think the inspiration behind uxn is game “Another World” which was made very portable as it is actually implemented as a VM: https://fabiensanglard.net/another_world_polygons/

The idea is that if your work is implemented on a VM that is very easy to implement. Then you can port all your programs to past and future computer systems by just implementing that VM on the computer you have at hand. This is the “permacomputing” part of uxn and has nothing to do with reliability or performance (although Another World was quite impressive as for Amiga 500).

Another thing is that uxn was designed with games, arts and music in mind and not with replacing life critical systems with.

Would be a good article without the uxn part. I think the author confused uxn with RISK-V or something.

“C was originally developed at Bell Labs by Dennis Ritchie”, this all adds up now :)

Was lack of overflow checks, no buffer bounds checks, weak error handling and null terminated strings a CIA con job? :D

So integer underflow, no bounds checking on buffer read, ignoring error codes, null terminated strings. Classic C :)

Good, let’s hope more will follow. If your business needs to know where I am, perhaps you should ask and I may tell you?

I did not try them but perhaps you can check:

• https://lib.rs/crates/unqlite
• https://lib.rs/crates/leveldb

I was hoping for BerkeleyDB or Kyoto Cabinet bindings that I have used in my Ruby times for this purpose but nothing there that looks maintained.

Yes it can. This (among many other reasons) is why privacy matters. Even if you have noting to hide today, law can change and now data that is collected can be used against you.

a decentralised finance protocol that acts as an exchange, lost out to “the recent insolvency of two large centralised entities”

So what it says is:

• we will spy on you and sell data collected to unknown third parties for our profit, or you can’t use the TV
• you don’t own this product and we can take parts of it’s functionality away from you at any time for any reason
• we will make more money off you by selling ads directly to your screen based on data that we have collected on you to maximize our profit and effect of advertisement on you and your family for our partners gain

No one could have predicted. /s

Now it is time for Europe to be able to make this core component of its economy and society.

GPUpocalypse is coming :) (when $15b worth of GPUs are dumped on second hand market duet to cryptocurrencies collapse or them not begin financially viable for mining any more)

I also can’t get there with Mullvad VPN on.

Yeah, still the case. Even if ME is not made for malicious purposes, it is a very bad idea to begin with. It is only useful for enterprise customers and not in a way that would not have been possible before.

Some say that Netflix has a blob in ME :)

Good watch: https://media.ccc.de/v/34c3-8782-intel_me_myths_and_reality

Well, I switched to Wayland (sway) exactly because mpv could not do vsync with X11. So I guess frame callback is how you get vsync working by default and client timing loop is how you get no vsync by default. And getting the other than the default thing is always a major hack - in last 20 years I wasted days trying to get X11 do proper vsync and it never really worked and probably will never do work.

Another think is that in one paragraph the complaint is that Xorg supports to many features and on another that Wayland is slow to adopt and requires justification for adding more features… so have cake and eat it too?

Also please don’t complain about missing features when you know they are not there just because the thing did not get all the development time the other thing did… unless stuff is broken by design/culture (like with the scale factor it seems).

You could use system like SQRL (https://sqrl.grc.com/pages/what_is_sqrl/) for login that does handle “password” resets without email.

You could use argon2 to hash the email as well, you ask user for email on “I forgot my password” page, argon2 it and compare (like with password). At this stage you will know the email and that is the same as set during registration, to send the reset code.

Got it through invidious download :)