The list is compiled by the MPA, a group that represents studios, etc. They work with our government, and to which degree I have no concrete idea, (edit: a trade association is supposed to work with governments on behalf of it’s members) but they merely submitted this list to our government. That’s according to the article and the torrent freak source.
I think the article wasn’t being clear and other comments seem to agree.
Terminating service over allegations of piracy. Kicking someone off the internet because an automated copyright system accused them of piracy. That’s crazy.
deleted by creator
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?
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?
And because corporations aren’t people, here’s the CEOs that ran things during 2014:
Hans Vestberg (b 1965) Verizon
Randall Lynn Stephenson (b 1960) AT&T
Glen F Post (b 1952) CenturyLink
We let these people act with impunity in our society but it doesn’t need to be this way. Look at how Elon, who thrives on attention, flips out over being tracked and heckled. They stole hundreds of billions from us but we don’t even act like it.
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.
When a computer reads some signal, the 0s and 1s in it’s memory is the data. The data must be processed so that the computer can understand it.
This computer is using threads to read neuron activity. It must necessarily receive data because if it didn’t it wouldn’t be reading neuron activity. They’re the same thing.
This data is processed so that the computer can make sense of the brain. Once it understands some activity it generates signals that can control external devices.
Here’s an example. Imagine a device that monitors the heart and does something to fix a problem. The device would get data on the heart and process the data so that it can perform it’s function.
Wouldn’t monitoring health concerns and mitigating data loss be extremely important in these scenarios?
Put it this way: If you took a thread talking about some tech from a joke community, and a thread about the same topic from a generic technology community, you won’t be able to tell them apart. People will bring the same energy and mindset to both. Jokes and “lol get rekt company I hate” will be pushed to the top, because they totally contribute to the discussion, while basic observations like “removing functionality is bad” will be pushed down. 👍
Not SO or it’s methods, I mean the human experience. It can be awkward to be new to it all and to feel the frustration/tunnel vision associated with being stuck on one problem… and then step back and have to dissect your issue, structure your question correctly, etc.
It’s just how it is, for exactly the reasons you stated. You can capture every little problem people face in programming, or you can hone in on useful patterns in goals, problems, and solutions, and educate people on how to see these things.
The idea of SO is a little awkward too I think. With something like Wikipedia we’re presumably in an academic mindset. Carefully gathering information, sources, structuring it all. And even then people can get turned off by the ‘bureaucracy’ or nitpicking or whatever.
When people show up at SO they’re probably more in a “I can’t figure this damn thing out!” mode. We’re struggling with a problem, keeping a bunch of junk in our head, patience being tested, but we’re still expected to have a bit of academic rigor in our question and discourse.
Yeah but a lot of people don’t really know what SO is for. They think you just go there and get help and call it a day. But the entire point is to produce structured questions, discourse, and answers aimed at future readers. Super specific, no-context, or duplicate problems are not useful. If you are not trying to generate useful content, don’t go to SO.
Just look at all the people getting frustrated at being told “you should probably do it a different way.” They really don’t understand that just because they’re asking the question, it’s not all about them.
Isn’t “it’s good enough for most users” a little too close to “it’s good enough to be bought, used for a bit, and then tossed”? Usually computers that were adequate for X stop being able to do X. There’s little to no margin and you can’t upgrade it?
I don’t get it, what makes the output trustworthy? If it seems real, it’s probably real? If it keeps hallucinating something, it must have some truth to it? Seems like the two main mindsets; you can tell by the way it is, and look it keeps saying this.
A hidden device implanted on our cortex at birth should detonate when we suggest something like “We should let corporations solve global warming.”