Nah, ISO is a shit organization. The biggest issue is that all of their “standards” are blocked behind paywalls and can’t be shared. This creates problems for open source projects that want to implement it because it inherently limits how many people are actually able to look at the standard. Compare to RFC, which always has been free. And not only that, it also has most of the standards that the internet is built upon (like HTTP and TCP, just to name a few).

Besides that, they happily looked away when members were openly taking bribes from Microsoft during the standardization of OOXML.

In any case, ISO-8601 is a garbage standard. P1Y is a valid ISO-8601 string. Good luck figuring out what that means. Here’s a more comprehensive page demonstrating just how stupid ISO-8601 is: https://github.com/IJMacD/rfc3339-iso8601

Relevant (median salaries in the EU): https://www.levels.fyi/heatmap/europe/

No you don’t! That’s why we have key-signing parties!

While I think this is a good idea (because copyright is a stupid concept in the digital age), the problem with this proposal is that Europe is also very pro-copyright. Doing something like this would probably piss off Americans, but if it also pisses off your next best ally as well, it’s probably not going to work out.

That’s actually very easy to do and you don’t need any special equipment. Simply use a male-male 3.5mm cable and connect one end from the stereo output of the cassette player and the other end into the microphone jack of any computer you own. Play the cassette - you can test the audio quality by running arecord -f cd - | aplay - - you will have to tune the volume output of the cassette player and the input sensitivity of the microphone.

From there, if you’re paranoid, you could use arecord to save the output to a .wav file and encode it once the recording is done, but I had no problem just using oggenc directly on the piped audio. The final command looked like this: arecord -f cd - | oggenc -q 5 -o file.ogg - (change to -q 10 if you want lossless encoding).

I’m not sure if this is the best quality per se, but I would definitely recommend it over using specialized equipment like cassette-mp3 converters. The problem with those devices is that if they use underpowered hardware, you might experience buffering issues where the encoding hardware can’t keep up with the audio stream or something like that. But doing it on a computer ensures that you will have all the processing power you need to make sure that this doesn’t happen.

Good luck! I found it very easy to do - it took 5-10 minutes of setup.

Looks like there’s been plenty of recent updates to me: https://github.com/void-linux/void-packages/commits/master/

And innovative gameplay too. Large companies are too afraid to try new things, and all the games feel like the same rehashed mechanics with a fresh coat of paint… but indie developers are much more willing to try new, interesting concepts.

MOBILE USERS CAN GO FUCK THEMSELVES.

Phew. That felt good.

The difference is how you interact with the browser engine. Blink is very easy to embed into a new browser project. I’ve seen it done - if you’re familiar with the tools, you can build a whole new browser built around the Blink engine in a few hours. You can write pretty much whatever you want around it and it doesn’t really change how you interact with the engine, which also makes updates very simple to do.

With Firefox, it’s practically impossible to build a new browser around Gecko. The “forks” that you see are mostly just reskins that change a few settings here and there. They still follow upstream Firefox very closely and cannot diverge too much from it because it would be a huge maintenance burden.

Pale Moon and Waterfox are closer to forks of Firefox than Librewolf for example, but they’ve had to maintain the engine themselves and keep up with standards and from what I’ve read, they’re struggling pretty hard to do so. Not a problem that Blink-based browsers have to deal with because it’s pretty easy and straightforward to update and embed the engine without having to rewrite your whole browser.

Unfortunately, since Google controls the engine, this means that they can control the extensions that are allowed to plug into it. If you don’t have the hooks to properly support an extension (ie. ublock), then you can’t really implement it… unless you want to take on the burden of maintaining that forked engine again.

That said, Webkit is still open source and developed actively (to the best of my knowledge - I could be completely wrong here). Why don’t forks build around Webkit instead of Blink? Not really sure to be honest.

I chuckled a bit while reading this, because what you wrote is exactly where Blink came from. It was a fork of webkit, which in turn was derived from KHTML. Then again, the fact KHTML was discontinued does support your point to an extent too, I guess.

But the point is, Chrome is doing exactly this - providing the engine free as in beer and letting people embed it however they like. And yet, what you’re predicting, ie. not using the original but just using forks instead, doesn’t seem to be happening with Chrome - they still enjoy a massive fraction of the market share. There’s no reason to believe that this couldn’t happen at Mozilla as well. People usually want the original product, and it’s only a small fraction of people that are really interested in using the derivatives.

Ironically, the anti monopoly lawsuit against Google will end this.

