Lucifer dared to question his father and was cast out for eternity and demonized for not blindly obeying. Not surprising he’d be a bit salty about that.

IIRC in the Bible Lucifer only kills one person, versus the millions God kills at a whim, usually for disobeying some bullshit he came up with that he never told anyone about.

Satan really just runs the place for God’s undesirables. Why would you want to worship the largest mass murderer in history in the first place though?

Assuming the stories and parables are true, or even based on any sort of reality, which of course they aren’t.

Or they could just use their existing scrapers and try to brute force it. Meta isn’t exactly known for being sneaky.

They’d have to host it from somewhere not related to Meta in any way, otherwise someone on the fediverse would find that link and spread the word, and it would be blocked the exact same way. It only takes one person making that connection, Meta knows they’re hated.

Instances will not have copies of content for instances they block. So while Meta has Threads… most of the fediverse has blocked it. Since they can’t get that data fia federation, they scrape. And the instances they scrape will also only have content from their unblocked instances. To ensure they get everything, they have to scrape everything regardless of federation.

The point they’re making is that they don’t need to scrape the data. It is available via federation. Scraping the data is less efficient and can negatively affect the platform performance, versus the built in federation system where that data sync is intentional.

Especially when Meta has a fediverse presence. The reason they’re scraping is likely because instances have blocked theirs, in part to prevent this exact thing.

Eh Diamond is okay, as long as it’s artifical. Better clarity and color, not contributing to the blood diamond trade, and a fraction of the price.

That being said, there are a ton of other prettier gems anyway, diamonds are boring as fuck.

So can the US military. We’re talking about reality though, not what’s technically legal.

They’re going to make the soldiers’ life a living hell for not following orders all the way through the inevitable court martial trial.

There are plenty of step-by-step guides to run Deepseek locally. Hell, someone even had it running on a Raspberry Pi. It seems to be much more efficient than other current alternatives.

That’s about as openly available to self host as you can get without a 1-button installer.

Your point OpenAI? Weren’t you part of the group saying training AI wasn’t copyright infringement? Not so happy when it’s your shit being copied? Huh. Weird.

First rule, always have backups. Especially with an older drive, make sure anything you might need is duplicated somewhere else. Ideally off-site to prevent loss in case of things like burglary or a fire. Even something as simple as Google Drive or OneDrive.

Personally, I’d take a look at replacing it with an SSD if you can afford to, not only because of the age, but better performance. You may not notice slowness, but making the jump from a HDD to an SSD is still at least a little noticeable even on secondary drives from my experience.

See you say no apocalyptic event, but we’ve done almost nothing to slow climate change, and that will destroy humanity in less than a century much better than we can directly do ourselves. The event has already started, and we’re ignoring it.

This is essentially what I did when I was laid off August last year. And it did take about that long to really be free of all the stress I’d racked up over the years in retail and other public customer-facing roles.

Eh, no one else is doing anything to provide support apart from Google either. Anyone else could do their own thing, no one is prevented from their own support. But very few companies and carriers even began to develop support for RCS, even after the Universal Profile. That is why Google developed their own support and built that support into the native app.

Verizon had their own RCS support via a proprietary carrier-specific app that never worked with anyone outside Verizon as far as I remember, and they dropped it in favor of Google’s option as soon as that was available. Samsung had their own RCS support in their proprietary Messaging app, also dropped because Google provides the same support on all of their products and Samsung doesn’t have to do anything or support it in any way. Google now provides an option for all Android devices specifically because almost no one was adding support on their own.

Anyone can, no one else will, because they have no reason to. The average user doesn’t care whether it’s Google, their carrier, or the manufacturer providing support for sending high quality photos to their friend’s phone number as long as it works.

Samsung had support before Google and Jibe… but they have abandoned their own RCS support. Simply because Google’s works on all of their devices and they don’t need to do any development to support it going forwards. Why pay for development and support for a system you don’t have to and get nothing from? No one is buying a Samsung phone for the Samsung Messages RCS capability.

This isn’t done out of altruism.

I never said or even got close to claiming that it was.

But there is a distinct difference between Google taking a fragmented RCS implementation across carriers and manufacturers on Android devices, and providing a single universally supported option for Android (the operating system that they control, but don’t prevent others from modifying heavily)… and Apple actively trying to avoid RCS support entirely in favor of their own proprietary system that does not support any products they don’t make and sell directly. Verizon had their own RCS app on Android, and Samsung added RCS support to their Messaging app on their devices, among others prior to the Universal Profile and Google adding support directly in Android Messages. That’s not something anyone can do or offer for iPhones other than Apple

Google worked to add support for essentially all Android customers. Apple decided none of their customers should be able to use RCS, whether they want to or not, simply because they had their own thing that only their customers could use and won’t let anyone else use. You can’t possibly be trying to claim that Apple is in any way a good guy here. Comparing the two directly here, Apple is clearly worse with no good reasoning for it, it is entirely for selfish reasons.

And absolutely zero users care about the reasons. They only know that sending messages back and forth is dogshit.

The source of the lack of support across is Apple not wanting to even try because they want everyone to use their proprietary system on their devices instead. Google at least implemented a system to get RCS support to as many devices as they could, even when carriers didn’t do anything to help. Apple instead had to be threatened by regulators before they even began to consider looking at it.

Well I’ve been able to RCS with basically everyone on an android phone since 2019 with almost no issues. That’s 5 years now.

I don’t really care how Apple wants to try and justify it. The answer is they don’t want to add support for an alternative to their walled garden proprietary system that no one else can use. They want to force everyone onto an iPhone and iMessage if possible. The only reason they’re even looking at RCS support now is because of regulators starting to look at their glaring lack of support for interoperability.

That wouldn’t be an issue today if Apple had started supporting RCS, the replacement for the old SMS/MMS system years ago like every Android phone. Instead of trying to strangle it by acting like iMessage on iOS was the only solution.

For a differing and quite simple opinion, as a lurker, it’s extremely annoying having a community post a ton of similar posts in a row like that take over my feed. It’s the same effect as spam, regardless of the content. I’m much more likely to just block the community and never interact again.

we can do better with something in unicode.

Uh… It is Unicode.

U+2042 ⁂ ASTERISM