I like that, but they forced me to use their solutions, which I didn’t appreciate. The only remote communication software they prepared was a horrible free software project that has been in maintenance mode for 20 years… I was surprised to see it compiled. The connection was horrible because it assumed ~'90s technologies.

I hope they know DMs aren’t secure on Fediverse.

Glad to hear :) What I mean is that Rust vectors and arrays are, for example, very similar to C++ vectors and arrays.

Nice summary. I’m wondering if comparison with C++ may help, because Rusts’ data structure design overlaps with C++ 's STL considerably. Another thing is that Geek for Geeks is not reliable, generally speaking.

If you’re correct, to me the usefulness of Wikipedia is actually different from that of encyclopedia, and the pattern I’m arguing goes against that.

I can respect your comment. The problem with Wikipedia’s scholarly articlesI wanted to raise was that some group of researchers (or businesses) wash away others’ views. In other times, mathematicians try to satisfy everyone from different disciplines, and write a very abstract article that covers everyone’s view yet is too academic and hardly readable to most readers who actually need Wikipedia.

As an academic I love this. On Wikipedia there’s actually fights among different expert disciplines going on. It is better to allow different instances operated by different discipline summarize knowledge from their own perspective.

I think it’s a dead lock. The replies show that they can’t even understand the concern.

That’s a typical death to a project. For, there will never be a moment for the team to address the concern. Whatever you try, the team won’t move an inch.

I don’t know what instance admins are thinking, but there’s no point complaining at this point.

And that’s fine. If one instance has to be able to delete one revenge child porn from all the instances, it has to be what you call a DRM. Also, don’t cache the key because that’s exactly the opposite of what this is meant for.

Lemmy providing an open API does not mean that third parties maintain compatibility forever. (Edit: for example, what happens if the third party app gets taken away by a malicious maintainer? Or becomes buggy, or un-maintainable, project dies, etc.)

I don’t want to upset you, but I think I have to say this for the sake of the community. The attitude like “we provide an API, so third parties will follow,” is what is causing instance admins’ distrust in the first place.

Maybe encryption can help? Instances only copy the encrypted image, and only the original instance provides the encryption key to client apps. This way, the original instance can de-facto delete the image copies by simply refusing to issue the key.

There’s no guarantee on third party tools continuing to work with Lemmy. Something as critical as deleting images, which can cause problems like revenge porn and such, must be given priority by the official project.