It’s not the CCTV you want to worry about. The CCTV is overwritten regularly and typically goes nowhere.

yes, it is the CCTV. Because there is no way to verify by yourself that the recordings don’t get transmitted or processed for their contents all the time.

Carrying a smartphone and worrying about CCTV while you post pictures of yourself where LLMs can scrape them is utterly irrational.

that’s a huge assumption. that kind of people don’t usually complain about CCTVs.

username checks out

so it must be a problem with your connector maybe

or with their programming language

But seems like you cannot do it with your own Facebook account.

what causes the limitation? the posts are readable to all registered users

wasn’t there a DB conversion document?

if you are downloading the tools in every pipeline run, you are doing it wrong, wasting resources and time. tools should be baked into a new docker image that you use in the pipeline. another pipeline updates the image on schedule

woodpecker was an older system, it supports github actions workflows too

the debian cve tracker also links to that page, but they have written 7.0-rc7 besides it.

https://security-tracker.debian.org/tracker/CVE-2026-31431

the openwall link has some comments that talk about the delayed patches, Greg KH also commented.

and the patch to the kernel was commited on 1th of April.

are you sure? what I have seen in git patch dates is 11th for the unreleased 7.0, and yesterday for the LTS versions

tbh they could have boasted even less bytes by just having everything in a zlib.decompress()

I regularly see a surprising amount of lemmy neighbours by their names, but not by their profile pictures, as voyager does not support showing them

I think they mentioned issues and pull requests

last year when Serinus changed the moderation policy that the “narrative” that trans people are not real or are mentally ill or whatever to not be considered hate speech and thus not to be removed automatically, following the similar change at Facebook.

wow, that’s wild. they do have quite a few highly questionable decisions, to put it gently. maybe we should treat them like we do .ml, and encourage people to move to other instances, while generally not participating in their communities

this defense edit does not make sense. no, volunteer foss engineers don’t need to stay clear of popular projects. if the allegations in the replies are true, I’m genuinely sorry for that, but that’s not a risk of being a foss developer, that is a risk of discussing on the internet.

if people are harassing you, you should report them to the admins.

this shit stirrer ex-googler really does not understand the signals people are giving… apparently the community response is “hilarious”, the moderators removing their toots at both instances are “overzealous” for acting upon multiple reports and giving a proper hilarious removal reason.

“everyone is dumb but me!” lol… (not a quote)

this person is really butthurt that people are telling them they have acted very irresponsibly.

really this is the better version??

for that matter they can to an extent. they could be probing ports on localhost and your network. only HTTP protocol though, but through timings they could probably differentiate between open, closed and filtered ports

the browser in voyager is probably your default browser over customtabs

and because of at the very least leaking, even verifying identity is not sufficient to verify humanity

It seems you don’t understand the idea, which wouldn’t be that people would be forced to disclose their identity on social media. Instead, social media would be required to check that users are who they say they are.

that makes no sense whatsoever. you are saying your name is “Hapankaali”. do you have any documents proving that you are actually “Hapankaali”? if you don’t, how are you planning to prove you are who you claim to be?

no, into the front. Otherwise it would still be usable while charging