supervent

joined 2 years ago
[–] [email protected] 9 points 2 weeks ago (1 children)

You are right, in this video have good explanations.

[–] [email protected] 4 points 3 weeks ago* (last edited 3 weeks ago) (7 children)

I am not saying about this article in concret, just saying the writer is not trustworthy in general. The majority of his articles have bias to russian side. And I stopped reading when I viewed his name. And again, spanish mass media not the best option for this topic.

[–] [email protected] 15 points 3 weeks ago (9 children)

All of his articles are based on information from the Russian Ministry of Defense. Russia always adapts, advances, and triumphs from its perspective, and that's not true. Spanish mass media it is not best option to stay informed about the war. Alberto Rojas from elmundo is more imparcial.

[–] [email protected] 15 points 3 weeks ago* (last edited 3 weeks ago) (11 children)

The writer is always supporting russian side and spreading russian propaganda in all his articles. Not trustworthy.

[–] [email protected] 1 points 1 month ago* (last edited 1 month ago)

For this use it is better tor

[–] [email protected] 11 points 2 months ago

I use Adguard's public DNS on my router for convenience, no problems at all. In the past I had pi-hole with some lists that in the end, from time to time, broke things.

[–] [email protected] 2 points 3 months ago

Ed2k/kad are still kicking, I use mldonkey for that networks

[–] [email protected] 2 points 3 months ago

mldonkey for ed2k/kad network and bittorrent

[–] [email protected] 1 points 4 months ago

Well I have an old suunto 5 peak, I like the battery, the construction style, navigation routes (for hiking, trail running), I miss something like garmin pay. But now suunto doesn't have an entry level watch, for this I said coros, polar or garmin. And between these 3, coros because it is focused on runners this brand and I think have better support than polar.

[–] [email protected] 1 points 4 months ago (2 children)

I wear a suunto but if I had to choose between these two, probably I'd pick up a coros for running.

[–] [email protected] 3 points 4 months ago (4 children)

If you need stay on budget, you could look into the coros pace 2/3 or polar pacer for MIPS, for amloled display you have garmin forerunner 165 or amazfit cheetah.

[–] [email protected] 13 points 4 months ago* (last edited 4 months ago)

And the same time more than ever russian casualties grow.

 

That's my favorite p2p program for ed2k/kad and bittorrent since like 2010

Changelog

3.2.1 - 2024/08/19

  • upgrade autoconf build system files
  • commit configure to git so that source archive is identical to the tag checkout
  • disable automatic invocation of autoconf

3.2.0 - 2024/08/17

Supported OCaml versions now are from 4.03 up to 4.14, as a consequence local (in-the-tree) build of OCaml is not supported anymore, you must have OCaml installed to build.

NB newgui2 build is finicky, see README.md for details (tl;dr system packaged OCaml and lablgtk2 or --enable-batch with OCaml 4.05)

  • fix duplicated Content-Length header (#82)
  • Support miniupnpc 2.2.8 (#101, Sergey Fedorov)
  • upgrade upnp/natpmp libraries versions for in-the-tree build (--enable-force-upnp-natpmp)
  • fix setting network-specific options from command-line (#34)
  • fix build with newer (safe-string) OCaml (#98, #99, Luca Carlon)
  • some internal code and build system cleanup
  • CryptoPP build fixes (#62, #63, #66, Hin-Tak Leung, Jesús Pérez Rey (Chuso))
  • dark theme for the web interface (Luca Carlon)
 

[2.54.0] - 2024-10-06

Added

  • Maintain recently connected routers list to avoid false-positive peer test
  • Limited connectivity mode(through proxy)
  • "i2p.streaming.profile" tunnel's param to let tunnel select also low-bandwidth routers
  • Limit stream's inbound speed
  • Periodic ack requests in ratchets session
  • Set congestion cap G immediately if through proxy
  • Show tunnel's routers bandwidth caps in web console
  • Handle immediate ack requested flag in SSU2 data packets
  • Resend and ack peer test and relay messages
  • "senduseragent" HTTP proxy's param to pass through user's User-Agent

Changed

  • Exclude 'N' routers from high-bandwidth routers for client tunnels
  • C++11 support has been dropped, the minimal requirement is C++17 now, C++20 for some compilers
  • Removed dependency from boost::date_time and boost::filesystem
  • Set default i2cp.leaseSetEncType to 0,4 and to 4 for server tunnels
  • Handle i2cp.inboundlimit and i2cp.outboundlimit params in I2CP
  • Publish LeaseSet with new timestamp update if tunnel was replaced in the same second
  • Increase max number of generated tags to 800 per tagset
  • Routing path expiration by time instead num attempts
  • Save timestamp from epoch instead local time to profiles
  • Update introducer's iTag if session to introducer was replaced to new one
  • RTT, window size and number of NACKs calculation for streaming
  • Don't select same peer for tunnel too often
  • Use WinApi for data path UTF-8 conversion for Windows

Fixed

  • Jump link crash if address book is disabled
  • Race condition if connect through an introducer
  • "Date" header in I2PControl response
  • Incomplete response from web console
  • AEAD verification with LibreSSL
  • Number of generated tags and new keys for follow-on tagsets
  • Expired leases in LeaseSet
  • Attempts to send HolePunch to 0.0.0.0
  • Incorrect options size in quick ack streaming packet
  • Low bandwidth router appeared as first peer in high-bandwidth client tunnel
 

[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
 

[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
view more: next ›