gerbilOFdoom

From a theory perspective alone, ignorant of Lemmy specifics: a database query can be made to list all cached images including a unique identifier for each image. Use this list to find each cached image.

Look at your cached image list and decide how you want to prune it. The most likely pattern for this system is FIFO, so prune the oldest cached data until you drop below the target disk usage.

In practice, you'll likely use somebody else's solution. Be sure to read the contents of their solution carefully to ensure it doesn't move sensitive data to an externally accessible location or exfiltrate data directly.

As a workaround: I think GrapheneOS let's you sandbox apps, including Google apps. You might install the standard Pixel camera in a sandbox and see how it performs.

Risk in this setup should be minimal due to the limited access the app would have.

Old software that can actually be superceded by some newer tech if someone feels like doing so.

Easy to use, lots of documentation. 10/10

I've found that for single person purposes, a RAID array is unnecessary. I just buy beefy 8TB drives. If it dies, just download any recent torrents again or pull a backup

So, you can work around these things but you're going to run into problems if you do:

-If you reset the router, you need to restore the original password else they'll know

-if they notice you using these devices when you wouldn't have access, they'll remove them further from your reach. Possibly permanently.

-If detected, a larger conflict is likely to be escalated. This includes a loss of the benefit of the doubt in the future.

I'd suggest that this is not the battle to fight. They're likely fighting your apparent obsession with tech. Let them have this battle and continue your fun later.

Try the Stormlight Archive, wheel of time, or mistborn books. Maybe the redwall books if you're younger. Fun and focus can still be had without a computer!

Oooo thank you for the links, that's the part I had a difficult time with. I don't think I'm subscribed to enough things, or I don't check frequently enough, to get the information updates.

I'll see what I'm qualified to do. I don't know Rust in particular so this is likely to turn into a rabbit hole that produces nothing but a greater knowledgebase in my brain for the next time I get fiesty about something.

I think the reason they'd need to do a thing in a pressed timeframe is that, while psychohistory describes populations over time, sufficient understanding can allow someone to make a relatively small tweak that ripples through time.

I've been spending some time considering the future technology stack of Beehaw. I'd love to work on some kind of moderation tools, especially because I know that they could be inserted alongside the existing codebase - even if in an exceedingly hacky way. Heck, even client side site scraping with content matching is an option if for some horrible reason we had to.

The fun part is not being able to ask those who run the server about specifics for what's needed.

Computer Science student here.

Forking Lemmy does fork its bad habits but doing so would at least give us the option of making direct improvements to the mod tools.

From what I've read, causing deleted content to get deleted quickly is a smaller change. Advertising that shortened deletion delay and giving the admins a "these keep our shit, yeet their federation privileges but check again every day and notify me when that changes" script wouldn't be too hard to create.

We might even be better off ignoring the Lemmy codebase for mod tools altogether. If we outright ignore cross-platform compatibility, we can make a mod tools API independent of Lemmy-proper that does what's needed and a JavaScript-controlled interface to sit on top or a separate toolset altogether.

I'm pretty busy right now but I rely on Beehaw for decent social media. I'd be willing to put a bit of time into it.

This is the most bougie hamster I've ever seen

The point of a digital signature is to announce that you made this document, as it exists at the time of writing. Once a change is made it should no longer identify as signed.

Most institutions don't use this functionality, despite the usefulness of it. At present, I'd recommend using it for publicly distributed files to protect against bad actors publishing a document that pretends to be yours.

As for legally binding, ask a lawyer. Generally, things are legally binding if they're signed by all parties. The specifics get funky, but a digital signature is a solid step for announcing that you did this thing at this datetime and a judge should recognize that if it comes down to it. Bonus points if all parties attach their digital signatures.

Whooooops, that's what I get for not verifying things sitting in my brain for a long time