People are quick to assume this, and there’s a very good chance that they’re right, but I don’t think we should take it as a given. It’s always possible that there could be some sort of court decision that allows Google to keep funding Mozilla after the “breakup” is complete.

In any case, we don’t yet know what the outcome of the antitrust case will be, so I think it might be best to avoid making statements of certainty like this until we see how things really shake out.

We should definitely take the possibility of this happening very seriously though.

You’re right about the fact that building an engine is hard, but Socraticly speaking, then why are there so many blink-based browsers and so few gecko-based ones? The answer is because blink is easy to embed in a new project and gecko isn’t.

If Mozilla really wants to take back the web (and I honestly don’t think they actually do), then what they should really be doing is making gecko as easy to embed in a new browser as blink is. They don’t do this, and I suspect that they have ulterior motives for doing so, but if they did, I think we would be much closer to breaking chrome’s grasp on the web.

Because let’s face it: Mozilla makes a pretty damn good browser engine. But they don’t really make a compelling browser based off it. Ever noticed how Mozilla has been declining ever since they deprecated XPCOM extensions? It’s because when they provided XPCOM, it enabled users to actually build cool and interesting new features. And now that they’ve taken it away, all innovation in browser development has stagnated (save for the madlads making Vivaldi).

They need to empower others to build the browser that they can’t. That’s what would really resurrect the glory days of Firefox in my opinion.

Website redesigns. Just more whitespace all over the place, less information on the screen, and more trouble trying to get anything done.

Github is especially bad about this. I’m so tired of only being able to fit about 50 lines of code on the screen at a time, or issues with a similar lack of information density. I can understand this paradigm for websites that you only use once every year or so, but for something that most people use regularly every day, it’s such a backwards anti-productivity trend. I hate it… hope it dies someday.

This has always been the whole point behind the Trojan Horse that is systemd. Now that Poettering/Red Hat control the entire userspace across virtually all distros, he/they can use it as a vehicle to force all of them to adopt whatever bullshit he thinks of next.

This is what the Linux ecosystem gave away when they tossed their simple init system to adopt the admittedly convenient solution that is systemd. But in reality, the best solution was always to drop init, and instead replace it with an alternative that was still simple to replace if the need should arise. But now that everyone is stuck on systemd, they’re all at the mercy of Poettering’s Next Stupid Idea.

Convenience comes at a price. systemd is the Google Chrome of Linux userspace. Get out while you can.

Indeed, Reddit was a great example of this. All of the stupid things they tried to pull off in the past few years (selling user data, turning off the API, insulting their users, VPN blocking, to name a few) would have not worked when they were a growing website. Now that they have so many low quality users, they can do that successfully because they know that said users are too dumb to realize how they’re being abused. Even larger websites like Twitter and Facebook operate this way.

The takeaway here is: don’t focus on having many users, focus on having good users. All relationships are a two-way street, and if you’re on the side of the street with too many people, you don’t have any personal leverage on your own. It’s in your best interests to get out of that relationship.

In some countries, there are already.

In others, it will be up to courts to decide whether this is illegally firing staff. That said, good luck getting equal legal representation to these trillion-dollar companies.

So yes, basically, it’s legal.

But part of the appeal of Linux is the fact that you can repurpose existing computers running other OSes to run Linux instead. This is a great way to lower the barrier to entry for Linux, because it’s easy to test it on a Live USB or a dual boot. It’s much harder to do this on phones because they have locked bootloaders.

Another problem is that phones are not productivity devices - they’re consumption devices. Maybe this is just my personal bias, but I don’t think people will be as passionate about liberating their phones because they’re inherently less useful than computers. Convenient, yes, but useful? Not as much.

That said, I would love to be proven wrong. I would definitely consider a Linux phone if they become more popular/useful, but I can’t really justify spending hundreds of euros/dollars on something for which I don’t see any particular use.

Great to see, but are there punitive damages too, or even charges for interest? Because if not, then they’ll just keep trying to pull stunts like this off again and again.

(My guess is that there isn’t because it involes a deal with Ireland, but I would love to be proven wrong.)

The biggest theft in history, even.

Why is nobody talking about this?? Oh yeah, because it’s okay when our planetary overlords do it. Let’s imprison some more homeless people for stealing bread instead!

That looks like a really nice policy. But my question then becomes, what happens if the company sells out someday? What if they get bought out by a larger company, or a private equity firm? Did they take funding, and if so, how much leverage do the funders have to influence them to make money and cut out programs like this?

It’s great to see companies trying to break that trend and I highly commend them for it! But we have already seen this pattern a million times before and it always ends due to something similar to this.