Nothing4You @ Nothing4You @programming.dev

Posts

0

Comments

129

Joined

2 yr. ago

the lemmy backend was supposed to mark posts in NSFW communities as NSFW automatically going forward, which is why the UI option in standard lemmy-ui was removed to mark a post as NSFW if the community is NSFW.

unfortunately while the UI change made it to 0.19, the backend change didn't, so currently people posting in NSFW communities from 0.19.11 lemmy-ui will not have a choice to mark their posts NSFW.

see https://github.com/LemmyNet/lemmy-ui/issues/3114

it should cover all federated actions.

any instance admin can decide to ban you on their instance or remove your content on their instance, but unless it's a local community or they're mod of the community these actions won't federate and will only apply to that specific instance.

the most useful one to look at is generally the one on the user's home instance, as that should list all actions that federated.

instance bans currently generally don't federate and won't show in the modlog of your home instance, but recent lemmy versions are automatically issuing community bans for all communities on that instance that you participated in.

they won't be sent by infosec.pub directly, but other instances may send activities referencing content from infosec.pub, which will lead lemmy.ml to pull it from the source as well.

this includes for example posts and comments in lemmy.world communities, because lemmy.world will announce those to lemmy.ml.

lemmy has an image proxy feature, but it doesn't seem to be enabled on lemm.ee currently. it also still has various issues where media may break, it should get better in future lemmy versions (probably only in 1.0, not in 0.19 versions).

some alt uis also have the option to proxy images if enabled by the person hosting it, e.g. tesseract.
there is an open instance available at https://tesseract.dubvee.org/, you can enable media proxying in the settings on the left.
as always with uis hosted by third parties, keep in mind that you need to trust the operator, as they could deliver code that steals your credentials. when possible, use uis hosted by your own instance operator, as they would have access to them anyway if they wanted.

bans currently don't create explicit records for all content that was removed with them.

when a user gets banned from an instance or a community, there is an option to remove content along with the ban. in those cases, all content within the scope of the ban gets removed as well, but no individual modlog entries for the content are created.

modlog entries also disappear when the associated object gets purged, which results in a deletion from the database, but that will result in a purge modlog entry.

I messaged @supakaity@lemmy.blahaj.zone on matrix about this a while back already, before it was published. this is easily backported to 0.19.8, most likely even with the custom blahaj patches. i'm not sure it was applied though, as i didn't hear back from her unfortunately.

I made two accounts on sh.it instance using the same email.

this isn't possible, you can't reuse the same email for multiple accounts on the same instance.

if you reset another account's password with that it just means that you the user @emberinmoss@sh.itjust.works uses a different email address.

slur filters are a commonly used method on lemmy to deal with certain types of spam.

there are lots of spammers posting links to blog spot subdomains all the time, i think there were at least two new ones just today.

unfortunately, the amount of malicious links (random spam posts) to blog spot significantly outranks the amount of legitimate links, which is likely why this was added to blahaj's slur filter.

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.

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.