Professional C# .NET developer, React and TypeScript hobbyist, proud Linux user, Godot enthusiast!

https://blog.fabioiotti.com/\ https://github.com/bruce965

  • 0 Posts
  • 30 Comments
Joined 5 years ago
cake
Cake day: March 9th, 2022

help-circle




  • I don’t think you need a guide. Just install the extension and give it a try. It’s pretty simple and intuitive.

    still no possibility to set default container for Ctrl + T

    It might be possible now, you could give it a try. But anyways, I don’t see how changing the default container for new tabs could be useful. There is a default container which is the “no container”, why would you want to change it?


  • Are you talking about these containers?

    Each container is isolated from the others. If you don’t want a tab to track you, just use a dedicated container for it.

    You can also configure Firefox to always use a dedicated container for certain domains.

    As for destroying the data, you probably just need to clear cookies on close. That’s configurable. If you are extra paranoid you can also clear the cache.

    Did I miss something?


  • In that case I would say start with a Debian-based or Ubuntu-based distro of your choice. Ubuntu-based distros are also Debian-based, since Ubuntu is Debian-based. Mint is Ubuntu-based so it’s a good choice imho. Mint should work pretty well for backups and Minecraft.

    As a counter-example, Mint would (probably) be a poor choice if you want to turn that PC into a router or a DNS server, but sounds like that’s not what you have in mind.

    If you plan to Install more stuff in the near future, you could optionally look into containerization (Docker) which would allow you to someday swap Mint with another distro when you decide that you feel like changing. All of this, without having to reconfigure anything. Portainer might be a good soft-entry to Docker if you don’t love the terminal, it gives you a nice UI. And it’s compatible with Mint, ofc.

    As for the fedi instance, it’s a good exercise, you will learn a lot about networks. Personally I tried installing a Lemmy instance too, but I ended up turning it off as I realized that it didn’t make sense for my use case. It just wasted bandwidth to stay in-sync with the rest of the fediverse.



  • As far as I understand, audio cards hold a buffer of the audio that should be played at any time. If the CPU can’t keep up producing new audio, it will loop to the beginning of the buffer. My guess is that when you suspend, the CPU stops producing new data before the audio card stops consuming it. And that’s why you hear the last part for a short instant.

    It also happens on my devices, and it’s always happened on all my previous devices as far as I can remember.

    Disclaimer: this is based on my understanding + a lot of suppositions. It might not be accurate.



  • I do have an opinion about Ecosia, but it’s just based on feelings, so it doesn’t even make sense to share it. Apologies for not answering your question.

    Instead I would like to focus on this point:

    Ecosia isn’t very private, since it sends data to Bing

    Also DuckDuckGo does this, but they aggregate and anonymize that data before forwarding it to Bing. That’s probably the best they can do without building their own first-party infrastructure. I would imagine Ecosia does the same.


  • bruce965@lemmy.mltoLinux@lemmy.mlGPG Key Managing
    link
    fedilink
    arrow-up
    2
    ·
    10 months ago

    I am not OP, but that would be the ideal solution for me. Unfortunately, KPXC does not support communication with the GPG agent and the team is not interested in adding this feature due to it being «[…] far more complicated than ssh-key management. There are already excellent tools for this, Kleopatra being the best».





  • […] re‑engineered flash physics by replacing silicon channels with two‑dimensional Dirac graphene and exploiting its ballistic charge transport.

    By tuning the “Gaussian length” of the channel, the team achieved two‑dimensional super‑injection, which is an effectively limitless charge surge into the storage layer that bypasses the classical injection bottleneck.

    That’s some seriously technical jargon.

    ChatGPT seems to be able to explain, not sure how accurate it is though.

    Flash memory traditionally uses silicon channels to move charges (electrons) into a storage layer. These researchers changed that by replacing silicon with Dirac graphene. Graphene is a single layer of carbon atoms arranged in a honeycomb structure. It’s called a Dirac material because its electrons behave like massless particles, moving extremely fast and with very little resistance.

    This leads to ballistic transport: electrons move without scattering, like a bullet in a vacuum. This is far more efficient than silicon, where electrons bump into atoms and lose energy.

    Tuning the “Gaussian length" likely refers to modifying the shape or spread of the electric field or potential in the channel (possibly shaped like a Gaussian curve, i.e., a bell curve). By adjusting this, they control how charge flows.

    Achieved two-dimensional super-injection means they were able to push a large amount of charge very efficiently from the graphene channel into the memory storage layer, and in a 2D way (across the flat graphene surface), rather than through a narrow point.

    Effectively limitless charge surge: normally, in flash memory, there’s a bottleneck where only so much charge can be injected due to energy losses and scattering. But with graphene’s ballistic transport and this super-injection method, that bottleneck is gone—or drastically reduced—enabling faster and more efficient memory writing.


  • Fair enough, but then it’s the same thing as open-sourcing the code but not providing support nor binaries.

    I mean, personally I also prefer it to FUTO’s proprietary license, that’s for sure. But I’m one of the few privileged users who can build from source.

    If this license doesn’t impose any extra restrictions on the code (and as you say, anyone can fork and provide prebuilt binaries), then this would just increase the risk of spreading malware, with no real benefits for the original developers.

    In my opinion, if you want to monetize your software without going proprietary, all you have to do is provide the users a convenient way to get it. There are some paid FOSS apps on Google Play, as well as some paid FOSS games on Steam. You don’t want to distribute binaries? Fine, okay, that’s alright and I respect your choice. You don’t want to provide support to non-paying users? Fine, that’s very reasonable in my opinion. But…

    …do you want to impose extra restrictions on your code? Fine to me, but then you are no longer doing open source, don’t try to pretend you are. And if you are not imposing any restrictions on the code then you are imho just going to hurt small users. We shouldn’t fight small users imho, we should fight the big corporations exploiting FOSS code for their proprietary businesses. But if there are no extra restrictions on the code, then big corporations wouldn’t care.

    That’s my opinion.


  • I’m not a lawyer, but this doesn’t seem to be compatible with (A)GPL licenses.

    I would say this is going to harm small users more than big corporations. As a small user I might be unable to build from sources myself, so I would have to pay. But as a big corporation building from source would be something I can certainly do trivially, then I wouldn’t be subject to the restrictions imposed by this license.

    Imho, if someone wants to force their users to pay, then they are not doing open source. Please let’s not try to pretend we are by adopting a OSI-approved license and slapping extra restrictions on top of it.

    Just go AGPL for datacenter-oriented softwares, or GPL for drivers and embeddable code, or a proprietary license such as FUTO’s for end-user software.


  • bruce965@lemmy.mltoLinux@lemmy.mlAMD vs Nvidia
    link
    fedilink
    arrow-up
    10
    arrow-down
    1
    ·
    2 years ago

    If you don’t want proprietary drivers the choice is quite straightforward: AMD. The official drivers are open source.

    As for my experience, I’ve had absolutely no problems in the last few years with AMD, but I have to admit that I have always been using an iGPU, which has always been good enough for my needs.

    I used to have problems with Nvidia proprietary drivers, but that was at least a couple years ago, things might have changed. I’ve never had issues with the free unofficial drivers, besides worse performance.