

I can barely get 3G
That’s astonishing, because I read that 3G was shut down 4 years ago in the US.


I can barely get 3G
That’s astonishing, because I read that 3G was shut down 4 years ago in the US.


PWAs can use local storage and they can have service workers, which allows them to run offline, at least in theory.


I’m using Keepass2Android (and KeepassXC). It can copy the database from/to an sftp server, so it can easily merge the entries. I don’t have the sftp server exposed to the Internet, because when I’m not home, nobody will change the database at home.


I just read that Google has abandoned the Coral TPU.


But with 800 MW it takes an hour and a half to get to 1.2 GWh, and an hour is 3600 seconds or 3600000 ms. So “a few” is doing a lot of work in that quote.


I see several options that start with >--, like --env=MOZ_APP_REMOTINGNAME=Personal - are these copy and paste errors or is it a special syntax that is described somewhere?


Keywords that you can put into your favorite search engine: archive.is ddos.


I got used to ip --br a recently.


But the US can impose a few inconviniences on you:


The article links to https://devblog.qnx.com/qnx-self-hosted-developer-desktop-initial-release/, maybe they don’t block your region.
Keepass2Android can use an sftp server. If something was changed on the desktop, Keepass2Android will ask if it should merge the changes.


Sure, just break millions of other people’s scripts on a whim.


Don’t forget the OpenDocument format of LibreOffice and the other format of the other office suite. Yeah, these will be retired any day now.
Also these.


Yes, facebook is running on a web server and the app (or a browser) is a client.


Some big-endian architectures are supported, but not RISC-V:
A related problem is big-endian support, which is also 32-bit only, and also obsolete. Its removal is blocked because IBM is still supporting big-endian mainframe and PowerPC systems; as long as that support continues, big-endian support will stay in the kernel.


But what would that help in this situation? You could as easily write result = asize; and the psize would again be unused.


I’m almost sure that ./ is the directory of the compose.yaml.
Normally I just run docker compose up -d in the project directory, but I could run docker compose up -d -f /somewhere/compose.yaml from another directory, and then the ./ would be /somewhere, and not the directory where I started the command.
In case anyone wonders: these are the same bugs reported (and fixed) last week, not new ones.


There are also some SAT receivers that run Linux, see e.g. https://www.opena.tv/app.php/atv_images
20 years ago we had only GPS, and it already was accurate to 10 or 20 meters.