Re: Downvote bots. I can’t say they’re necessarily bots, but my instance has scripts that flag accounts that exclusively give out downvotes and then bans them. That’s about the best I can do, at present, to counter those for my users.

It is usually not a good idea to specify what your exact metrics are for a ban. A bad actor could see that and then get around it by randomly upvoting something every now and then.

There is also the risk of homograph attacks. The link below is for domain name encoding via IDN, but the same applies to usernames. You could easily impersonate another user by having chars that look similar.

https://en.wikipedia.org/wiki/IDN_homograph_attack

Sure, but even if they started tomorrow it would probably be years before it even could be considered experimental outside of the most daring early adaptors.

Having a combability layer is not ideal but it would mean they could have something worker for more users faster and at the same time see which modules/drivers they should focus on.

Sometimes they can be challenging or overgrown, so you have to know what you’re doing and be prepared to turn back if necessary, but I owe a lot of truly incredible experiences to this app.

Since it uses OpenStreetMap you should consider updating it for others later. Don’t think you can do it in Organic, but it can be as simple as in a browser adding a note to a trail about what state it is in.

“Thread closed due to inactivity.”

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.

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.