Next time an artist makes a big deal about being ripped off I’m going to contrast “working hard and then getting ripped off” with “underregulated industry manipulating society for profit” and probably just pirate.

deleted by creator

How to “block” ads: Refresh the video multiple times. They will show a few different ads and then give up. It even works on console YT apps which have more ads.

I guess it affects impressions? I figured they would have fixed that, but this still works so whatever.

From what I can find, by “These routers send your credentials in plaintext”, they actually meant to say, “The mobile app sends credentials in plaintext.”

If you use the web interface then your credentials are not sent in plaintext. The routers themselves also don’t send credentials in plaintext.

The people who found this out got that wrong, and a lot of people are confused because they didn’t expand on “in plaintext.” They could be a little more professional / thoughtful.

Edit: I’m also thinking about the “may expose you to a MITM” bit. I think if it was https then a MITM (assuming all they can do is examine your packets) wouldn’t work because the data can only be unlocked by the private key. It sounds like it was an http connection?

That’s what I said. Free licenses are for free software, while copyleft is for “free software.” Copyleft is because corporations like Xerox will act in bad faith, etc. Free licenses are for free software. Copyleft is for Free Software, The Movement. People aren’t cucks for not deigning to make every piece of code they write part of some statement.

Permissive licenses are truer to the spirit of free software but copyleft, while kind of a copout, seems more pragmatic due to corporations. I wouldn’t avoid copyleft licensing on principle or anything but it feels incongruous to want to make something freely available to all but then nitpick over how they use it.

It’s new to me, I think it’s saying that your system is built up by you declaring what you want in a file, a single source that everything comes from.

It’s atomic because each action the system takes is carefully completed rather than bailing out and requiring you to fix something.

It’s immutable meaning you declare how you want things to be set up and then critical changes stem from those declarations and nothing else. You would obviously generate preferences, save data, etc. but the files that make the system / packages work are carefully locked.

It’s like the concept of flatpaks + structured system defining + modern common sense OS operations?

No problem. I’m no guru and I’m currently on Zig but I think learning some Rust is a really fast way to hone skills that are implied by other languages.

You use lifetimes to annotate parameters and return values in order to tell the compiler about how long things must last for your function to be valid. You can link a specific input with the output, or explicitly separate them. If you don’t give lifetimes the language uses some basic rules to do it for you. If it can’t, eg it’s ambiguous, then it’s a compile error and you need to do it manually.

It’s one of the harder concepts of rust to explain succinctly. But imagine you had a function that took strA and strB, used strB to find a subsection of strA, and then return a slice of strA. That slice is tied to strA. You would use 'a annotation for strA and the return value, and 'b for strB.

Rust compiler will detect the lifetime being shorter than expected.

Also, ownership semantics. Think c++ move semantics. Only one person is left with a good value, the previous owners just have garbage data they can’t use anymore. If you created a thing on the heap and then gave it away, you wouldn’t have it anymore to free at the end. If you want to have “multiple owners” then you need ref counting and such, which also stops this problem of premature freeing.

Edit: one more thing: reference rules. You can have many read-only references to a thing, or one mutable reference. Unless you’re doing crazy things, the compiler simply won’t let you have references to a thing, and then via one of those references free that thing, thereby invalidating the other references.

Not going to X (or any wrappers) but I’m curious what “supported games” means. Because I would expect that it’s actually “games that support timeline markers” like how they integrate rich presence. Devs could just use a new header and implement this nifty feature.

I don’t see a negative. It’s foss so you ought to be relaxed about others using your code. The issues are probably just articulating problems that were already there. If it’s stuff you don’t care about… it’s a foss repository so you just ignore it.

The other day I was trying to disable Ubuntu Pro stuff and the way to do it reminded me of Windows. Once I get my media backed up I’m switching to another distro, just not sure what one yet.

I don’t understand feeling those things and then choosing to buy a Sony game that requires a Sony account, normalizing and supporting such practices. Giving people money is far more of a normalization tactic.

Burning CDs. That’s how I know most people didn’t know how to do it, or want to put in the effort. You had to go buy a stack of CDs, hope your computer supported burning, had to make sure players could support the burned disc (depending on if you made a music disc or data disc, if it was rewritable), and spend the time to burn the disc.

Contrast that to ctrl+c ctrl+v.

There’s more people who can ‘duplicate’ digital files than there were people burning CDs.

The amount of people who will duplicate their tapes and CDs would be lower than the amount of people who will duplicate their digital files.

Most of the time when a law sounds silly for banning something when alternatives exist, it’s because people themselves are silly and don’t actually go for the alternatives at the same rate as they would the banned thing. Ie gun accessory bans, ninja star bans.