Weird. Other than how it used to choke when there were conflicts (and all uploads stopped until that was fixed) I haven’t had any issues like that. Guess I’m just lucky.

I’ve had pretty good experience with Nextcloud’s instant upload. The only time I’ve had it shit the bed was ages ago when it would occasionally get stuck on a conflict, but that hasn’t happened in a long time. Pretty much all of my image folders (camera/DCIM, Screenshots, Downloads) get synced. The only annoying thing was when apps would suddenly change where they download to and I’d have to reconfigure yet another sync folder, but I can’t really fault NC for that.

Mine is set to upload and keep a local copy and only do a one way sync (phone to NC). Not sure if that causes less issues than a 2 way sync or deleting the local copy after upload?

Just defederated from usagi [dot] reisen just in case federation starts working on that end.

Web app, specifically, or any apps?

I’m also familiar with these three (web) apps:

• Alexandrite: https://alexandrite.app/
• Mlmym (Old Reddit Lookalike): Not sure if there’s an “open” instance of it, but several instances offer it. See https://old.lemmy.world/ for an example (not sure if SJW offers Mlmym or not).
• Voyager: https://vger.app/

Might also also check out https://lemmyapps.com/ which has a good list that you can filter by platform/feature.

It does, but I’m talking more about scheduled posts. Many instances require those to be tagged as bots.

Maybe dubvee? That’s kind of the exact vibe we’re fostering.

Site info: https://dubvee.org/site

I’m looking for a instance with…

• the fewest trolls (they’re site-banned upon discovery)
• [the fewest] bots (see rule 2: “No fscking bots”). Some bots are allowed, but only ones that are just a human queuing up things to post on a schedule.
• and anyone that likes to take things to the extremes (See Rule 8)

Cons are that a lot of accounts are banned (rule 8) and we don’t federate with some instances: .ml, grad, hexbear, lemdroid (too much spam originates there). We’re kind-of the opposite of lemm.ee in a lot of ways, so it might be a bit jarring if that’s where you’re coming from.

Yep, known issue: https://feddit.org/post/13613230

Can confirm, but depending on the VPS, your traffic may only be metered in one direction. Mine only meters egress, not ingress, so it’s not too bad if I want to use my media server.

I’m still putting that together, but it’s basically something like:

UPDATE post set url = thumbnail_url where thumbnail_url like 'https://dubvee.org/pictrs/image/%' and url like 'https://lemm.ee/pictrs/image/%'

For the Kbin users to clear out their avatar/banners, I just did:

UPDATE person set avatar=NULL, banner=NULL where instance_id=(select id from instance where domain='kbin.run')

UPDATE community set icon=NULL, banner=NULL where instance_id=(select id from instance where domain='kbin.run')

…and will update that for lemm.ee

I’m working on a Bun/NodeJS script to download the avatars, icons, and banners for all the lemm.ee users/communities, upload them to my pictrs, and then update the DB with the new values referencing the local images.

Prob gonna have to break that up into two steps so I can download and file the images before lemm.ee goes down and upload/assign them after (so they’re not overwritten by federation).

Not sure if I’m gonna do that for comment / post body images. Basically, I just want the archived communities to look nice.

Depending on how the admin has pict-rs (the “subsystem” it uses for media) configured, post images can create local copies /thumbnails for image posts. Some instances opt to do that, some don’t.

Other images like ones posted a comments, user/community avatars/banners aren’t stored anywhere except their home instance.

But yeah, even the limited caching has proven problematic if questionable/illegal content gets posted.

I’m gonna run some scripts on my instance’s database to look for posts that have lemm.ee pict-rs URLs and local thumbnails. Then update the url value to that of the local thumbnail_url. That’ll at least fix them on my instance where I have a copy.

I won’t be doing that until after lemm.ee shuts down, otherwise the original values will federate back in if there’s any activity on the posts.

For comment images or ones where my instance didn’t create a thumbnail, they’ll just have to be broken I guess - same goes for the community icons, though I suppose I could go ahead and get local versions of those and update the communities afterward. Prob also set those to “Mods only” in the database to keep local users from trying to post there.

For user avatars, I’ll probably just clear those in the database so when looking back at old content from .ee, it won’t try to fetch them and timeout/404.

There were less posts to worry about then, but for community icons and user avatars, that’s the same thing I did when kbin shut down.

That’s pretty much it.

Every instance that was subscribed to those communities will retain their local copy of the posts/comments and remain visible. You can even still comment on them, but only users on your instance will see them (i.e. without the home instance for the community being online, they won’t federate beyond your local instance).

The only hiccup is image posts. Different instances have different configs for creating local thumbnails of images, and community icons/banners aren’t cached, so it’ll mostly be text-only copies of the content.

And any comments or posts to other communities by .ee users that have images hosted on.ee will be broken.

All of mine use bind mounts so I can just tar-gz the whole deploy folder for backups and migrations. For volumes that connect to remote shares (SMB, NFS, etc) I use named volumes and let Docker take care of their lifecycle.

If named docker volumes would let me specify the local filesystem location, I’d use them. As-is, I rarely do.

Sorry, I had to meme this thread:

As well as can be expected, all things considered. Hope the same to you.

I just like that it’s smaller. Like, you can actually have conversations (or slapfights :sigh:) and can actually recognize people. Kind of like something bigger than a small town but smaller than a huge city.

I’m not opposed to growth, and it would definitely be a good thing in the long run, but I like that it’s not just shouting into the void here.

Yeah, maybe add “[Satire]” to the title because it reads too much like every other AI-bro press release lol.

Counterpoint: Good?

The fediverse has no global identity system. Just like how temporary email addresses protect YOU from spam, disallowing them protects volunteer-run services like Mastodon, Piefed, Lemmy et al from spam (and trolls, etc).

I do not approve any registration applications from throwaway email providers. Also, volunteer-run services are much less likely to use your email address for nefarious purposes. Data breaches are another thing, but TBH, most of the spam I get is from spammers just spraying out to anything that’s formatted like an email address. Not sure about Mastodon, but Lemmy and Piefed do not reveal your email address to anyone (admin can only see it during singup and in the database). At least in Lemmy, the passwords are hashed, but the standard advice to use a unique password per service applies so that in the event of a data breach, the email+password combo will only compromise that single service.

I guess the moral of the story is to save the tinfoil hats for BigTech™ and show the Fediverse people, who are trying to do better, that you’re here with good intentions. As an admin, I’ve seen more spam, trolls, and n’eer-do-wells signup with throwaway emails than people who are here because they want to be here, and to a severe enough degree that I will no longer accept registrations using such services.

Then you really should list all of the secondary functions you plan to add to it, make sure they understand what those are, and agree to each of them: full disclosure.

If you do something on it that could get them in trouble, it’s their ass on the line, not yours.

Are you friends okay with you doing that? I would not be, especially if my so-called friend didn’t disclose the secondary operations of the device that’s in my home, on my internet connection, under my name.