but dozens a minute increase in the dawn hours?

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

well there’s lots of wasted space where the vacuum bag is empty

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

ok, a backdoor then. can they overwrite any file with it?

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

that’s horrible and funny at the same time.

I will assume they fixed that vuln later

that’s probably way too much for any sane Python algorithm. if they can’t run it, how do they even know how much is needed?

Probably they should only make a prototype in Python, and then reimplement it in a compiled language. it should reduce the resource usage massively

yeah but it turns out a lot of my lemm.ee links are not actually to content that’s originating from there, but lemm.ee-view links for which if I search, there’s no result.

Fortunately I also have the title and image permanently loaded for these links, so I can find them with some manual work

how do you know it’s working if you can’t connect?

if you run the server on your computer, did you set up the port forwarding? does it work if you just connect to localhost, or the local ip of that computer?

I guess this way people often just think that higher number is better, even if only subconsciously, and people will more often by a newer phone. but single increments like with the generation don’t have the same effect if the numbers are already large, and if they would use the release year maybe that wouldn’t have this effect on sales because people know it’s just the year. and a change from 2024 to 2025 does not seem to be so big as from 5 to 6

It’s mostly not because of instance shutdown though. especially on lemmy, because lots of posts are readable elsewhere after shutdown.

It’s not all the lemm.ee posts, just a significant amount of them.

also in the meantime I realized my hundreds of lemm.ee links are not actually links to lemm.ee hosted posts, but just links to the lemm.ee view of them. I was just very often copying the wrong link that still worked, but wasn’t the definitive one

hmm that’s interesting because I did not have a lemm.ee account! :D just 3 tons of links to it.

edit: I misunderstood it, no I didn’t have an account there

also in the meantime I did some research. it turns out I was probably remembering the Lemmy Universal Link Switcher userscript: https://greasyfork.org/en/scripts/469273-lemmy-universal-link-switcher

it can look up posts by their activitypub id, which is the de-facto ID of a post, that is same across all instances. this ID is the url of the content on the original instance. so, the following could be an activitypub id, if the post was actually created on lemm.ee: https://lemm.ee/post/64477597

to look up a post by this, the userscript uses the /api/v3/resolve_object API endpoint.
it searches your local instance, and if you are authenticated it also queries the host in the url, lemm.ee in this example. but of course this remote query does not work anymore.

now here comes the twist. I know I always read lemmy through sh.itjust.works, so whatever I saved should be known by this server. and the link that I save, often does not point to the origin instance, because clients work that way.
so it seems 2 lemm.ee links that I tried to look up were not actually posted there, because bmy server does not know a post that has this ap id, I just somehow got a link that points to the lemm.ee version of that post or comment…

Fortunately the messaging app I misuse for link collection always loads the title and image of the webpage, so by some manual work I should be able to find the actual links to each of them.

speaking of that, there was a userscript that is able to find the same post on other instances. I should look it up, in case it can also work with posts of offline instances

you can delete the calendaring and contacts apps

snapshots, clones, or automated setup with ansible or such

what do you mean by off network? on the wifi of a different home’s network, that has internet access?

the wireguard client on your laptop is supposed to give the laptop (and the laptop only) access to your home network, and the reverse proxy running on the laptop is supposed to give local devices access to services at home selectively, by listening on port 443 on the local network, and processing requests to services that you defined, by forwarding them through the vpn tunnel.
this requires that a machine at home runs a wireguard server, and that its port is forwarded in your router