Was playing it a bit in the morning while it was slow at work, seems fantastic so far!

I hate how installing or removing (or even updating) a flatpak causes the whole software center to completely refresh, and it doesn’t keep its state so if you were in the middle of a search or scrolled down through a category… say goodbye to it.

Generally it’s just through my distro, it’s always occurred since I’ve used KDE unfortunately (since that was one of my first thoughts). This has been across Fedora (and derivatives), Nix, Arch, and Kubuntu.

As far as I know, if you don’t have it on Steam then yes.

The Steam build still gets all of the updates to the game… for now, so if you grabbed it on Steam before it was delisted you can continue to play through that.

This doesn’t read as a global Blocklist for all Android phones in the world. It reads more as a local database/API for blocked numbers on your phone.

So blocked numbers would theoretically be applied to your messages apps and other “telephony” based apps that use phone numbers such as WhatsApp (should said apps implement the API).

Google already seems to have a spammer database for numbers, though I’m not sure if that applies to just Fi users, Pixel users, or anyone who uses the Google Phone app. If I have call screen disabled, I’ll see numbers on an incoming call have a red background with a “likely spam” description.

But based on the comments on this post, I feel as if I’ve overlooked something in the article here (I’ve just woken up so it wouldn’t surprise me) - is there a mention of it being a worldwide list?

It would be an alright show… If it didn’t use the Halo name and was written to just be another science fiction/fantasy TV show.

But unfortunately I don’t think the show was ever made for hardcore Halo fans - whether that’s because of the writers or just Paramount going over the writer’s heads I couldn’t say.

Once I woke up a bit more I had another look at the article, and this phrasing certainly makes it sound like it needs approval at some point:

Due to a licensing dispute between NVIDIA and Activision in 2020, GeForce NOW lost access to all Activision-Blizzard games.

Perhaps though it’s a case of “Better to ask for forgiveness than permission” and they just add games until someone tells them to pull it off, I’m not sure. It’s been 4+ years since I looked into GFN, I tried it out during the beta period but I don’t believe I’ve used it since then.

They might’ve done so out of necessity. I don’t know if the dev(s) of the Simple Tools apps were working on it full time, but if they were and just not enough contributions were coming in from it… Well everyone has to eat.

As the saying goes, “everyone has their price”. It’s easy to condemn the developers for their choice until you’re in the exact same scenario as they were. Whether that’s because they were starving, or even just offered enough money to make their lives a lot easier - not too many people would turn it down.

deleted by creator

I’m a bit surprised to see that you disagreed with the “NixOS is hard to configure” bit, but then also listed some of the reasons why it can be hard to configure as cons.

By “configure”, they probably didn’t mean just setting up say, user accounts, which is definitely easy to set up in Nix.

The problems start to arise when you want to use something that isn’t in Nixpkgs, or even something that is out of date in Nixpkgs, or using a package from Nixpkgs that then has plugins but said plugin(s) that you want aren’t in Nixpkgs.

From my experience with NixOS, I had two software packages break on me that are in Nixpkgs - one of them being critical for work, and I had no clue where to even begin trying to fix the Nixpkg derivation because of how disorganized Nix’s docs can be.

Speaking of docs inconsistencies you still have the problem of most users saying you should go with Flakes these days, but it’s still technically an experimental feature and so the docs still assume you’re not using Flakes…

I was also working on a very simple Rust script, and couldn’t get it to properly build due to some problem with the OpenSSL library that one of the dependent crates of my project used.

That was my experience with NixOS after a couple of months. The concept of Nix[OS] is fantastic, but it comes with a heavy cost depending on what you’re wanting to do. The community is also great, but even I saw someone who heavily contributes to Nixpkgs mention that a big issue is only a handful of people know how Nixpkgs is properly organized, and that they run behind on PRs / code reviews of Nixpkgs because of it.

I’d still like to try NixOS on say, a server where I could expect it to work better because everything is declarative such as docker containers - but it’s going to be a while before I try it on my PC again.

Correct on all accounts. Just to be more precise, I’m not placing any blame on the players in my prior comments - the blame goes to GFN and Activision since the player expects to be able to play a game that they’ve paid for, on a service that they have paid for.

Right, I didn’t mean to imply that playing on GFN was cheating by any means - I probably should’ve worded that a bit better.

I meant more of “If Call of Duty explicitly allowed GFN to add the game, then players who play via GFN shouldn’t have a chance to be banned just for playing through it”

Doesn’t the publisher of the game have to approve for a game to be put on GeForce Now?

I mean, don’t get me wrong - I know anti cheat detection has never been perfect, but you’d think this would be something they heavily try to make sure they get right.

No VPN, it’s strange because I haven’t had a problem with any other services that use IP geolocation (which I assume is what KDE uses) - even Gnome’s auto location tool seems to work fine.

Oh wow, I didn’t know about Kandalf and KDE valley, that’s awesome!

Looks fantastic! Although, speaking of the Night Color settings - does anyone know how the location data for the auto night color mode is sourced? It always seems to place me on a different continent…

This bug was the nail in the coffin on Nvidia for me and I finally picked up a 6700 XT to replace my 2080 this month…

But, when I was on my 2080 trying out Wayland, I of course always noticed this bug on actual apps themselves (such as my IDE…) but it didn’t always manifest in games, at least not till 545 came out.

Not sure why, since of course most games are run through XWayland. Perhaps they’re in a similar situation and I’d be curious if they opened something like Discord, if they saw it there.

It never should’ve gone out in the first place. Whether it was ever going to be a good idea (I do not believe so) is something that can be debated elsewhere, but it definitely was not a good idea with the current state of Bungie and Destiny 2.

Am I surprised that someone higher up in management pushed/green-lit the idea? No.

And no Bungie, you do not get brownie points for seeing the train wreck (that they were completely tone deaf enough to cause in the first place) and being like “Oh we can see that this was not bringing joy, we’ll pull it… for now”.

What?

First of all, after the shitshow that was the launch of D4, that’s just hilarious. S2 is certainly better than the start, but it is no holy grail that magically fixed everything.

Secondly, you’re dreaming if you think a DLC is worth more than the base game.

And finally, I like how they’re “asking” players if they’d “be okay” with it. Are you telling me that if the majority of the player base said “NO!” they’d actually listen? If there is anyone who believes that, well I’ve got a bridge in Sanctuary to sell you.

Ah I see, that’s unfortunate then. For what its worth, I still think the bot is a great idea for discoverability and bridging the two services together! I hadn’t seen it before since I usually have bot users muted and happened to see this comment chain while logged out.

I’ve given it a follow from my Mastodon account since I do tend to miss quite a few cool Lemmy posts it seems, and I think it’ll help me find some communities in general that I’ll want to subscribe to from over here.