Nothing4You

to add to that, Lemmy currently does not handle site bans well if it’s not a home instance ban, as instances don’t keep track of which other instances have banned which users. this should get better with 1.0 though, as a PR to improve that was recently merged.

for now, there is a band-aid solution that federates community bans for all communities local to the instance the user got banned from, but that only includes communities that the user previously participated in, so they’ll still be able to participate in the local copies of other communities from the instance they’re banned from, it just won’t fully federate out.

it’s also the case for deletions without account deletions, but iirc there is some delay before it gets rewritten in the db to allow the user to undelete it for a bit of time.

only admins can set communities to hidden currently. this is also not exposed via lemmy-ui, it has to be done via API.

they’re using my federation exporter as data source.

it’s just scraping the federation api every 5 min for each included instance and then visualizing that.

there seems to be a codeberg mirror but it’s not updated continously: https://codeberg.org/LemmyNet

instances get added automatically once they reach a threshold of monthly active users. iirc it’s >6 mau, you could check the code to confirm.

Removed by mod

Removed by mod

the mod got banned from blahaj, which, when set to also remove their content, removes communities they’re head mod (or only mod?) of as well: https://lemmy.blahaj.zone/modlog?page=1&actionType=ModBan&userId=124892

that post on lemm.ee in your first point is dead

you shouldn’t reuse domains on the fediverse for a new instance anyway, subdomains are fine though: https://programming.dev/comment/14173239

I’m pretty sure it’s doable but it might be necessary to become a mod first, which admins should be able to in remote communities as well iirc. it’s just that their mod actions won’t federate.

based on the creation date advertised by the instance, lemmy.ml exists since 2019-04-20. lemmy.world exists since 2023-06-01.

on lemmy, people blocking you will only hide your content from them, it won’t prevent you from seeing theirs.

I think my grafana is newer and stuff is deprecated

that’s unlikely, i’m running 11.2.4 currently.

yes, you’ll need to run that exporter against each instance you want to be monitoring.

my setup looks more or less like this: https://github.com/Nothing4You/grafana.lem.rocks

depending on the grafana version you are using you may be running into this bug though: https://github.com/grafana/grafana/issues/96356

Then I generated sql statements to remove duplicate posts that had higher ids than the other posts theyre a duplicate of

i assume this was done after updating the other tables referencing this table, such as comments, votes, saved posts, as previously discussed on matrix?

while it may be omitted here for simplicity, it can be dangerous to not mention that for others that might find this in the future if they experience index corruptions on their own if they don’t fix all references, as that would result in data loss.

you can find your user info in the /api/v3/site response. the /api/v3/user endpoint requires a name or person id.

i recommend checking out https://join-lemmy.org/api/classes/LemmyHttp.html

you can only set a community to only allow local users, not prevent users from interacting with remote communities.

you’d have to either disable federation or set up a script to automatically remove all remote communities, but that also won’t be a per user thing, just a per instance thing.

unfortunately restarting fediverse software on the same domain doesn’t really work well with all other software and without local fixes.

activitypub uses cryptography for authentication and there isn’t a standard for changing keys / reusing identities, so different software will deal with this in different ways.

reusing URLs for posts and comments is even more problematic and will definitely cause broken federation with other lemmy instances as well.

if it was decided to recreate an instance from scratch in the future that’d best be done on a new (sub-)domain.

if the database was saved it should work just fine to rebuild the instance from that, it’ll probably just take a few days to restart federation everywhere.

I’m not suggesting either way, just providing some technical background.

You basically can’t if your instance was set up before 0.19.4, as there won’t be any association between users and uploads for older uploads. You also can’t do this without breaking thumbnails everywhere unfortunately.

The latest Lemmy version has a fix where thumbnails now are actually stored at a reasonable resolution for thumbnails, but old thumbnails may be quite large, and this does not retroactively shrink older thumbnails.

It’s possible to pull image aliases from the DB and ignore them when iterating over aliases within pict-rs, but you these will only be manual uploads, not automatic uploads like generated thumbnails. For posts by local users, deleting thumbnails will also end up breaking them for 0.19.5+ instances, as they should reuse the original thumbnail url.