Re:Twitter Says Parts of Its Source Code Were Leaked Online
by wmf on Monday March 27, 2023 @12:56AM
(#35322992)
These terms have accepted meanings and I looked it up just to be sure.
"Being fired means that the company ended your employment for reasons specific to you. Getting laid off means that the company eliminated your position for strategic or financial reasons and not through any fault of yours."
Re:Twitter Says Parts of Its Source Code Were Leaked Online
by reaperducer on Monday March 27, 2023 @11:48AM
(#35328198)
It's somewhat a generational thing.
"Laid off" didn't really come into common use until the late 80's and early 90's when companies started caring about the PR hit from firing lots of people all at once. Think steel companies and car companies and coal mining companies.
Before that, you got "fired" whether it was your fault, or not. If you were lucky, you company specified you were "fired without cause," but that wasn't always expected.
In the 70's, my mother lost her job when an entire hotel was closed down. She wasn't "laid off." She was "fired." Although she called it "shit-canned."
I recently came across another term for it that they used in the 1940's, before "fired," but I can't remember it right now.
Re:Twitter Says Parts of Its Source Code Were Leaked Online
by wwfredrogersdo on Monday March 27, 2023 @11:54AM
(#35328275)
Are you saying that when “laid off” began being used 30-40 years ago it implied you’d be rehired? Because that’s the claim being made above about the current meaning of the term.
Edit: Wikipedia agrees that this is a generational difference and the term laid off used to imply it was temporary. Today I learned…
Re:Twitter Says Parts of Its Source Code Were Leaked Online
by wwfredrogersdo on Monday March 27, 2023 @11:50AM
(#35328217)
That is not what the terms mean. Firing implies let go for cause and laid off implies it wasn’t for cause. Being laid off doesn’t imply you could be rehired, perhaps you are thinking of the term “furloughed”.
Re:Twitter Says Parts of Its Source Code Were Leaked Online
by danso on Sunday March 26, 2023 @06:52PM
(#35320554)
I would think their identity is as subject to subpoena as any anon user at any social media service.
From the article:
> Twitter also asked the U.S. District Court for the Northern District of California to order GitHub to identify the person who shared the code and any other individuals who downloaded it, according to the filing.
I wonder if GitHub could be compelled to turn over ever IP that did a git clone?
Re:Twitter Says Parts of Its Source Code Were Leaked Online
by lapcat on Sunday March 26, 2023 @07:15PM
(#35320763)
> One concern is that the code includes security vulnerabilities
I find this kind of funny, because open source is typically viewed as a benefit as far as security is concerned.
Given how few engineers remain at Twitter, they probably ought to open source their code and allow outsiders to find and fix security vulnerabilities, freeing up Twitter engineers to figure out how in the world to generate revenue for the service.
Re:Twitter Says Parts of Its Source Code Were Leaked Online
by brianwawok on Sunday March 26, 2023 @08:08PM
(#35321180)
Right. Now go work for a f500. Ask if you can post your source code on GitHub to improve security? There isn’t some magic thing that posting your source does, except in the short term make 0 days 10000x easier.
Re:Twitter Says Parts of Its Source Code Were Leaked Online
by reaperducer on Monday March 27, 2023 @11:37AM
(#35328077)
Right. Now go work for a f500. Ask if you can post your source code on GitHub to improve security? There isn’t some magic thing that posting your source does, except in the short term make 0 days 10000x easier.
Doesn't seem to stop Microsoft, IBM, Chase, and others.
Re:Twitter Says Parts of Its Source Code Were Leaked Online
by wmf on Sunday March 26, 2023 @08:00PM
(#35321108)
Code that's intentionally open source tends to have better security long-term. Proprietary code that was accidentally leaked is pretty bad for security in the short term.
"Being fired means that the company ended your employment for reasons specific to you. Getting laid off means that the company eliminated your position for strategic or financial reasons and not through any fault of yours."
"Laid off" didn't really come into common use until the late 80's and early 90's when companies started caring about the PR hit from firing lots of people all at once. Think steel companies and car companies and coal mining companies.
Before that, you got "fired" whether it was your fault, or not. If you were lucky, you company specified you were "fired without cause," but that wasn't always expected.
In the 70's, my mother lost her job when an entire hotel was closed down. She wasn't "laid off." She was "fired." Although she called it "shit-canned."
I recently came across another term for it that they used in the 1940's, before "fired," but I can't remember it right now.
Edit: Wikipedia agrees that this is a generational difference and the term laid off used to imply it was temporary. Today I learned…
https://en.m.wikipedia.org/wiki/Layoff
"Laid off" meant you could collect unemployment for a while, and might be called back when conditions changed.
Like how coal miners would be "laid off" when the price of coal went down, but be called back when the price went back up.
From the article:
> Twitter also asked the U.S. District Court for the Northern District of California to order GitHub to identify the person who shared the code and any other individuals who downloaded it, according to the filing.
I wonder if GitHub could be compelled to turn over ever IP that did a git clone?
https://www.theverge.com/2023/2/14/23600358/elon-musk-tweets...
Interesting. I wonder what the repo was called, I imagine it couldn't have been anything extremely obvious or we would have heard about this earlier.
It wasn't obliviously named at all. The toplevel folders were:
- adp
- ann
- auth
- aws-dal-reg-svc
The README.md file just said "PublicSpace"
And the breakdown of languages used is odd for twitter: - Scala 56.2%
- Java 27.3%
- Python 7.9%
- Starlark 4.7%
- Shell 2.4%
- Thrift 1.2%
- Other 0.3%
I'll save you the trouble: Wayback only has the DMCA notice since the snapshot was taken today
I find this kind of funny, because open source is typically viewed as a benefit as far as security is concerned.
Given how few engineers remain at Twitter, they probably ought to open source their code and allow outsiders to find and fix security vulnerabilities, freeing up Twitter engineers to figure out how in the world to generate revenue for the service.
Doesn't seem to stop Microsoft, IBM, Chase, and others.
Or the Chase bank backend processing code.
Or the Chase bank fraud protection code.
...to boost Musk's tweets.