this post was submitted on 01 Jul 2023
4345 points (96.1% liked)
Mildly Infuriating
35405 readers
1823 users here now
Home to all things "Mildly Infuriating" Not infuriating, not enraging. Mildly Infuriating. All posts should reflect that.
I want my day mildly ruined, not completely ruined. Please remember to refrain from reposting old content. If you post a post from reddit it is good practice to include a link and credit the OP. I'm not about stealing content!
It's just good to get something in this website for casual viewing whilst refreshing original content is added overtime.
Rules:
1. Be Respectful
Refrain from using harmful language pertaining to a protected characteristic: e.g. race, gender, sexuality, disability or religion.
Refrain from being argumentative when responding or commenting to posts/replies. Personal attacks are not welcome here.
...
2. No Illegal Content
Content that violates the law. Any post/comment found to be in breach of common law will be removed and given to the authorities if required.
That means: -No promoting violence/threats against any individuals
-No CSA content or Revenge Porn
-No sharing private/personal information (Doxxing)
...
3. No Spam
Posting the same post, no matter the intent is against the rules.
-If you have posted content, please refrain from re-posting said content within this community.
-Do not spam posts with intent to harass, annoy, bully, advertise, scam or harm this community.
-No posting Scams/Advertisements/Phishing Links/IP Grabbers
-No Bots, Bots will be banned from the community.
...
4. No Porn/Explicit
Content
-Do not post explicit content. Lemmy.World is not the instance for NSFW content.
-Do not post Gore or Shock Content.
...
5. No Enciting Harassment,
Brigading, Doxxing or Witch Hunts
-Do not Brigade other Communities
-No calls to action against other communities/users within Lemmy or outside of Lemmy.
-No Witch Hunts against users/communities.
-No content that harasses members within or outside of the community.
...
6. NSFW should be behind NSFW tags.
-Content that is NSFW should be behind NSFW tags.
-Content that might be distressing should be kept behind NSFW tags.
...
7. Content should match the theme of this community.
-Content should be Mildly infuriating.
-At this time we permit content that is infuriating until an infuriating community is made available.
...
8. Reposting of Reddit content is permitted, try to credit the OC.
-Please consider crediting the OC when reposting content. A name of the user or a link to the original post is sufficient.
...
...
Also check out:
Partnered Communities:
Reach out to LillianVS for inclusion on the sidebar.
All communities included on the sidebar are to be made in compliance with the instance rules.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
As a former individual who understands the underlying systems, it seems like they botched deployment of a new feature causing issues and cannot figure out how to solve them.
Most of Twitter is and has been in maintenance mode since acquisition (think of 10 man engineering team and 1 left to handle maintenance).
This is why it cracks me up every time when someone is praising Elon for "cutting slack" when firing all those twitter employees. Yes, twitter did not implode immediately. Turns out, people can build software that is stable enough to run in maintenance mode. But good luck dealing with new issues cropping up.
People too far removed from IT/Dev team can become disillusioned as to what they do.
If you have a good dev team, you won’t hear about them doing anything until shit hits the fan. If you haven’t heard from them?… They’re doing their job. Leave them alone.
I don't think I've ever met a former individual. What happened? Was it like a Frankenstein thing?
Former individual is just the politically correct way to say dead guy.
Actually, he pissed of Captain Janeway and was erased from the timeline.
Used to be a nice guy before he became a former individual.
Or he got assimilated by the Borg. No longer an individual lol
I hadn't thought about that, but you're right. And it still could have been from pissing off Janeway.
Finally the people witty people came from Reddit
presumably they joined a hive mind
Nah, cloning gone wrong.
They federated with others.
From what I read they refused to pay Google for hosting services when the contract was up for renewal...which was June 30th.
A day that will live in Internet infamy.
Last day of the fiscal quarter. Changes tend to happen.
I heard similar; That this was the result of a migration away from Googles storage, which was cut off before they had the replacement fully set up. So they lost a ton of data and are severely limited in what they can display.
This is just what I've heard.
I've noticed that my batch image downloader works on maybe 40% of all twitter posts, and only 40% of the time (It used to work 100% of the time before Musk arrived). It's fucking annoying. I think they're having major API and CDN issues.
I heard similar; That this was the result of a migration away from Googles storage, which was cut off before they had the replacement fully set up. So they lost a ton of data and are severely limited in what they can display.
This is just what I've heard.
I heard similar; That this was the result of a migration away from Googles storage, which was cut off before they had the replacement fully set up. So they lost a ton of data and are severely limited in what they can display.
This is just what I've heard.
I heard similar; That this was the result of a migration away from Googles storage, which was cut off before they had the replacement fully set up. So they lost a ton of data and are severely limited in what they can display.
This is just what I've heard.
I've heard this multiple times from the same person even
wow me too, what are the odds
That's just what I've heard!
I heard similar; That this was the result of a migration away from Googles storage, which was cut off before they had the replacement fully set up. So they lost a ton of data and are severely limited in what they can display.
This is just what I've heard.
I heard similar; That this was the result of a migration away from Googles storage, which was cut off before they had the replacement fully set up. So they lost a ton of data and are severely limited in what they can display.
This is just what I've heard.
It's not a result of Google storage. Google served only for data analysis and batch jobs. These would not be sufficient enough to cause service degradation. Just a bad launch of a feature (via server side) that had unintended consequences.