In circa 2003-2004, it was as close to on par with browsers at the time as it would get. I think the WebKit fork did damage to the momentum. By 2008 with KDE4, the rework that split it and Dolphin into to products was basically the final nail I think, as development work effectively stopped.

Likely old accounts are an exploit vector for hackers. That would be the only reasonable excuse. However someone in the business unit will use this as their lever to make other bad decisions.

The irony is that Chrome’s rendering engine was a fork of WebKit, which was a fork of KHTML, a free and open source rendering engine created by KDE for Konqueror. They basically took something free, used Microsoft’s “embrace, extend, extinguish” tactics on it. Now KHTML is vestigial, only found in the UserAgent string.

But we could have had a truly free open source cross platform browser with Konqueror.

Best we have now is Firefox, but the bulk of Mozilla’s development funding comes from setting Google as the default search. So it is also hijackable.

I think it was still called Phoenix when I originally dropped it. Before it got renamed Firefox. Came back around last year after adblock stuff in chrome finally chased me away.

If they’re the copyright holder, they are allowed to use any license they want. Including a modified AGPL. It’s up to the users to understand what license they’re getting the software under. In this case, it is a modified-AGPL.

This is like Qt when they used the modified GPL (Qt 2-3 era, before they went full LGPL). Qt was the copyright holder and can issue under terms they decide. Then it is up to the users to decide if those terms are acceptable. KDE decided these terms were acceptable, but some other users did not.

However, if a user decided to ignore the additional clauses in Qt and treat it as unmodified GPL, they would have been in violation of the license. Because Qt was the the copyright holder and can dictate terms. Qt would have won the court case. It never happened, so it wasn’t tested, and that’s ancient history now.

But here OnlyOffice is in the same boat. They can dictate the terms, and a court can decide if a user is in adherence of those terms. There’s no part of copyright law that OnlyOffice is violating here.

What will be up for legal debate is whether EuroOffice is willfully and maliciously violating it, or if they just interpreted differently. If the latter, then there will be a great deal of legalese. The real question will be: the AGPL as amended by OnlyOffice – does it permit forking, and are forks subject to the same modified clauses.

I suspect OnlyOffice wins this one if it actually goes to court. Which will be super annoying from an end user perspective.

The problem with this is that OnlyOffice owns the copyright and used attribution agreements from any contributions. Meaning, as owners of the copyright, they are allowed to set the license. So if they applied the AGPL wrong, they aren’t violating anyone else’s copyright. If OnlyOffice has used someone else’s AGPL code and then added these impossible restrictions, then I would agree.

The legal battle between euro office and onlyoffice is interesting. I actually hope it goes to european courts. I suspect onlyoffice will win this one, but then everyone will abandon their code.

Simultaneously TDF and collabora are having a spat.

Interesting things afoot in the FOSS hosted office ecosystem. Prediction: a third option emerges – clean room rewrite (maybe this is a good thing).

Hypothetically: Lemmy instances where every user has to have physically met an admin and proved that they’re real or something. And they’ll only federate to other instances following the same rules.

It’ll almost be like the early 90s dialup BBS small communities, with FIDOnet ;)

Uncle, how do I upvote twice? ;)

The end of the anonymous web is nigh. We may not like it, but it’s probably the only way. We used to joke in the 90s about requiring an internet driver’s license before allowing people on Usenet. It might actually be happening.

Okay, first off, I’m really impressed that Lemmy (the web interface anyway) embeds TIL.vids video player and it just works. Since it’s peertube, I guess I shouldn’t be surprised. (I wonder how hard it is to create a peertube instance, hmmm.)

Next: as a former KDE dev, I love these sorts of updates. Put it on the background while I was working this morning :)

Most interesting: hiding things from screencasting… if Plasma were ever deployed in an educational context, this will hurt the anti-cheating software that screencasts your screen during test taking. Well, they probably make you use windows in that situation anyway ;)

Weirdest: mouse pointer stays in centre mode… bizarre. Would be fun to couple with an eye tracking camera to create a fucked up feedback loop haha.

Went to a strip club once and the stripper was handing out fake $69 bills with her image on it and a link to her OnlyFans…

Definitely not in ziplock bags hidden in the nearest forest to the school, put there by your older brother…

You might need help. If you’re unwilling to seek help, then at least learn to code and, you know, read the code.

When modern billboards became a thing, many cities or similar jurisdictions passed laws limiting their proliferation, in order to ensure you didn’t end up in a billboard filled dome.

In Canada, at least, you can register your address as a “no admail” destination, and you’ll stop getting those flyers entirely. It doesn’t stop certain protected classes of ads, in particular ads for prospective politicians during an election campaign, or mail that is personally addressed to you (even if it is an ad). But does shut it almost completely down. This would be the legal equivalent of installing a real-world ad-blocker.

I spent about a decade as a KDE developer.

KDE has this mindset where if someone wants to implement something they think is cool, and the code is clean and mostly bug free, well – have at it! Ever wonder why there’s 300 options for everything?

Usually (because there’s a bunch of people trying to optimize the core for speed and load times and such) this also means that the unused code-paths are required to not contribute negatively to things like load times. So a plugin like this that doesn’t get loaded by default unless enabled, and thus doesn’t harm everyone else’s performance. It also means that if it stops working in the future and starts to bitrot, it can be dropped without affecting the core code.

Admittedly, a lot of people have flawed reasoning too.

Nope, haha. OpenSuse is old.

This is an amazing graph. https://en.wikipedia.org/wiki/File:Linux_Distribution_Timeline.svg

OpenSuse comes from Suse which comes from Jurix and Slackware. There’s a dotted line from Redhat, because of the use of the RPM format, but that is as far as their interbred. Many people consider it one of the OG distros.

Arch sprang from the aether later, but one could argue it owes Gentoo for its concept (also a dotted line there).

Debian is an OG. It, Redhat, and Suse are approximately the same age.

Slackware on the other hand just keeps going.

I thought GCC dropped support for compiling to the abacus?

Colour me cautiously optimistic