this post was submitted on 25 Jul 2023

382 points (97.8% liked)

Enough Musk Spam

2956 readers

5 users here now

For those that have had enough of the Elon Musk worship online.

No flaming, baiting, etc. This community is intended for those opposed to the influx of Elon Musk-related advertising online. Coming here to defend Musk or his companies will not get you banned, but it likely will result in downvotes. Please use the reporting feature if you see a rule violation.

Opinions from all sides of the political spectrum are welcome here. However, we kindly ask that off-topic political discussion be kept to a minimum, so as to focus on the goal of this sub. This community is minimally moderated, so discussion and the power of upvotes/downvotes are allowed, provided lemmy.world rules are not broken.

Post links to instances of obvious Elon Musk fanboy brigading in default subreddits, lemmy/kbin communities/instances, astroturfing from Tesla/SpaceX/etc., or any articles critical of Musk, his ideas, unrealistic promises and timelines, or the working conditions at his companies.

Tesla-specific discussion can be posted here as well as our sister community /c/RealTesla.

founded 2 years ago

MODERATORS

jordanpeterson@lemmy.world

an0nym0us@lemmy.dbzer0.com

382

They should freaking hire anyone now having basic web development knowledge (i.redd.it)

submitted 2 years ago by fuckReddit@infosec.pub to c/enoughmuskspam@lemmy.world

25 comments fedilink hide all child comments

top 23 comments

sorted by: hot top controversial new old

[–] ArgentRaven@lemmy.world 74 points 2 years ago (1 children)

Hah, I bet I know exactly what happened. I did the same thing years ago. There's an import script you can run that'll move your domains and subdomains, which saves you a ton of time. But it often misreads your input, and puts a leading "." In front of everything.

I bet someone wanted to save time, and it happened to them. Then it's a game of catch-up to remove the leading period before the next TTL update.

This is exactly what happens when you're understaffed and overworked, and you have someone who isn't experienced in the process enough try to handle a big task.

Rookie mistake, Elon!

[–] SeaJ@lemm.ee 12 points 2 years ago (1 children)

They do not have the manpower to check any of that.

[–] kautau@lemmy.world 7 points 2 years ago

It’s ok someone will tweet it at musk and he’ll just keep firing engineers which will definitely help

[–] iByteABit@lemm.ee 28 points 2 years ago (2 children)

How did this even pass to production, do they just merge shit to main and pray to God it works?

[–] dustyData@lemmy.world 39 points 2 years ago* (last edited 2 years ago) (1 children)

Whenever you see this sort of technical problems from Twitter. Remember that Musk fired almost all of his staff. Including software engineers.

[–] BURN@lemmy.world 19 points 2 years ago (1 children)

And the ones he didn’t fire left en mass. At least the ones not tied down by visas and/or other red tape

[–] just_change_it@lemmy.world 0 points 2 years ago* (last edited 2 years ago) (1 children)

You underestimate the laziness of the typical office worker.

[–] BURN@lemmy.world 5 points 2 years ago

I am one of those lazy ass office workers lol. I’m sitting here at work on Lemmy, but even I would have been jumping off that sinking ship a long while ago.

[–] Katana314@lemmy.world 10 points 2 years ago (2 children)

When I think about it, this is actually exactly the kind of bug that very easily passes to production.

You have your dev environment; something like "katanasdevmachine.twitterdev.com", where you do your work and verify bugs. This environment is configured with a developer database, and developer URL configurations. So there might be "katanasdevmachine.twitterdev.com" simulating x.com, and then "briansdevmachine.twitterdev.com" to represent twitter.com. You and Brian do a test of the redirect from there, and all's well.

It's only when you're moving to the genuine domains that small URL-parsing/concatenating bugs might show up. But there's not many easy ways to "simulate" being on the actual twitter.com website with test code you've written. It's doable, just not convenient. So, these sort of URL configs can very often be the one place that bugs essentially go "untested" in an imperfect workflow.

[–] bronzle@lemmy.world 2 points 2 years ago

I mean, /etc/hosts, but I see your point. I’d guess this might be a case of, “this is pretty simple, we’re good to go”. then “oops”

[–] iByteABit@lemm.ee 0 points 2 years ago

Yeah that's true

[–] reddig33@lemmy.world 23 points 2 years ago (2 children)

Who would want to work for Twitter at this point? It’s not going to survive with Elon at the wheel.

[–] sci 31 points 2 years ago (2 children)

some indian contractors who would be sent back if they quit

[–] jungekatz@lemmy.world 5 points 2 years ago (1 children)

Musk literally laid off every twitter employee in India !

[–] TurtleJoe@lemmy.world 10 points 2 years ago

There are still employees in the US who have to keep working to keep their visas.

[–] Kalkaline@lemmy.one 8 points 2 years ago

Related question: what's the difference between a kiss-ass and a brown-noser? Depth perception.

[–] SmarfDurden@lemmy.world 16 points 2 years ago

That doesn't seem to be true anymore. I just checked and there isn't a "." there anymore.

[–] guy@lemmy.world 15 points 2 years ago (2 children)

Interestingly, you can break a lot of websites by adding a trailing dot to the URL, like twitter.com..

It's a perfectly valid URL, a fully-qualified one, and should resolve to the same place with or without the trailing dot. Some sites, like google.com. handle it correctly, but many fail completely, or fail partially, or at least don't preserve your login session.

[–] Starmina@lemm.ee 10 points 2 years ago (1 children)

back then it allowed to not have any ads served on youtube

[–] And009@reddthat.com 4 points 2 years ago

Strike 1

[–] kogasa@programming.dev 5 points 2 years ago

Suddenly paranoid that my 0 viewer per month personal site might not handle this correctly

load more comments