It’s not so much that they’re blocking it, as it is that they’re not implementing it. In GNOME, as I understand it, the Emoji picker is implemented by the toolkit (GTK). That means that apps that don’t (fully) use that toolkit, such as Chrome and Firefox, will need to add the implementation themselves. That is now done for Firefox.

Yes, but that didn’t work in Firefox before this change. The whole point of this change is to make that work in Firefox as well. (Likewise, it still doesn’t work in Chrome, Chrome-based browsers, and Electron apps.)

So the situation in which this makes sense is when you’re using Gnome.

What would it mean for you to call it yourself? This change is just so that if you press Ctrl+. in Firefox, the native emoji picker shows up, so at least in that sense you’re invoking it yourself? (Before this change, Ctrl+. would do nothing in Firefox, even though it would show the emoji picker in normal GTK applications.)

Well, if this happens:

The plan is however to open source when Orion is self-sufficient (business model of Orion is you are the customer and can pay for it - like we used to pay for browsers 20 years ago before advertisers started paying for our browsing), meaning it can sustain its own development independent of Kagi Search.

https://news.ycombinator.com/item?id=46554890

I guess the main question is: will they open source it if they feel the need to cancel it? Either way, given that it doesn’t seem to have any particularly distinguishing features yet, that there are plenty of quality open source browsers, I’ll wait until they’ve reached that point.

Sounds like KDE is also doing a lot of work that will be helpful on phones, nice!

Didn’t read to me like OP was arguing for a single alternative.

Mozilla Public License, and there are a number of forks. A browser is a lot of work though.

deleted by creator

Give me Flatpak and atomic distros, I’m too old for maintenance. Give me some of that good dumbing down, cause I’m dumb.

They might be thinking about Winboat, which, as I understand it, is basically running a VM in a container, and then running Windows in the VM.

Yeah exactly, suing them for non-compliance would be more effective, though of course, also more effort. That said, it sounds like in this case, just asking them would’ve worked as well, which is a lot less effort 😅

Ah right. So I guess my point was: the DMCA takedown doesn’t necessarily force them to publish the code on GitHub, although luckily in this case they did end up doing that.

I’m not sure I follow that sentence?

The first thing that came to my mind is that a DMCA takedown on GitHub doesn’t stop them from using it, but only from sharing their own additions with the world.

Haha yeah, I’m not super up-to-date on Bazzite, but I believe it doesn’t add much on a Steam deck. (And if you don’t want your other devices to boot up into Steam, you probably don’t want it there either.)

Being able to install it yourself on any device seems like a big advantage :P

Yeah unfortunately i can’t quite recall the context, but I think they were attempting to make encrypted storage the default, but then that broke on existing databases or something? It was a pain at least, I know that much 😅

(Although would be less of a pain nowadays, now that Signal has proper sync to restore my history.)

I mean, I use the Flatpak, but I have also run into breakage concerning the experimental support, resulting in Signal Desktop no longer being able to start, and me having to track down a GitHub issue with a workaround. I can imagine wanting to run the Distrobox just so you’re closer to a system that the upstream developers actually test with - not so much to avoid running a single command, but to lower risk of breakage.

Not by default, IIRC, and the integration is still marked as experimental - so just what the readme is saying.