Smaller doesn't matter if they're going in a 3.5" tray. There are some models that only come with 2.5" trays, but go figure, the only 2.5" model that isn't a 5-figure all-flash enterprise-scale model is one of our least popular models
Eccitaze
joined 2 years ago
I work tech support for a NAS company and the ratio of HDDs to SSDs is roughly 85-15. Sometimes people use SSDs for stuff that requires low latency, but most commonly they're used as a cache for HDDs in my experience.
I don't think that most of us are outright fascist, but I do think most of us are not just apathetic, but also willfully ignorant. For one reason or another--lack of education, viewing politics as "boring," no energy to pay attention beyond headlines, a lack of media literacy--most Americans simply cannot see the impact an administration has on society beyond their immediate experience. For these people, Trump was a guy who said stupid shit, lowered their taxes (ignoring the sleight of hand where the 'tax cut' was almost entirely due to changes in tax withholding so the extra money on their paycheck was counterbalanced by a lower tax return), and held a rally when he lost. They're not explicitly fascist--if the tanks start rolling down their town's Main Street, they'll wail and moan about "I never wanted this, how could this have happened"--but to them, things like "economics" or "human rights" or "democracy" or "equality" are boring toys that nerds play with. They're the type of person that complains about crumbling roads and potholes and bad traffic, then turns around and complains about construction projects to fix the very things they were complaining about.
So I don't necessarily fully agree that America is more fascist than we like to admit, but I think it's largely a distinction without a difference--most Americans are perfectly happy to stand by and let fascism take the reigns, to do nothing and complain about anybody who does try to fight against it, right up until it's too late and THEY'RE the ones up against the wall.
The public has the memory of a goldfish. We're less than 3 years out from the single worst administration in the history of this country, and we're seriously considering putting him back in office.
Did you see Dutch Oven? Holy fuck that's the scariest robot I've ever seen!
You need to learn your Internet history. It wasn't so long ago that we had a diverse, interoperable community of instant messaging platforms based on XMPP, an open, federated protocol. Anybody could host their own XMPP server, and communicate with any other XMPP server. Then in 2006, Google added XMPP support to their Talk app and integrated it into the Gmail web interface. But there were problems:
First of all, despites collaborating to develop the XMPP standard, Google was doing its own closed implementation that nobody could review. It turns out they were not always respecting the protocol they were developing. They were not implementing everything. This forced XMPP development to be slowed down, to adapt. Nice new features were not implemented or not used in XMPP clients because they were not compatible with Google Talk (avatars took an awful long time to come to XMPP). Federation was sometimes broken: for hours or days, there would not be communications possible between Google and regular XMPP servers. The XMPP community became watchers and debuggers of Google’s servers, posting irregularities and downtime (I did it several times, which is probably what prompted the job offer).
And because there were far more Google talk users than "true XMPP" users, there was little room for "not caring about Google talk users". Newcomers discovering XMPP and not being Google talk users themselves had very frustrating experience because most of their contact were Google Talk users. They thought they could communicate easily with them but it was basically a degraded version of what they had while using Google talk itself. A typical XMPP roster was mainly composed of Google Talk users with a few geeks.
Only a few years later, Google would discontinue Google Talk, migrated all their users to Hangouts, and decimated the XMPP community in an instant. Most of the Google users never noticed, outside of some invalid contacts in their list.
That's why everyone distrusts Meta. Even with Threads being a relatively unsuccessful platform by commercial social media standards, its active userbase still dwarfs the entire Fediverse combined. There's absolutely nothing stopping Meta from running the exact same playbook:
-
Add ActivityPub support, but only partially
-
Add new features to ActivityPub without consulting with the rest of the Fediverse or documenting the extensions, degrading the experience for everyone not using Threads
-
Entice Fediverse users to migrate to Threads--after all, why use Mastodon or Lemmy when 95%+ of ActivityPub traffic originates from Threads?
-
Deprecate ActivityPub support after most of the Fediverse is on Threads, leaving it smaller and more fragmented than if Threads had never federated at all, while forcing everyone who migrated from another Fediverse platform to Threads into an impossible choice between abandoning the vast majority of their contacts or subjecting themselves to Meta's policies, tracking, and moderation
I'd bet the ticket slipped through the cracks--it might have been pulled by an agent near the end of their shift who thought "I'll respond first thing tomorrow" and was let go the next day, or the ticketing system glitched and improperly took it out of the queue, or a tier 1 agent didn't follow proper escalation procedures and reassigned it to someone who never bothers to check their ticketing queue.
I'd suggest submitting a fresh ticket along the lines of "Following up re: ticket 29XXXXX" and copy-pasting the original message into the new ticket.
Source: work for a different company's support team that also uses a public-facing ticketing system
Who says the government has to hire anyone? Have the sysadmin set it up, have your existing Twitter staff swap to using mastodon, done.
The entire point of the season 1 finale is that if Pike's fate gets retconned it'll turn out very, very poorly. If Pike doesn't end up the way he did in TOS, it means he doesn't vacate the captain's chair on the Enterprise, and when the events of Balance of Terror happens, Pike's inclination towards compromise and peaceful negotiations leads the Romulan empire to conclude that the Federation is weak and declare war, causing the death of millions. Future!Pike even says at the end "every timeline where you don't end up in that accident ends up with something horrible happening, and someone else taking your place."
Hell, I've seen accusations that the author of this mod made literally that exact mod for BG3 that "fixed" Wyll and his father by turning them white. Shit's disgusting.
That makes literally zero sense, because the 14th Amendment bars anyone from holding any civil or military office who engaged in insurrection. And before you go on about "well durrrrr the presidency isn't an office," the constitution refers to the presidency as the Office of the President of the United States repeatedly:
Article 1, Section 3:
Article 1, section 3:
(This provision is especially important because it means that if the presidency isn't counted as an office the president is literally immune from impeachment because there's no provision in the constitution to actually try the president for impeachment.)
Article 2, section 1:
12th Amendment:
22nd Amendment:
I could go on, but I think you get the point. Claiming that the 14th Amendment doesn't cover the presidency completely ignores the plain text of the entire fucking constitution!
Another fun side effect is that the president not being an office covered under the 14th amendment would also mean they're exempt from the Emoluments clause, though that one might already be dead.......