russjr08 @ russjr08 @outpost.zeuslink.net

Posts

2

Comments

525

Joined

2 yr. ago

As far as I'm aware, none of the music services really have a direct transfer option available. You pretty much have to use a third party service to do so from what I found the last time I tried to do a major switch.

Funnily enough, I feel like this is one of those things that are present day "AI" could probably help with, if it were integrated with these services. Realistically you'd just need something to do some OCR of images from your playlists, and match the results - I'm kind of surprised that's not something Spotify, Google, etc have done yet.

It is not, unless they perhaps have a YT Music-only subscription but I haven't seen such.

Edit: It looks like there is a YT Music Only subscription available, for $3/mo cheaper. I'd still say if you use YouTube any more than just on one-off occasions, its still worth picking up regular YT Premium if you're grabbing the music one anyways, but at least the option is there.

I believe what they are saying is, they don't judge how other people spend their own money.

I'll preface this with I don't do any workstation-tasks that are being mentioned here, I can only speak from a regular desktop/slight gaming user but...

I'd agree with this take. I have an Nvidia 2080 right now, and at the start of the new month I'm looking to try to pickup a 6700XT (I have a low budget as well, so its about the best I can shoot for) because I've hit my limit with Nvidia's shitty Linux support. An X11 session feels like crap because the desktop itself doesn't even seem like it renders at 60 FPS (or rather, not consistently, but with a ton of framedrops) - and I only have two 1080p 60hz displays... should be easy for this card. A Wayland session feels "smooth", but is glitchy as hell due to a multitude of reasons. It is only just now (as of the 17th IIRC) when they've released their 545 beta driver that Night Light/Night Color is finally working on a Wayland session, because they lacked GAMMA_LUT support in their driver... But now XWayland apps feel even worse because of this problem. This is not going to be fixed until either Nvidia moves their driver to using implicit sync, which won't happen - or they actually manage to convince everyone to move over to supporting explicit sync, which requires the proposal being accepted into the standard (something that will take a while), and all compositors being updated to support it.

I am on the opposite side of OP, I don't do any sort of rendering/encoding but I spend a fair amount of time gaming. The XWayland issue in particular is basically the deal breaker since still most things use XWayland.

While I do hear that Nvidia is the choice for anything that needs NVENC or CUDA, using the desktop side of things will feel horrible if you go with an Nvidia card as your primary, and you'll constantly be trying to chase workarounds that only make it slightly better.

