Anything realtime needs to be at least 60 fps, the closer to my monitor 144Hz the better. Something like a city builder or turn based strategy or non-time-critical relaxed co-op stuff is fine to be 30+.

I’d never want to play any shooter at lower than 60, no RTS, no racing game and so on.

I’ve got backups. Haven’t updated or looked at my server in months. If I’m ever compromised by missing security updates, I just load a backup and regenerate all keys.

I don’t put any critical data on public facing servers.

I just use the qbittorrent “search” feature. Add some of the search plugins for different sites that you can find when you open the search options.

*Arrs are nicer, but a lot to setup imo. qbittorrent you just download, open it when you need it, and then you’re done with it. If you don’t torrent a lot, it’s more time-efficient.

Until you run into some kind of problem :D

The close message should just say exactly this. If it’s one click to reopen, then the click is the response to your suggested notification.

Well the reason to auto-close is that this is not an entirely unlikely resolution. When I inherited a project with a bunch of issues and started going through the backlog, around 50% of tickets were duplicates, already solved, unreproducible, etc etc

When you’ve only got limited time, having less of those issues to analyze and then close anyway is a very valid reason. It leaves more time for fixing real issues. Of course it comes at the cost of ignoring perfectly valid issues as well, that’s why this is obviously never an optimal policy to implement, and should only be done in desperate situations.

That’s why the “easy way to reopen” is so important. Your concern is theoretically valid, but if tickets are usually ignored for years, then it really is a desperate situation for the project whichever way you handle it. You can decide between an endlessly growing list of issues that likely aren’t valid anymore, or pissing some users off.

I don’t really see why it would be harder to find an existing or similar bug. You should be looking (or rather you should be automatically notified) before/during creating a new ticket for existing tickets describing the problem. If a closed ticket describes the exact problem, you should be finding that too, and then should just be able to use the easy way of reopening if necessary. You should also be able to find the workaround in there if someone posted it.

It’s definitely not a beautiful solution, but if you implement something like this, the project is already in a desperate state, there’s not too much good choices there anymore.

I… know… that’s why I explicitly mentioned this already xD

I don’t think so. It should have an easy way of reopening - if it has, and you’re flooded with tickets on an open source project that you can’t possibly handle all, then it’s a good way to prioritize. Of course it doesn’t have an easy way to reopen here, which sucks, it’s some kind of locking instead of just closing it with a possibility to reopen.

Old tickets have a non-zero chance of the reporter being the only one to run into it because of a weird setup/usecase (and then abandoning the project), it being fixed by other work, or probably a bunch of other reasons it could be obsolete.

If no one cares enough to reopen it once every 6 months, then it’s probably fine to ignore it indefinitely.

I literally have a rpi4 and just put libreELEC on it

int toIncrement = ...;
int result;
do {
  result = randomInt();
} while (result != (toIncrement + 1));
print(result);

Also just noticed the site I linked also has performance per dollar pages, USA, new, non-used prices though. I would encourage to buy used.

I’m not sure if 16GB over 12 currently has a lot of effect. I currently have 16 and my VRAM almost never goes above 8-10 or so. Depends heavily on the game of course, but I think 16 is only really useful in the future.

That is for you to decide.

The way you decide is to go to a reputable review website like https://www.techpowerup.com/review/?category=Graphics+Cards&manufacturer=&pp=25&order=date and select one of the reviews of a relatively recent, unrelated card, for example the XFX Radeon RX 7900 XTX.

For this specific site, you then go to the “Average FPS” (or “relative performance”) page and look for your models you actually want to compare to in the list. Since you picked a relatively recent review, you can also see newer cards, so you can also see how much of an upgrade you’d get with newer cards you maybe haven’t considered yet.

In this case, the average fps of the 5700XT is 49.2, while the 6700XT gets 60, an improvement of ~22%. Now, you either know what 49 and 60 fps look like, or you go into one of your older games and use an fps limiter to limit to those fps values and play a bit and compare.

In any case, the final decision is up to you and no one can really tell you what you think your money is worth.

Edit: of course, this assumes your CPU is not a bottleneck. These tests always go with the most powerful CPU. You haven’t said anything about yours, so I assumed it wouldn’t be a bottleneck.

Imo it’s very unlikely that we grew to like music that already existed rather than growing to like audio patterns and then noticing we can make music.

Yep it’s pretty hard, also would like to know this, also no idea

Don’t worry, I’m not living under a rock and still had no idea. You need pretty specific knowledge for this to mean something.

Denylists itself make sense… Centralized ones absolutely not

I’m pretty sure most torrent applications have a “set location” button on the torrents, which automatically moves the torrent to the location you choose.

I know that qbittorrent also allows you to rename files and folders within the torrent.

The only thing that I have not seen possible is to change the directory structure within a torrent - i.e. move files one directory level up to “flatten” it. If a file is within three nested folders, then it is always like that, but you are able to change both the file and folder names, just have to do it from within the torrent client so that it can pick that change up.

But what you can always do is use filesystem links instead of moving the actual files around, keeping the actual torrent files in some invisible data directory and only “operating” on the links. Works more or less well depending on your OS :D

It’s absolutely not a skill worth having. If you ever run into issues and need the CLI, you can always get your knowledge right in that moment. If you already can do everything with your GUI and get the same results, getting the knowledge to do it some other way is just wasted time and duplicate work.