• 0 Posts
  • 43 Comments
Joined 1 year ago
cake
Cake day: March 24th, 2024

help-circle
  • 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.



  • 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:




  • 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.




  • 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.







  • pretty much, yeah. lemmy has a persistent federation queue instead of fire and forget requests when activities get generated. this means activities can be retried if they fail. this allows for (theoretically) lossless federation even if an instance is down for maintenance or other reasons. if mbin has a similar system maybe they could expose that as well, but unless the system is fairly similar in the way it represents this data it will be challenging to integrate it in a view like this without having to create dedicated mbin dashboard.




  • at least the image resizing topic has recently been fixed in lemmy, thumbnails sizes are limited (at the time of thumbnail creation) in the latest release. I’d have to look closer at the other stuff, the api part is unlikely to have changed and will affect all frontends, but js part should differ depending on the front end. some instances already use other frontends by default and there is also a replacement for lemmy-ui being worked on (lemmy-ui-leptos), but I don’t know how they compare. either.

    it should be taken into account though how much of this is cacheable as well, as it will then typically only affect the first load for the static files.

    I can totally understand the issues in general though, I’ve been living with a 64kbps uplink for several years in the past.