I'd really rather not spend money on a new GPU right now as a friend gave me his old 2080 that I'm using at the beginning of the year, specifically because money has been really tight for me - but when you try to use your PC (and I work from home, so that's a major factor) and you feel like you're constantly having to fight it every. single. day just to do the basics, well... enough is enough. I've heard some Nvidia users say that it works perfectly fine for them, and that's fantastic - but that has not been remotely close to my experience. It's just compromise after compromise after compromise. I hope that the NVK driver will change things for non-workstation workflows (since I don't imagine you'd be able to use NVENC/CUDA with NVK) but the driver isn't ready for production use as far as I understand.

At the very least, if you're able to keep both your AMD card as your primary, and just add in the Nvidia GPU then you can use Nvidia's PRIME offloading feature to run applications specifically on the Nvidia GPU. This has... its own fair share of problems from what I've heard, but the issues I've seen in passing have generally been on the gaming side, I'm not 100% sure how it does for things like NVENV/CUDA. Sadly for me, I don't believe my case/board actually has enough space for both GPUs to be in there, and even if it did, it certainly wouldn't have enough room with my extra PCI-E WiFi adapter in there - but that's a bridge to cross when I get there, I suppose.

I guess my conclusion for the OP is, how is your current desktop experience with your 1050TI? If it hasn't been a hindrance for you, then perhaps you're fine with your current plan - but as the Linux ecosystem starts to move more towards Wayland being the only realistic option to use, I do fear that Nvidia users are going to suffer a whole lot until Nvidia can finally get their act together... but I suspect there will be a massive lag time between the two.

Yeah if it's the comment chain that I think they're referring to, I believe it came down to Mozilla "being in bed with Google" because Google is the default search engine.

I'll take the default search engine being Google over things like affiliate links being hijacked, but maybe I'm crazy for taking that position.

Yep, my desktop PC may or may not have one of its SSDs not mounted...

If someone on server B were to boost that posts from server C, then yes they'd show up on server A as far as I know - but only if they're boosted. The federation aspect works a lot like Lemmy's, so while my instance my federates with lemmy.world (and vice versa), my instance doesn't know about the communities on LW unless someone on my instance subscribes to that community in particular (and vice-versa for a community on my instance not showing up on LW until someone over there subscribes). At least, that's how I understand it - to be honest I still don't have my head completely wrapped around Mastodon's federation aspect but since both Mastodon and Lemmy use ActivityPub I'd reckon that they're very similar.

Oh I didn't even notice my instance had made it onto the "All" section there, that's pretty cool!

It's done through a similar mechanism, you can paste the URL of a user on a different Mastodon search which triggers the same style of search as it does on Lemmy. Mastodon has relays (an admin needs to add/subscribe to one, and the relay has to confirm/accept) however which can also help "kickstart" Federation so to speak as well - which is like blasting a firehose at an instance.

Interesting, sounds like they're killing the wakelock that Caffeinate acquires then (which is what actually keeps the screen active), rather than killing the whole app itself.

That's another one of those issues that I don't think there's too many workarounds for. Theoretically I might be able to have the app check to see if the wakelock is still active and if not, re-acquire it... but if there's no way for the app to "know" that the wakelock has been killed in the first place, the only way around it would be to constantly ask Android "Is the wakelock still active? Is the wakelock still active? Is the wakelock still active?" over and over again, which would definitely lead to battery issues.

I do know it works on some Samsung devices, as I bought an old A2... something to test it on, and couldn't find any signs of a problem there.

I mean hell, I'd love for there to be a way to not even require a wakelock for Caffeinate, but the only other way is a "soft" wakelock, in which you tell Android "Never turn the screen off while my app's window is open", but of course that would mean you'd need to keep the actual app window in the foreground and would defeat the whole purpose (such as my favorite usecase, keeping the screen on while I'm reading a recipe - or keeping the screen on while I'm tracking a delivery from a food delivery application).

If you're on an EFI based system and have systemd, you can use systemctl reboot --firmware-setup to get into BIOS!

Dark theming is definitely a fair point, I'll definitely need to have a look into that.

Material You support is probably going to be out of scope though, as I feel that would be making it complex for the sake of being complex.

I do want to learn more about the Material You API that being said.

Well I definitely am glad to hear that! Yeah the situation is just unfortunate, as there's really nothing I can do for the users who are getting the issue - since as you've seen, Caffeinate is already really light on RAM usage (which would normally be one of the only ways to try to remedy the issue as a developer, from what I can tell).

In the end I just decided to keep it compatible for all mobile devices, though I did consider adding a "compatibility warning" type of banner to the app or a one-time notification for devices that had a small amount of RAM. Eventually the emails stopped coming in about it though so I figured either the problem ended up resolving itself as updates to the platform occurred, or everyone who was going to run into the issue already ran into the issue. I've pretty much considered the app to be feature complete now, short of any Android changes that break it (such as when notification channels was introduced, followed by full-on notification runtime permission requirements).

I'm curious about what you mean by the issue with Android's security model. Apps can have whatever package name they want (... Well, I am sure you can't publish a com.google package on the Play Store) so that doesn't make sense.

The only thing I can imagine you're referring to is data sharing between applications signed with the same key, but that's not the package name.

And you really don't want it to either. That could cause all sorts of privacy issues if you accidentally include private information in the conversation - and as far as I have heard it is harder to remove information from LLMs than it is to "add" information to it.

Also Microsoft's Tay could adapt itself based on conversations and that went real well...

Someone could've compromised the materials used to build the CPU, better assemble the atoms together one by one.

Maybe your bug report didn't get collected into the other bug report, but it'll be resolved for Plasma 6 thankfully!

Or AMD, apparently. The bug report for this issue was explicitly renamed to say "Non Intel GPUs" - even though it seemed to be more likely(?) to happen to Nvidia users.

As far as I understand, its the major push for moving forward with Wayland and dropping X11 as fast as possible yet Wayland still doesn't work for a lot of workflows (say, making use of global hotkeys, or Nvidia users, etc).

Welcome to the Fediverse! Hello from Lemmy!