Nothing4You

is that sync? sync has some issues with local communities. I think it might get better if you subscribe to the community.

compare with the web version to rule out account related issues.

normalerweise werden keine frames eingebunden, nur bei video embeds meine ich

i can see rust being a bit more challenging to support properly in an IDE and there still being various special cases not handled properly, and i’m glad that it’s free to use non-commercially, but with jetbrains rustrover i frequently see it calling out errors in code that happily compiles, autocomplete being semi-random in how it wants to complete today, which seems to have gotten worse with their recent AI pushes, and even a couple times the entire IDE locking up not too long ago, though i don’t remember whether the last part was in rustrover or one of their other IDEs. overall pycharm has been pretty stable for me, as long as you provide it with a pre-existing venv or let it create one for you, as the integration with the latest and greatest™ python package manager may not be there yet.

honestly at this point I don’t consider it worth continuing the discussion here, as it doesn’t seem that you understand enough of what you’re talking about, despite your claims of dealing with it for “years”, yet you keep implying that i’m likely the one being wrong or even lying/misrepresenting things.

the second screenshot is from the same browser as the first, both are in firefox, using the tor browser variant in safest mode, which blocks even more than the average noscript installation in firefox. tor browser is a hardened variant of firefox esr. if it works in tor browser without loading js from third parties it’ll very much do so in any other browser. the screenshot is from macos, which is probably why you’re not used to it, but that’s just what firefox on macos looks like. this is my standard firefox install:

besides, if lemmy was loading and executing javascript from other instances, this would be a massive security issue, which is yet another reason why your claim of loading js from other instances is ludicrous for someone who knows how these things work, at least when you keep insisting on it.

as i mentioned before, noscript is not an extension that is easy to use without some basic understanding of how websites work. if you’ve been having issues for years due to not understanding these things and how to deal with them properly that suggests that it’d probably be better for you to just switch to something like ublock origin with anti-tracking filter lists if you’re not planning to spend some time learning how websites work and what the different types of blocked resources do.

i don’t even see how you would be blocking images with noscript, as there doesn’t even seem to be an option for it. unless of course you’re confusing noscript with something like umatrix, which does allow blocking images by default as well, but it would also clearly show that there is media blocked and not scripts:

anyway, if you’re truly interested in understanding these things and not just rant about them please do some research on the technology being used.

nothing about this is cherry-picking. it’s simply how lemmy works. there are no remote js sources. lemmy-ui even sets security headers that prevent loading js from third party domains.

doesn’t require allowing javascript of a million other servers?

half the images are broken because I’m expected to allow scripts on like 30+ sites to see most of the posts

software like noscript is not exactly beginner friendly. you’re expected to understand the impact of your blocking and what you are blocking. the only domain you need to allow JS from on lemmy.world is lemmy.world. standard lemmy-ui does not load any js or css from third party sources, only the domain where lemmy-ui is served. your noscript configuration is blocking the actual images, not javascript that would be required to load images.

edit:

to expand on this, even in tor browser in safest mode, lemmy.world works totally fine when all you do is allow JS from lemmy.world on lemmy.world:

modlog view is a bit broken currently and doesn’t make much sense if you don’t know how it works.

the modlog view currently merges the different types of modlog entries in a single view, but the pagination doesn’t make much sense that way.

for example, removing a comment is an action that happens quite frequently, but removing a community does not. the modlog shows e.g. up to 20 actions per modlog entry type, so you may see comment removals for the last few hours, but community removals could be for the past year. then when you hit next page, you’ll see the next page for each type, but the times make even less sense now. you’ll see entries 20-40 for comments, but also 20-40 for communities.

the timeline will be consistent when you filter for specific entry types.

you can simply check your profile and modlog on the instance in question. it’ll show that you got banned from that instance 8 days ago. since you didn’t participate in any community on that instance there were no community bans federated out. instance bans currently don’t federate, only community bans for communities on the instance you got banned from, if you have previously participated in them.

grafana.lem.rocks isn’t operated by lemmy.world.

as I was traveling for the past couple days I didn’t get to fix earlier, but everything should be working again now.

mod actions generally do federate correctly, at least on the latest lemmy versions. it’s just reports that don’t.

but in general, you will need an account on the community instance to get full federation abilities when you take potential instance bans and defederations into account. even when it’s not a defederation, if a user is banned from your instance but not from the community instance their posts won’t make it to you.

it’s literally explained in the post that it uses admin credentials

looks like the federation issues were just related to feddit.nl sending to lemmy.world, did you figure out what caused this?

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

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.