![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://fry.gs/pictrs/image/c6832070-8625-4688-b9e5-5d519541e092.png)
That is still source code, obfuscated but still source code.
That is still source code, obfuscated but still source code.
Counting in lines of code is the most stupid metric.
It works quite fine, use it daily. Well, XMMS2 to be pedantic.
Just some shellscripts bound to windows-keys to pause/play and load new files.
The question is whether x86 is even relevant anymore
Also RISC-V, though that is probably a few years away at least.
He could have handled it better. But he didn’t call the code crap directly, just the bundle of everything.
Having a meta package and let users choose seems like the best way. But this is a Debian issue, and not a keepassxc issue. It is up to Debian to package it anyway they want.
Exactly. And if you want those features, you install the full version. Packages can break in sid, that is the whole point of it.
I am also running sid and keepassxc and I see no problem with this change. In fact it seems like a very sane thing to do, and something I wished more packages did.
It is still just a “trust us” deal. They say they have deleted it, and all you can do is trust them. They could possibly get into legal troubles if it was shown they were lying, but that could be easily avoided as well.
GDPR is ok, but much of it is based on good actors doing what they should.
Why not just go full WSL?
Most of those cookie banners are not even needed, you only need them for tracking cookie, not login and session cookies. But of course everyone decided it is just easier to nag all the users with a big splash screen.
A lot of them are not even doing it right, you are not allowed to hint the user that accept all is the “correct” choice by having it in a different color than the others. And being able to say no to all shouls be as easy as accepting all, often it isn’t.
Basically, cookie banners are usually not needed and when they are they are most often incorrectlt designed (not by accident).
Then the bot would be useful, now it is just spam. If you want to watch it somewhere else: Use a browser plugin for it, don’t spam every thread.
Or maybe it is a feeble attempt to annoy people that sign up with foo+service@somewhere.com
and then sort it into different inboxes (of course you can filter on other things but + is built into gmail). You can also use it to see who sold your info when you get spam on that adress.
You would need to specify the new port when using ssh (using the -p$PORT option).
You can put a host entry for it in .ssh/config specifying the port.
And if it succesful, or at least passenger doesn’t boycott them over it, it is just a question of time until other airlines adds it as well