The only thing I really miss is doing data calculations in Google because I have shitty Internet and I want to know how many hours I’ve gotta let this thing download before I get my bandwidth back.

At this point, the community is clean. So unless more is posted, then you should be good. If someone searched for the community and caused a preview to load while the content was active though, then it could be an issue.

From what I was informed, purging a post doesn’t remove the associated cached data. So I didn’t take any chances.

Not really. You could technically locate the images and determine precisely which ones they are from their filenames, but that means you actually have to view the images long enough to pull the URL. I had no desire to view them for even a moment, and just universally removed them.

As mentioned in my edit above though, ensure you are in compliance with local regulations when dealing with the material in case you have to do any preservation for law enforcement or something.

I’m on 1.18.4, once I deleted the most recent images, the former CSAM posts(among others) became broken images. So yes, it was pulling from local disk cache. Then I took care of the posts themselves after the content was invalidated.

Reminds me of Obsidian, which is what I use for notes. But obsidian isn’t selfhosted. I might actually host a copy of that because it’s cool

You can host a webmail like roundcube or similar. I don’t know if they can be turned into PWAs with phone notifications though.

Nah, you can often move around games on external drives from computer to computer just fine and they’ll typically work.

For my instance, I already have an MXRoute account that I use for my personal email, so I just set up an account on there and pointed Lemmy at that. I’ve been down the road of self-hosting email, and it is a dreadful experience.

Granted, that was with full inboxes and POP3, just hosting the send part might not be so bad. But then you have to contend with possibly being on spam lists, and those are hard to get yourself removed from. If you have some cash to let someone else deal with that headache for you, I fully encourage taking that route.

Sorry for the confusion, but Moe isn’t my last name, just the jamie part. I also own jamie.tools and jamie.today.

I’m on jamie.moe, I like to collect domain names that are just my name.

Any VPS provider worth their salt will have corporate clients with data far more valuable than a random person’s vacation photos. So they probably don’t want anything to do with that data unless it brings them legal trouble. Plus, not knowing can help shield them from all sorts of liabilities.

Possible, but I don’t see it happening. Postgres provides functionality that MySQL/MariaDB don’t, so if a lot of that functionality is used, the primary devs probably aren’t going to want to take on the extra overhead of maintaining and testing it. In those cases, it would require additional rewriting on the Lemmy side to make it work seemlessly. A fork could likely do it, though.

I’m using it now, it seems to be working really well. One thing I would probably suggest is adding the ability to list community names not to add. For example, on my personal instance I wasn’t really wanting “Piracy” communities, since they could federate infringing data to my instance. But piracy communities are fairly big, so I need to go back and prune them out.

Update: Did a -f watch of the logs for WARN messages while upping worker counts. Seems 1024 was the sweet spot. Upped further to 1500, and the warnings for expired headers have entirely stopped in large part. So it seems this was the solution.

Thanks for your help!

The machine is a dedicated server with 6 cores, 12 threads, all of which are usually under 10% utilization. Load averages currently are 0.35 0.5 0.6. Maybe I need to add more workers? There should be plenty of raw power to handle it.

Pretty much, that would force federation. Though I don’t think users in the other community would see your communities until someone from there searched one of yours.

An idea I have is giving small communities an option to run the bot on their instance, and it would add them to a list. Then, communities voluntarily participating in that list could auto-populate each other’s communities through the bot. I could see spammers abusing something like this to try and flood feeds with garbage content until they’re defederated though, especially on instances with open registration, so there is a downside. But that’s something the community of proper users will need to be prepared to fight down the road.

I’m working on a Rust API wrapper around the existing common API to make it easier to use. Implemented the calls that could let someone do this exact thing at scale last night.

It’s nowhere near ready for production and is still missing a lot of basic API functionality even for a simple bot, but I think it’ll be ready to publicly release in an alpha state within the next couple days.

Yeah, I mentioned on another comment that storage space is the last thing to worry about, 1GB of storage is typically a fraction of a penny.

It stores them on a local pictrs server and pulls them from there, which, to my understanding, holds them for a week.