[-] [email protected] -2 points 9 hours ago

anonymized

why is this a concern again?

[-] [email protected] 2 points 9 hours ago

"checking" does not prevent anything bad from happening. and if that file were read by a malicious actor, it would likely be immediate and you'd never even notice.

[-] [email protected] 4 points 14 hours ago

I assume this is directly due to the recent repeal of Chevron.

[-] [email protected] 5 points 14 hours ago

Correlation is not causation.

[-] [email protected] 4 points 14 hours ago
[-] [email protected] 4 points 18 hours ago

That depends on your threat model. What are you worried about?

[-] [email protected] 4 points 18 hours ago

I would’ve thought most desktop users just leave it running all day long like I do.

They do. OP is not a normal user.

[-] [email protected] 5 points 18 hours ago* (last edited 18 hours ago)

It’s really not a big deal

For most casual users, it is a deal-breaker. And it's hard to get everyday people to use your software with roadblocks like that.

every time I open my email client.

You must not get email very often, this is absolutely a non-starter for me.

[-] [email protected] 4 points 18 hours ago

Thanks ChatGPT.

[-] [email protected] 6 points 18 hours ago* (last edited 18 hours ago)

How do you know?

[-] [email protected] 5 points 18 hours ago* (last edited 18 hours ago)

For gamers, it’s likely a 1-5 FPS loss

I highly doubt it... would love to see some hard data on that. Most algorithms used for disk encryption these days are already faster than RAM, and most games are not reading gigabytes/sec from the disk every frame during gameplay for this to ever matter.

[-] [email protected] 12 points 18 hours ago* (last edited 18 hours ago)

How in the fuck are people actually defending signal for this

Probably because Android (at least) already uses file-based encryption, and the files stored by apps are not readable by other apps anyways.

And if people had to type in a password every time they started the app, they just wouldn't use it.

-8
submitted 1 week ago by [email protected] to c/[email protected]
6
403 on API endpoints (lemmy.readme.io)
submitted 1 month ago by [email protected] to c/[email protected]

Tried to use several different API endpoints as described in the link, but they all return 403 with a cloudflare "Just a moment..." html reply. Even tried copying an existing jwt token from a working logged-in browser but the same thing still happens.

Any idea what I could be doing wrong?

curl -v --request POST \
     --url https://programming.dev/api/v3/user/login \
     --header 'accept: application/json' \
     --header 'content-type: application/json' \
     --data '{"username_or_email": "redacted", "password": "redacted"}'
...
< HTTP/2 403
...
<!DOCTYPE html><html lang="en-US"><head><title>Just a moment...</title>
...
22
submitted 2 months ago* (last edited 2 months ago) by [email protected] to c/[email protected]

I am noticing that some comments, which are coming from users on other verified (via /instances) federated instances, do not show up on a post. For example: https://programming.dev/post/13648105

Does not show this comment on it: https://lemmy.ml/comment/10803786

Any ideas why? I checked the modlog and the comment wasn't removed, and their post history to me does not look like someone that is likely to be banned from the instance, so I'm not sure what else it could be.

10
submitted 2 months ago by [email protected] to c/[email protected]

My lemmy account is on the programming.dev instance but I use newsboat for RSS reading of some lemmy.ml communities, along with browsing the local homepage of lemmy.ml and some other instances in a regular browser. Is there a way to do either of these things from the programming.dev instance so that I can easily comment on posts without having to manually locate the same post by browsing to /c/[email protected] on my own instance?

view more: next ›

refalo

joined 2 months ago