this post was submitted on 21 Jan 2025
74 points (100.0% liked)
Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ
55507 readers
617 users here now
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
Rules • Full Version
1. Posts must be related to the discussion of digital piracy
2. Don't request invites, trade, sell, or self-promote
3. Don't request or link to specific pirated titles, including DMs
4. Don't submit low-quality posts, be entitled, or harass others
Loot, Pillage, & Plunder
📜 c/Piracy Wiki (Community Edition):
💰 Please help cover server costs.
 |
 |
|---|---|
| Ko-fi | Liberapay |
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I don’t know why i2p would be flaky on macOS. I run i2pd (hate Java) on Linux and macOS and it’s functionally the same.
That was just my assumption, because the modern macOS network stack is not exactly similar to Linux, so some changes would be required, and since it's not that widely used (at least in the I2P community) it wouldn't get tested and developed that much. But again, that was just my assumption.
As a former Java dev: Completely understandable. i2pd is the only I2P implementation I will ever touch, the Java client is just a buggy mess with bad performance.
A lot of the macOS networking stack (at a lower level) comes from FreeBSD. People have argued that the BSD network stack is superior to Linux whereas Linux runs applications faster. At a low level, I think this is still accurate.
I’m a Ruby developer but I tried to port a Linux application written in C to macOS before and it was mostly rearranging positional arguments to system API calls; however there’s probably a lot more going on that I’m not aware of too.