Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)RE
Posts
3
Comments
2,019
Joined
2 yr. ago

  • I2P has a mechanism where if you can't open a port, another I2P router can help with NAT hole punching so that you can establish a connection.

    In practice this means I2P users can be equally well connected regardless of being able to open a port.

    But, unfortunately I2P is very slow. But maybe it's just because there's few people running routers, on slow networks?
    In any case, it would be beneficial to have it easily accessible to everyone, so that copyright holders can go pound sand.

    Edit: When you couldn't open ports for I2P, the I2P router will have the "Network: Firewalled" status. This is the description of this status on the router dashboard:

    Firewalled: Your UDP port appears to be firewalled. As the firewall detection methods are not 100% reliable, this may occasionally be displayed in error. However, if it appears consistently, you should check whether both your external and internal firewalls are open for your port. I2P will work fine when firewalled, there is no reason for concern. When firewalled, the router uses "introducers" to relay inbound connections. However, you will get more participating traffic and help the network if you open your firewall. If you think you have already done so, remember that you may have both a hardware and a software firewall, or be behind an additional, institutional firewall you cannot control. Also, some routers cannot correctly forward both TCP and UDP on a single port, or may have other limitations or bugs that prevent them from passing traffic through to I2P.

  • did you recently install librewolf, and log in to ff sync? librewolf has it by default to delete almost everything when you close it, and sync will make your other browsers do that too.

    speaking from first hand experience.

    you can disable this in the settings, no need for about:config diving.

  • I don't need an LLM on my phone, and most people don't either. I mean, I'm not an AI addict, but also, these are battery powered devices!

    if I want to use an LLM on the go for some reason, I would either run that at home on a computer that was made for performance, or just use the duck.ai site because that's just fine too.

    my phone has 6 GB, and that's plenty. I have a ton of apps installed, and always running background services like Syncthing.

  • This means that I can't use the built-in webcam until upstream support for the specific sensor arrives in the kernel.

    wouldn't it suffice to build it from source into a kernel module that you can load? that way you wouldn't even need to build the kernel. DKMS would help to automate this for kernel updates