• 2 Posts
  • 167 Comments
Joined 4 years ago
cake
Cake day: January 21st, 2021

help-circle

  • kevincox@lemmy.mlMtoOpen Source@lemmy.mlGIMP 3.0 Released
    link
    fedilink
    arrow-up
    23
    arrow-down
    2
    ·
    17 days ago

    Actually I would pick GIMP.

    1. Says what it is, an image editor.
    2. No popups and random interruptions.
    3. Not only AI editing examples which makes me thing the tool is AI only.
    4. An overview of the variety of major features it has rather than just AI editing.
    5. Links to helpful documentation rather than endless marketing pages that say nothing.

    Really think only thing I would like to see is some screenshots and examples of using the tool, rather than just info on what it does. But the Photoshop page barely has this, just a few examples of the AI tools.


  • I still recommend it. I’m not fully happy with the situation but for now I consider it my best option.

    1. I consider Chromium-based browsers out of the question as they give too much power to Google. This is already showing to be a problem with new APIs and “features” that Google is pushing into the web platform and the bigger the market share gets the more control they have.
    2. Web browsers are the biggest attack surface that most people have. Displaying untrusted webpages and running untrusted code is incredibly difficult and vulnerabilities are regularly discovered. I don’t yet know a Firefox fork that I trust enough to reliably respond to security vulnerabilities quickly and correctly.

    So for now I am staying with raw Firefox. Not to mention that as a disto-built Firefox I have some insulation from Mozilla’s ToS. But I am very much considering some of the forks, especially the ones that are very light with patches and are mostly configuration tweaks.



  • For .config it isn’t as important to me, but putting things that can be re-created in .cache (well the proper environment variable that defaults to .cache) is very nice because I don’t need to back up all of that junk.

    But it wouldn’t be unreasonable to put something like .config in a git repo, and storing full history for large and frequently changing files is a waste of space if they aren’t really “config”.






  • The most likely situation is that the torrent isn’t good. I would also force a recheck of the torrent to double-check that the files on your disk haven’t been corrupted. But if that file is still saying “0 B” remaining (don’t just look at 100% as it may be rounded) after the recheck then I would bet pretty good money on a broken torrent. If this is a public tracker it is fairly common.

    However even if it is broken you may be able to play by using a different players. Different apps can skip over different forms of corruption, so you may get lucky.



  • The main issue is accepting incoming connections. When you are behind a NAT (as most VPNs are for IPv4) you need some solution (such as port-forwarding) to make your torrent client connectable. This causes a number of issues when torrenting.

    1. When someone starts a download they will try to connect to the seeders. If the seeders are not connectable this will fail.
    2. As a fallback when the seeders notice the leachers they will try to connect to them. If the leacher also isn’t connectable this will also fail.

    If neither party is connectable the download can’t happen, so you may fail to get content that you want.

    This is extra relevant if you are on private trackers where seeding is tracked, has direct value and is competitive. If you are not connectable every new downloader will immediately connect to the connectable seeders and finish the download before your client even knows that they exist. (reannounces for seeders can be very infrequent, such as hourly, so it will take an average of 30min for you to notice a new seeder and try to connect to them). This makes it very difficult to acquire much upload unless there are very few other seeders.

    NAT is evil, all hail IPv6.


  • It would be nice if there was a shortcut to go “back to previous site”. Because on one hand using back to navigate around map moves is often very convenient, but sometimes I want to go to the site before the map. Having a two-level history with page and site would be super useful.