leopold @ leopold @lemmy.kde.social

Posts

0

Comments

239

Joined

2 yr. ago

I don't follow. ElasticSearch was only available under proprietary source-available licenses. Now, it's also available under the AGPL, which is open source, meaning ElasticSearch is now open source software. What part of this is deceptive or contradictory?

Uh, Cinnamon does not need a compatibility app to run Qt apps. No desktop environment does. You mostly just need to be X11 or Wayland compliant. The same is true with GTK.

MV3 doesn't make adblockers impossible, only less effective. It's important to note that MV3 has changed a fair bit since the initial controversy and isn't quite as limiting as it used to be. The fact that adblockers will lose some functionality at all is still a dealbreaker for me and many others which I thankfully won't have to deal with as a Firefox user, but it isn't going to kill adblockers on Chrome and most users will probably just install an MV3-compatible adblocker and move on with their day.

uBlock Origin's developers don't seem to want to make a proper MV3 port, which is fair because they'd probably have to rewrite most of the extension, but they did create the far more minimal uBlock Orgin Lite, which a lot of people have taken to be an attempt at porting uBlock Origin to MV3. It isn't that. On top of MV3's limitations, it also makes the decision to work within these self-imposed restrictions:

• No broad host permissions at install time -- extended permissions are granted explicitly by the user on a per-site basis.
• Entirely declarative for reliability and CPU/memory efficiency.

These aren't MV3 limitations, just a thing Gorhill decided to do. See the FAQ. You can get much closer to uBlock Origin within MV3's constraints than uBlock Origin Lite does. Right now, the best option appears to be AdGuard, which has been making a true best-effort attempt at porting their adblocker to MV3 pretty much since the announcement.

itch.io also has a Linux app

So... why are people upset about this? I'd say it's about damn time. Having two settings apps is pretty ridiculous and it's honestly crazy it's taken them this long to ditch the control panel. I still remember people making fun of Microsoft's inability to drop control panel in the Windows 10 era. Is there anything special about the control panel or uniquely terrible about the settings app that would warrant this kind of negative reaction? Is it because of the settings that aren't available in settings? If they're preparing to drop control panel that probably means they're going to add whatever settings are still stranded on it to the new settings app, unless there's evidence that they won't do that.

Dunno. Regardless of the method used by the extension, I think any extension called "Bypass Paywalls" that does what it says on the tin can pretty unambiguously be said to be designed to circumvent "technological protection measures". In this case, it circumvents the need to login entirely and obviously it circumvents the paywall.

Though as you said, these guys should probably be sending DMCAs to the Internet Archive if they actually want to stop their paywalls from being bypassed. I know they do honor takedown requests. Maybe archive.today is the problem? Maybe they don't honor DMCA requests. I very often see them used on Hacker News whenever someone wants share a paywall-free link to an article.

You can do that with permissively licensed software too. Except with those, the party distributing their repackaged version doesn't have to distribute source code alongside it. A lot of companies avoid copyleft software because they don't want to or cannot deal with stricter licensing terms. If you're a company creating commercial software which you intend to sell, you don't want to use any GPL code, because you want to keep your software closed source to avoid exactly what you described from happening.

This can be exploited by primarily licensing your open source code using strong copyleft (like the AGPLv3) while selling commercial licenses to businesses that don't want to comply with the AGPL and are willing to pay up. Qt is able to successfully use this even with weaker copyleft (LGPLv3) because it's used a lot in embedded systems (like smart cars) which cannot comply with the LGPLv3's anti-tivoization clause.

This means copyleft licenses can make it easier to profit if you're the author of the code, but of course third parties can more easily profit from permissive licenses.

Er, yes. It's one of the main features being introduced in 3.0. I don't know why you would just assume they're not adding it without looking it up. It made quite a bit of noise when it started being in the works.

Basically everywhere I go on Lemmy you're there spouting ignorant bullshit, garbage takes, rage-bait and misinformation. You're inescapable. This is the perfect example. You know what you're saying is wrong. You know you're being dishonest. Do you wanna know how I know? Because I literally told you as much less than two weeks ago when you tried spreading the same lies. But you didn't care back then and you still don't care now. The only thing you seem to care about going by the other things I've seen you post is pushing your favorite projects, and you will use all of the arguments available to do so, including the ones that you just entirely made up. You think LadyBird is the better project and are trying to spread the belief that Servo is dead to make others buy into the LadyBird hype further. But, of course, Servo verifiably isn't dead and in fact the Servo team writes up monthly blog posts detailing their progress, which show the project developing at a healthy pace. And to top it all off, when these facts are pointed out to you, your only comeback is "means nothing". Clearly you're not the kind of person to let facts tie you down.

LadyBird is an unusable pre-alpha-quality web browser. The fact that they haven't bothered porting to Windows yet is both thoroughly unsurprising and entirely meaningless. In its current state, it wouldn't become popular either way. But I guess Linux users have this weird inferiority complex where everything must instantly be dropped to port to Windows even when it makes little sense to do so.

WebKit/Blink are mostly LGPL.

WebKit isn't dead and is being used by GNOME Web.

Because it doesn't matter for most apps. XWayland works fine.

Even Blender says if it fails to use Wayland it will use X11.

What are you trying to say? Of course it does. Pretty much every Linux app still supports X11, because a lot of people are still using X11. Only exception I'm aware of is Waydroid.

OS is also identified by user agent, so it's no less vulnerable to fake agents. In any case, I'd wager the vast majority of users even on Linux use unaltered agents, though this isn't something that can be backed up one way or another because there are no numbers for fake agents.

Putting aside the fact that you're engaging in extremely blatant goalpost moving, WebKit is open source and is being used by open source browsers like GNOME Web.

servo is a lot further along because they're not bothering with javascript and are just using spidermonkey. see WPT: https://staging.wpt.fyi/results/?product=servo&product=ladybird

So you believe that Mozilla was just "cutting useless bloat" on the sole basis that "If it was good Mozilla would’ve used it more"? Yes, I think I will stick with my own take. They dropped it because making web engines is expensive and they no longer wanted to invest in making a new one in Rust. It was good, that's the entire reason people are complaining.

Servo is not the old name for Gecko. Gecko existed long before Servo was started and Servo continues to be developed independently of Mozilla. It was a research project to develop a web rendering engine in Rust taking advantage of parallelization. The parallelization stuff mostly made it through the Quantum project several years ago, which did indeed help performance. That's about it. As of right now, Gecko's code base 55.4% C++, 22.6% JavaScript, 4.5% C, 4.3% Kotlin and a mere 3.8% Rust. If Servo had indeed been integrated into Firefox, over half of this would be Rust. 53.2%, if the current Servo repository is anything to go by.

laying off the servo staff at least was a mistake

Really, it would work for one religion plus its derivatives.