

that’s good to know. when I signed last year I think it was enough to type in my id card’s number and my name and location.
that’s good to know. when I signed last year I think it was enough to type in my id card’s number and my name and location.
898k. I’m very happy this is happening. but I’m worried about how sudden the signatures started coming in, there was a chart somewhere. Hopefully they are valid.
well if they find the drivers, and make the necessary changes from another tablet or phone that’s similar and suported, yeah
well there’s lots of wasted space where the vacuum bag is empty
ok, but this does not help when the connector is vertical, like on the back of a PC, and often the front too. which side is “up”, left or right? on this particular product, of course.
and then comes when you cant see the connector while trying to plug it in.
I have a satellite tracker for when I want to contact radio sats,
which one do you use? can it show where is it on a camera background?
programming socks
you must have lots of LoTs
wpa2, but password limited to 10 characters. letters and numbers only, trying anything else crashes it, and you have to figure this out yourself
maybe the frontend is buggy. did you try with the default frontend?
we need to add cloud connected cameras! oh and AI detection, that prevents you turning it on even if it’s empty, but also if there’s no network or if you need to do your yearly password update
if it don’t complete under a Tiktok I ain’t waiting!
/s
ok, a backdoor then. can they overwrite any file with it?
“that’s the neat part! they don’t!”
fediverse over Tor?
maybe base it on Briar
*federated
with properly limited access the breach is much, much less likely, and an update bringing down an important service at the bad moment does not need to be a thing
it’ll still cause downtime, and they’ll probably have a hard time restoring from backup for the first few times it happens, if not for other reason then stress. especially when it updates the wrong moment, or wrong day.
they will leave vulnerable, un-updated containers exposed to the web
that’s the point. Services shouldn’t be exposed to the web, unless the person really knows what they are doing, took the precautions, and applies updates soon after release.
exposing it to the VPN and to tge LAN should be plenty for most. there’s still a risk, but much lower
“backups with Syncthing”
Consider warning the reader that it will not be obvious if backups have stopped, or if a sync folder on the backup pc is in an inconsistent state because of it, as errors are only shown on the web interface or third party tools
the config and databases or the media, you mean?
if so, the former, but I mount the meadia with a read only docker volume just to be sure, because chances are I would never notice it