Never encountered that bug on Eternity but I would suggest making a bug report for that issue on the page for Eternity so they might be able to fix it.
Liftoff is on it’s last legs, once the last 0.18.5 instances make the upgrade to 0.19 it’ll almost certainly be unusable. Dev isn’t active anymore so I wouldn’t count on an update to fix it either, at least not any time soon. He also said he doesn’t have much experience with auth so even if he does get back to it it could take him a while to re-implement login.
Probably not, I doubt they even understand what the fuss was even about and are now wondering why quality has gone down so much and why subs are becoming full of spam and reposes.
I guess this is how they’ll learn about the effects of ruining the experience for moderators and content creators, a majority of Reddit’s scabs are consumers so naturally when creators and mods leave quality goes in the toilet.
which reddit was obviously super happy about the pirate sub closing down.
Oddly it wouldn’t seem entirely like that since when it shut down they basically forced it to reopen. Which is funny since they dislike it so much, guess the traffic and ad revenue is more important to them.
Mainly I just use the one built-in to settings of Gnome, I never torrented on public wifi (most public wifi I’ve used is too slow to download without chewing up all the bandwith) but the MAC address randomizer seems to work very well, even with the ones that use timed paywalls (where they let you use it for a time then lock your MAC address out and ask you to pay).
In this day and age everyone should be using a MAC address spoofer, especially on Public Wifi, many of them track mac addresses and impose limits based on time and data usage.
If you’ve ever been using public Wifi and noticed it got slow or stops working after a time, that’s why. Some will even be up-front about it by asking you to pay for it after a time.
Ubuntu, because snaps break shit and don’t work right a lot of the time, also they left people hanging with 32 bit support which isn’t great (for being a Legacy OS for weak computers it’s not a great look for them, or all the Linux distros that followed them).
There were a lot of problems with Fedora and CentOS, none of them as bad as Ubuntu though. Most were either instability or software availability due to lacking RPM versions of the software I needed.
Arch itself hasn’t given me many problems but it is ideologically problematic for a lot of reasons (mainly the elitism) and it is also a rolling release which isn’t great if you don’t like being a guinea pig and getting software before all the bugs have been ironed out.
But even if you can intuitively understand what the machine code is you’ll still need to convert it by hand back into something more portable, or to the machine code of another platform you might want to run it on. There’s not really an easy automated way to do that, even when playing dirty.
That’s the hard part, getting it into a different form, such as from x86 to ARM or from 6502 RISC to x86.
Only if they wrote why in it though, plenty of people (unfortunately myself included) fail or forget to add meaningful comments or they let their comments go stale when making changes by forgetting to update them (I do it a lot too), and some people also use horrible function names that don’t make any sense.
So it only really applies to source code intended to be released where care was made to ensure it would be readable, it might not apply for source code never intended to be public, such as stolen, leaked, or posthumously released. In this case the only real benefit is that it can be recompiled on different architectures provided there isn’t a dependency issue preventing that.
Yes there is indeed a difference, but for us it makes little to no difference. In the end what matters is that we have it without having to reverse engineer it, which is a slow and laborious process (even when you do it with dirty methods).
It’s not actually unstable, more accurately it’s tested and verified as much as Debian stable, meaning it’s fine for desktop use but I wouldn’t use it for a server or critical system I plan on running 24/7 without interruption, both since it may have bugs that develop after long term use and gets more frequent updates which will be missed and render it out of date quickly if it’s running constantly.
That’s probably the reason why instances like lemmy.blahaj.zone, pricefield.org, and reddthat.com chose to disable them. They aren’t constructive and more importantly they lead to people using them instead of reporting, which is really bad when it comes to enforcing rule violations.