640B ought to be enough for anybody

MICROS~1

It is risky to carry encrypted devices across the border which you are not prepared to give them the passwords to.

In most cases they won’t ask you to decrypt anything, but they do sometimes randomly and when they do if you refuse then you can/will be denied entry and/or they’ll keep the device(s) indefinitely.

One approach to avoid this problem is to create an encrypted disk image (your operating system hopefully comes with a program to do this, you shouldn’t need to install anything) and then store it online somewhere and then download it after you’ve crossed the border. Read about how to pick a strong yet memorable passphrase.

It was reported last year that the US was going to start requiring that you disclose all of your social media accounts used in the previous five years, but that did not actually go into effect in December as it had been announced that it would. Something along those lines could still happen later this year though: Here and here are articles from March and May of this year about it.

red alert klaxons, or something else from a star trek sound bank like this

AUR is bad, actually

i would be surprised if it is true that “If you don’t remove that it shows your personal account to anyone who receives it so that they can chat directly with you”, and a search just now didn’t find anything to substantiate that.

It’s a very recent change

is it though? if so, how do you actually find out the profile name from the si parameter?

obviously tracking parameters from URLs should be removed in any case, but afaict only google can use this to find which user generated the link.

after some more reading i found conflicting reports but i think this might actually be happening; apparently it is only visible in the app?

But why rewrite programs that existed for decades and have proven their stability and safety? Rewriting them to Rust won’t make them safer, it will just introduce the kind of issues original versions have got fixed long ago.

Of course rewriting them will introduce some new issues, but it will also eliminate classes of bugs from which there are definitely still a great many in old “stable” C code (bugs which are now being discovered and will presumably continue to be discovered at a much faster pace due to LLMs).

The whole project is about abolishing GPL. And Rust is just an excuse.

I don’t think it is just an excuse; I believe that improving security is also a goal… but removing GPL code is clearly also part of their motivation :(

No, it is not a good time. A project like Ubuntu should now be in freeze as they had about 3 months before release

This bug was reported (and resolved by rolling back to the GNU coreutils version of cp) on June 30, a little over 15 weeks prior to the scheduled release date.

Which distros have a feature freeze that far in advance?

Ubuntu hasn’t even scheduled theirs for this release yet; if you edit that url to look at previous releases’ schedules you can see their feature freeze and debian import freezes are typically about 2 months prior to release. (See here for descriptions of all of the different types of freezes…)

What an absolute shitshow

I’d say the month of June is actually a good time to be breaking and fixing things in a release that is due to come out in (checks notes) October.

Beyond that, I recommend that you post on !nostupidquestions@lemmy.world or somewhere similar if you need people to explain why telegram is offtopic in communities about privacy technology. (This discussion is very offtopic in this thread so I won’t reply further here. If you really feel the need to argue about the above I recommend you do it in a new thread somewhere it isn’t offtopic; if you tag me maybe i’ll reply there.)

And I never got the actual reason

imo the reason is pretty clear in the modlog you’re linking to. the ban duration was disproportionate though, so, i just unbanned you. (please do not advocate for the use of telegram in !privacy@lemmy.ml though! lmao)

This led to a few larger instances blocking it (.world I think is the kargst to have done so) blocking it, so their users cannot access *.ml communities.

Huh? Lemmy.world has not blocked lemmy.ml, nor have (correct me if i’m wrong?) any other large instances.

Here is this very comment from me (on lemmy.ml) viewable on lemmy.world, btw.

The existing chess community on lemmy.ml/c/chess seems to be dead

it looks like !chess@lemmy.ml is averaging a few posts per month this year and has 2.4k subscribers; not very active but i wouldn’t call it dead.

moderators are not reachable

the mods do seem inactive; i and other lemmy.ml admins remove spam if/when it gets reported (which has happened four times this year). if someone (with some posting history) wants to be added as a mod of it just let me know and i’ll add you.

and is hosted on .ml which is defederated by many instances

huh? which instances have defederated lemmy.ml?

which music genres do you like?

Did you not read the post? OP clearly says:

I ran the numbers and I like every single music genre pretty much equally

😂

As others have said it is a huge amount of work to maintain a fork of such a complicated piece of software.

Especially around security: web browsers constantly process potentially-malicious data, which gives them a large attack surface. Every browser regularly has new vulnerabilities discovered which must be fixed. Hard forking a browser means that, even ignoring any bugs in the new code the fork has added, every time a bug is discovered and fixed in the code they forked from someone needs to analyze the upstream’s fix and port it to the fork. The more they diverge, the more work this is. Failing to do this work lets any malicious website exploit the bugs and install malware on users’ computers.