🛡 I2P: End-to-End encrypted and anonymous Internet - PurpleI2P/i2pd
[2.53.0] - 2024-07-19
Added
- New congestion control algorithm for streaming
- Support miniupnp-2.2.8
- Limit stream's outbound speed
- Flood to next day closest floodfills before UTC midnight
- Recognize duplicated routers and bypass them
- Random SSU2 resend interval
Changed
- Set minimal version to 0.9.69 for floodfills and 0.9.58 for client tunnels
- Removed openssl 1.0.2 support
- Move unsent I2NP messages to the new session if replaced
- Use mt19937 RNG instead rand()
- Update router's congestion caps before initial publishing
- Don't try introducer with invalid address
- Select newest introducers to publish
- Don't request relay tag for every session if we have enough introducers
- Update timestamp for non-reachable or hidden router
- Reset streaming routing path if duplicated SYN received
- Update LeaseSet if inbound tunnel failed
- Reseeds list
Fixed
- Crash when a destination gets terminated
- Expired offline signature upon destination creation
- Race condition between local RouterInfo buffer creation and sending it through the transports
You still have realvnc lite. It is free, 1 user, 3 machines, less features, but the basics still there.
🛡 I2P: End-to-End encrypted and anonymous Internet - PurpleI2P/i2pd
[2.52.0] - 2024-05-12
Added
- Separate threads for persisting RouterInfos and profiles to disk
- Give preference to address with direct connection
- Exclude addresses with incorrect static or intro key
- Avoid two firewalled routers in the row in tunnel
- Drop unsolicited database search replies
Changed
- Increase number of hashes to 16 in exploratory lookup reply
- Reduce number of a RouterInfo lookup attempts to 5
- Reset stream RTO if outbound tunnel was changed
- Insert previously excluded floodfill back when successfully connected
- Increase maximum stream resend attempts to 9
- Reply to exploratory lookups with only confirmed routers if low tunnel build rate
- Don't accept too old RouterInfo
- Build client tunnels through confirmed routers only if low tunnel build rate
- Manage netDb requests more frequently
- Don't reply with closer than us only floodfills for lookup
Fixed
- Crash on router lookup if exploratory pool is not ready
- Race condition in excluded peers for next lookup
- Excessive number of lookups for same destination
- Race condition with transport peers during shutdown
- Corrupted RouterInfo files
It's just Germany, the rest of Europe (EU and non-EU) doesn't actively care about them unless it's cp.
It's still my favorite network (using it from more 20 years ago), but for the latest things I use bittorrent and seed to both networks (bittorrent and ed2k/kad) through mldonkey 24/7.
Tor relay (guard/middle or bridge/snowflake) and i2p node (i2p, i2p+ or i2pd)
Then samsung galaxy a35.
Samsung phones nowadays are one of the best software support on every budget, starting with the A15 4G (~150€) with 5 years to the flagship, S24 ultra with 7 years.
Samsung galaxy A15 5G, Cheap phone (~180$), micro-sd, headphone jack, good software support (4 OS updates, 5 years security updates), good battery, 1080p amoled 90Hz 800 nits.
Maybe you could try ed2k/kad (emule/amule/mldonkey), soulseek or dc++ networks. Just drop the files in the sharing folders and seed. My preference is ed2k/kad.
Snowflake/bridge is used when you do not want the authorities/ISP know, you are using tor or because it might be blocked (like on contries with censorship). When you are running snowflake/bridge you are helping these users. For the contrary, if you use a normal tor relay, they(ISP, authorities, who ever is watching your connection) know, but they do not know what you are doing.
I run different services on my debian server and I would like to know if there any terminal command or something to show the countries and number connections that have established contact