433 karma · joined October 31, 2016
A six-year-old filmmaker has as much claim to copyright protection as Spielberg and Tarantino. Just because one uploads to YouTube and one is paid millions of dollars by a major movie studio, it doesn't mean that they're different in the eyes of the law.
From what I understand, once a work is created, copyright is assigned to that work's creator. That creator may then license that work however they want. Quality doesn't factor in.
You shouldn't say anything to anyone who doesn't respect copyright laws - or, rather, you shouldn't have to. Your tax dollars, and the entity that you authorize to be the one to use force where you live, should be able to say whatever you, as the governed citizen, want to say to the person who doesn't respect copyright.
I hadn't heard this.
What do you do if you’re working in a fork of the project and you need to make those changes?
I’ve got a project broken down into modules. Module A uses module B. These are both checked into GitHub, so the module path is something like guthub.com/distortedsignal/my-project/src/a or whatever.
I need to make a change across both of these modules. Will my compilation pick up the changes?
What if I need to make a backward-incompatible change in b when b is a fully separate project?
https://en.wikipedia.org/wiki/Ottawa_Rough_Riders
These teams played <i>in the same league</i>.
Dolan's Wikipedia page blames him for the post-94 dip, which may be fair, but if that's the case, then he's seen them through two rebuilds, one of which culminated with a Stanley Cup Finals appearance (2014, if I recall). I'll never forgive him for not getting Hank a Cup, but sometimes these things can't be helped. Hockey is fickle.
The Knicks are a smoking crater, from what I understand, tho.
To give context for "only thing keeping The Escapist afloat" - this isn't the first time The Escapist has imploded. Around 2013/2014(?) there was a big blowup, I think The Escapist was bought out, and the new owners terminated a bunch of people and only (really) kept on ZP. The owners basically bought The Escapist for ZP. They ran as a skeleton for quite a few years, and recently (2021?) they started doing more stuff. Their 3 Minute Reviews have been pretty good, and the Cold Take series has been great.
This is disappointing for me. I thought they were going in a good direction. It's too bad that management decided that they didn't want to keep funding interesting, well considered voices.
I don't think anyone uses it, which is why I don't use it.
Maybe it's just more of a social network thing?
I hope you have a great day.
2. Yeah, I was trying to come up with a simple "can't be exchanged easily" things and I (pretty obviously) failed. Got any ideas of "can't be exchanged easily" stuff?
1. Unit of Account (https://en.wikipedia.org/wiki/Unit_of_account)
2. Store of Value (https://en.wikipedia.org/wiki/Store_of_value)
3. Medium of Exchange (https://en.wikipedia.org/wiki/Medium_of_exchange)
So think about a couple examples of these:
Goats would be terrible money. A unit of account that is "goats" would be subject to birth- and death-rates.
Sports game tickets would be terrible money - they're significantly more valuable before the game, and after the game, they're far less valuable.
Mountains would be terrible money. How could you exchange them, unless you were able to keep track of who owned the mountain?
Dollars are actually pretty good at all three. They don't die. They're pretty stable in terms of value. It's pretty easy to give someone Dollars.
Bitcoin are... ok... at some of these. It's pretty good as a unit of account - if you can secure your wallet. It's... ok... at being a store of value - there have been some very high-profile sudden value fluctuations that left people holding a bag. It's pretty easy to give someone Bitcoin, but not trivial. It looks like it costs about $1 to make a bitcoin transaction happen, where I can transfer a few dollars for free.
I'm not a Bitcoin supporter, but I don't think it's fair to malign the tech for things it actually can do.
But I understand that you're not interested in the discussion. Sorry that I assumed that you were.
Hope you have a great day!
- Who f-ing knows anymore? First, it meant factual, and now it means fictional.
- used to describe something that actually happens or exists.
- A good way to show that you are a[n overly-dramatic person]...
- Truthfully actual. Not figuratively. Used when not b-s-ing or by fake cats pretending not to.
I think this gives a good cultural cross-section of what the word means. If you want a (heh) literal definition of "literal", there are other "more professional" dictionaries, but if you want how people actually use the word, I think that UD gives a pretty good reference to how it's currently used. Language is chaotic, and that's a good thing! If it weren't, it would mean that thought and culture were stagnating (hot take, but I think I can back it up).
I think that my disagreement with your opinion is that you're a prescriptivist linguist, while I'm a descriptivist linguist. My preferred dictionary is one that describes how the word is currently used in its common cultural form. For obvious reasons, these are basically impossible to keep up to date. If I'm reading your philosophy correctly, you would prefer a more static, well described language. French is probably as good an example of a prescriptivist language that I could think of off the top of my head. Check out https://en.wikipedia.org/wiki/Acad%C3%A9mie_Fran%C3%A7aise for more on that.
I don't think either of us is "correct", but I think that each dictionary is useful in a specific place. If you're trying to write formal communication, then a prescriptivist dictionary is the best choice. However, if you're meeting a new person and you don't understand what they're saying because they use a word in a new or unexpected way, then a descriptivist dictionary is probably better.
Besides, how would you go about constructing a slang dictionary? Many of these words and terms and defined informally at best, and constantly contextually redefined at worst. Any attempt to create a static slang dictionary is going to be constantly under assault from the shifting landscape of language around it. I don't think there is any better example than the word "literally" in the last 20-25 years. In the mid-90's, it meant a very specific thing. Now, it's very different.
This is a PERSONAL store. Not a corporate store. If this gets busted, I’m out a lot of money, but my company is very safe.
If you have expertise here, I’d be very interested. What is your backup and restore solution? How do you guarantee that your files are safe?
I’m still not sure that we’re using the same definition of “air-gapped” here. From my experience, and air-gapped system is one that is entirely off the network. Like you said, one user, but the system is gapped because there is something dangerous on it. Airgapped systems are used for research. The user should always have root privileges (they can’t mess anything up too badly, and if they do, image the machine or dispose of it in a fire or whatever) so… again, why passwords? What do they do? What do they protect?
Being serious - if the system is already not able to get anywhere, nobody needs to authenticate on it or with it. If you have passwords there, they don't _do_ anything.
I'm pretty security minded - the word "security" is in my job role - but my password vault is in Google Drive. I need to have it on many machines, and I want it to be backed up. I know my limits - I don't have the hardware and software infra and expertise that Google does - so I trust them with that data. Could it bite me? Yes, but it would require someone a) downloading my passwords file and b) decrypting it. That's enough steps that I'm confident that I'm safe enough.
As someone in software security, I tell people I'm the fourth or fifth priority for any product. Function, Speed, and Simplicity are all ahead of me on the priority totem. I get it, but it's frustrating.
I'll be watching this. Thanks for the project!
I think this is a good tool, but not a great tool. Some refinement is needed, but the API is good, if sparse.