undefined
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.
What in the hashtags is going on here?
I do, unfortunately.
If I hear his droning groggly voice going off about some fake shit, I usually snap and tell whoever to shut that shit off. It’s unbearable. The guy sounds how I imagine anyone would after a 40+ years of Quarter Pounders and Diet Coke, he’s probably way over his fair share in carbon emissions from diet alone.
I thought I could tolerate reading quotes of him but it’s a mess every time. Whatever schools he attended failed him greatly.
Who else should we blame? Trump won the popular vote, so it was those who voted for him who caused this. Whether they’re dumb as shit or not doesn’t change that.
I’m a master of not taking sides and it’s very easy to do: just keep your mouth shut.
Transmission is my favorite design-wise on macOS but I wish it had i2p support.
Doing research I think I’ve got my head around it. I’ll probably talk to a tax accountant regardless, but this information seems to be correct.
I see it deleted now but I’d guess that either my instance or Lemmy client was out of sync.
Right, but if you open the Associated Press article in Apple News you can report issues with the article.
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.