CAVOK

--Stolen and reposted here, sorry zab, but I hope you're fine with some extra promotion--

Hi,

[...]

After about a year off MuWire is back to the land of the living and the network has ~50 active users at any given time. Here is how to set it up and connect:

1. Go to the GitHub release page

2. Download the connections.txt file and save it somewhere

3. Depending on your operating system:

On Windows, download the MuWire-0.8.14-beta2.exe installer and run it. It will install everything you need to run MuWire. Skip to step 5.

On Linux, you need to install Java 17 or newer. This will be different on each distribution

On Mac, you need to install Java from [here] (https://jdk.java.net/22/) (available for both Intel and Apple Silicon).

4. Download the [MuWire-0.8.14-beta2.zip] (http://muwire-0.8.14-beta2.zip/) file and unzip it. Run the bin/MuWire script to launch MuWire.

5. Go through the MuWire setup wizard. When the main window appears, select Connections (top-left menu) -> Import connections and select the connections.txt file you saved in step 1.

Watch the bottom right of the main window - there is an icon like a molecule with the number of active connections to the MuWire network. As soon as MuWire connects, you can use it to search, share, download, message other users and more.

Enjoy!

zab_

cross-posted from: https://lemmy.world/post/17746311

This release, I2P 2.6.0, continues our work by fixing bugs, adding features, and improving the network's reliability.

Newer routers will be favored when selecting floodfill routers. I2PSnark received features which improve the performance of PeX(Peer Exchange), in addition to bug fixes. Legacy transport protocols are being removed, simplifying the code in the UDP transports. Locally-hosted destination will be reachable by local clients without requesting their LeaseSet, improving performance and testability. Additional tweaks were made to peer selection strategies.

I2P no longer allows I2P-over-Tor, connections from Tor exit IP addresses are now blocked. We discourage this because it degrades the performance of I2P and uses up the resources of Tor exits for no benefit. If you are a helpful person running both a Tor Exit and I2P we encourage you to continue to do so, using different IP addresses for each. Non-exit relays and Tor clients are unaffected by this and do not need to change anything.

As usual, we recommend that you update to this release. The best way to maintain security and help the network is to run the latest release.

RELEASE DETAILS Changes

• Router: Increase minimum version for floodfill routers

• Router: Disable I2P over Tor

• Address Book: Cache locally hosted destinations

Bug Fixes

• I2PSnark: Peer Exchange Tweaks

• I2PSnark: Bugfixes

• Router: Peer Selection Tweaks

Other

• Translation updates

This release, I2P 2.6.0, continues our work by fixing bugs, adding features, and improving the network's reliability.

Newer routers will be favored when selecting floodfill routers. I2PSnark received features which improve the performance of PeX(Peer Exchange), in addition to bug fixes. Legacy transport protocols are being removed, simplifying the code in the UDP transports. Locally-hosted destination will be reachable by local clients without requesting their LeaseSet, improving performance and testability. Additional tweaks were made to peer selection strategies.

I2P no longer allows I2P-over-Tor, connections from Tor exit IP addresses are now blocked. We discourage this because it degrades the performance of I2P and uses up the resources of Tor exits for no benefit. If you are a helpful person running both a Tor Exit and I2P we encourage you to continue to do so, using different IP addresses for each. Non-exit relays and Tor clients are unaffected by this and do not need to change anything.

As usual, we recommend that you update to this release. The best way to maintain security and help the network is to run the latest release.

RELEASE DETAILS Changes

• Router: Increase minimum version for floodfill routers

• Router: Disable I2P over Tor

• Address Book: Cache locally hosted destinations

Bug Fixes

• I2PSnark: Peer Exchange Tweaks

• I2PSnark: Bugfixes

• Router: Peer Selection Tweaks

Other

• Translation updates

Britain's new Prime Minister Keir Starmer and French President Emmanuel Macron on Thursday hailed an opportunity to strengthern relations between the UK and France on key issues such as defence, security and cross-Channel migration. Meeting at a summit for the European Political Community at Blenheim Palace near Oxford in the UK, the two leaders also reaffirmed their support for Ukraine.

Meta will withhold its next multimodal AI model — and future ones — from customers in the European Union because of what it says is a lack of clarity from regulators there, Axios has learned.

From the maintainer "alreadyburnt" on reddit.

Before we begin: Snap(and AppImages) are still not official packages. This still an experimental package and just a side-project of mine.

A few years ago, I got way too interested in these semi-novel packaging systems that the various distributions came out with. I went on a rampage of experimental package creation, often without necessarily knowing the future of the packages themselves. Many versions ago, the most popular of those packages broke in a particu`larly annoying way, and I did not have time to fix it. Until a few weeks ago, that is, and now, it's actually a lot easier for me to be sure that what I'm packaging is going to actually work because I can generate and test the packages continuously.

TL:DR the Snap, which I created, then broke, is now fixed, and it's likely to stay that way. If you are a snap user stuck on an old version, update as soon as possible.

It is generated using jpackage combined with the Easy-Install source. As a package, it functions like the Easy-Install bundle and not like the .deb or .jar installers.

https://snapcraft.io/i2pi2p

What's the real point? Nobody really cares about Snapcraft that much, except maybe Canonical. A lot of people don't even like them. That's not why there's a Snap of I2P now. The reason there's a Snap of I2P now, and that this experiment was not discontinued outright, is because it demonstrates the power of jpackage, the technology underlying the Easy-Install Bundles for Windows, to generate self-contained images that can easily be adapted to Linux package formats. Once you can stick a jpackage inside a Snap, you can just as easily stick it inside of an AppImage. A slightly different manifest format will leave you with a working Flatpak. The same applies to docker-compose and probably many other tools. Or, you can just stick it all into a .zip file and treat it like an I2P portable installation. The files your packaging are always the same, and are simply generated by jpackageing a custom I2P router launcher.

For more information, see:

https://snapcraft.io/i2pi2p

https://github.com/eyedeekay/I2P-Snaps-and-Appimages/