lolcatnip

joined 1 year ago
[–] lolcatnip@reddthat.com 0 points 8 months ago (7 children)

Nonvoters don't get to have opinions.

[–] lolcatnip@reddthat.com 5 points 8 months ago (4 children)

I played Diablo 3. It was extremely boring.

[–] lolcatnip@reddthat.com 6 points 8 months ago

White supremacists trend to be white for some reason.

[–] lolcatnip@reddthat.com 4 points 8 months ago

Good thing we have Rust.

[–] lolcatnip@reddthat.com 5 points 8 months ago

Sorry but we can't avoid dealing with the DEA.

[–] lolcatnip@reddthat.com 0 points 8 months ago

The dude looks like Michael Jackson to me.

[–] lolcatnip@reddthat.com 2 points 8 months ago* (last edited 8 months ago) (2 children)

Probably because different messaging platforms have different opinions on how to implement encryption, and those opinions are baked into their infrastructure at a pretty low level. If two platforms don't support a common encryption system, the only way to move traffic between them is to decrypt and re-encrypt the data at the boundary between platforms, giving both platforms access to the unencrypted messages.

Mandating a common system for E2EE seems like a good step 2, but just getting them to exchange messages at all is a good first step that doesn't require anyone to change their backend to support a different encryption mechanism.

(Just to give an example I'm familiar with, you can tell Facebook's encryption isn't E2E because you access Facebook Messenger from a new device and have access to all your old chat history. Making Messenger support E2EE would break a basic assumption about how it works and what features it offers.)

[–] lolcatnip@reddthat.com 6 points 8 months ago (1 children)

Nah, fuck RCS. There is no reason for a mobile carrier to be involved in anything besides voice calls and TCP/IP traffic. Any protocol that requires participation from carriers beyond delivering TCP/IP packets is broken by design. It's like designing a water faucet that somehow can't work without active cooperation from your local water company.

[–] lolcatnip@reddthat.com 6 points 8 months ago

They all have the capability to support a UI where you type a message, hit send, and the message is delivered. This proves it's possible to make and support an interface that hides all the backend complexity. If they don't expose the same functionality through an API, it's because they don't want to, not because it's too hard.

I'm sure there will be some features that aren't fully supported across messaging platforms, but for basic use cases like sending a text or an image, there's really no excuse.

[–] lolcatnip@reddthat.com 13 points 8 months ago

I just noticed my ankle hurts. Why? No idea. How long has it been that way? Also no idea. I hope it goes away on its own.

[–] lolcatnip@reddthat.com 27 points 8 months ago* (last edited 8 months ago) (1 children)

The issue isn't Google using AI to process the data. The issue is that the internet is filling up with AI-generated crap.

[–] lolcatnip@reddthat.com 9 points 8 months ago* (last edited 8 months ago)

I always saw "my computer" as infantilising. If something is going to be labeled as "my" thing, it should be because I applied the label.

view more: ‹ prev next ›