Thanks!

The mention was at about 12:06, in the form that OLM breaks down at about 50 users “give or take”, so it’s not really a limitation imposed by the system itself and it would be difficult to impose it. I doubt this is the experience of all Matrix e2ee users at least at that exact point, but e2ee has always had some growth pains, so there could people with those issues; on the other hand few large rooms are e2ee to begin with, so experience on those is limited. E2ee also requires the users to be more mindful about their data as in not to lose their private keys, and these problems probably increase linearly as the room size increases.

I didn’t notice any claim of rooms larger than 50 becoming public.

I’ve only heard a second-hand info about it, but apparently one local policital party uses e2ee in Matrix with hundreds of people in the room, so that should be a proof that the encryption is not limited to 50 users—and this info sounds just as well founded as the information provided by the video ;).

The guy carries on stating that pretty much all of the huge matrix rooms are not end-to-end-encrypted, and I have no reason to doubt that. Personally I see little point in having such large rooms encrypted anyway, because if you have a large room you will also likely have very relaxed checks on who gets to enter it (e.g. it could be completely public), and if that’s the case, then so can any party who wishes to monitor the room join the room as well. E2ee won’t be protecting those cases. (While at the same time you lose server-side search feature and efficient notifications, though at least the latter one is being fixed with out-of-envelope notification data—which again leaks a bit more metadata…)

The video also makes it sound like that if you have a Matrix Home Server in the network, it’s going to end up hosting CSAM. This is only the case if one of the users of that HS are in a room that has the content, so it’s not like it will just automatically get migrated there. I imagine vast majority of Matrix Home Servers have limited account creation abilities (e.g. companies, personal home servers, organizations, etc), eliminating or at least highly discouraging this kind of issue.

Btw, the video makes an excellent point about the Matrix CDN issue, which is being fixed currently as well (that change is already merged to the matrix spec), by requiring authentication. Next steps is going to associate media to messages, making this kind of thing even more strict. All this means IRC bridges will need to start hosting Matrix-side contents by themselves, though…

Because encryption doesn’t work for rooms over 50 people, so any room over that size is public by default.

By public you mean non-encrypted? How does that work? When you create a room, you default to encryption, and there is only one participant (the room creator). And you cannot turn off encryption, so what then happens when you get 51 participants?

Also existing non-encrypted rooms are never automatically switched to encryption, so the switch must be explicit. Does it refuse to do it if there are more than 50 participants?

I’ve never heard of this limit nor was I able to find info about it (so a link would be great), but there could some factor that increases problems as the number of people increases… Perhaps 50 is some practical suggestion for the maximum number of people to have in encrypted sessions?

If you want to have multi-host redundant storage at home (via e.g. minio or ceph), S3 is a pretty good protocol to provide it.

S3 is nice in the way it’s not a file system so it can have relaxed semantics, while also providing secure access to individual files over HTTPS via URL signing.

Some people seem to be stuck in the idea that S3 means cloud hosting. Not sure if that was your view, but it’s worth spelling out sometimes.

Moving away from Discord can mean you need to stop interacting with the community using it. My personal examples are: Tilt5, Makera, Turbo Sliders. In the these cases Discord is also the way to access support for something you’ve paid for.

Getting thise communities to move into something open (e.g. Matrix) can be a tall order.

Papermerge version 2.0, version 2.1 and version 3.0 are entirely different and incompatible applications.

That doesn’t exactly inspire confidence in the future versions of this application, given in particular the use case of long-term document archival :).

I just noticed https://lemmy.ml/u/giloronfoo@beehaw.org had proposed the same, but here’s the same but with more words ;).

I would propose you try to split the data you have manually into logically separate parts, so that you could logically fit 0.8 TB on one drive, 0.4 TB on another, and maybe sets of 0.2TB+0.2TB on a third one. Then you’d have a script that uses traditional backup approaches with modern backup apps to back up the particular data set for the disk you have attached to the system. This approach will allow you to access painlessly modern “infinite increments” backups where you persist older versions of data without doing full and incremental backups separately. You should then write a script to ensure no important data is forgotten to be backed up and that there are no overlapping backups (except for data you want to back up twice?).

For example, you could have a physical drive with sticker “photos and music” on it to back up your ~/Photos and ~/Music.

At some point some of those splits might become too large to fit into its allocated storage, which would be additional manual maintenance. Apply foresight to avoid these situations :).

If that kind of separation is not possible, then I guess tar+multi volume splitting is one option, as suggested elsewhere.

By that logic, is the compositor working any different than a trojan? Is there really a difference?

The Wayland compositor is always capturing all your keyboard and mouse as well. No permissions asked. Pretty sus.

I have 64GB RAM and my 64GB swap still gets filled to 60% over time.

It just happens so that apps end up touching some memory once that they never then use again. Better use some SSD for that instead of RAM.

I suppose it explains why people have a bad attitude about Wayland when tools providing useful functionality are described as trojans.

X11 can (…mostly…) have great security by just providing a suitable X Security module to it. It just seems it wasn’t considered that big of an issue that anyone bothered. Nokia Maemo/Meego used to rock such a module.

It doesn’t actually detect moved code, though, like git diff can? I gave it a shot and also there’s a couple issues open about it, e.g. https://github.com/Wilfred/difftastic/issues/520 .

Other than that, difftastic is quite nice.

Welcome video game streaming?

Speed records aren’t usually representative of regular use top speeds, are they?

And how about the actual speeds they are used with? Another poster suggested the maintenance costs of traditional speeds skyrocket as speed increases, while maglev doesn’t really have a lot of stuff that wears down in the first place.

Thanks! Found one article from Tuesday about it: https://domainincite.com/28897-freenom-is-losing-another-cctld-after-collecting-military-emails

Is there information about this situation with Mali government about ml domains? I cannot find anything about it.

Though apparently some ml domain receives a lot of accidental US military emails :).

Just keeping a single frame buffer image can take tens of megabytes nowadays, so 100MB isn’t all that much. Also 64-bit can easily double the memory consumption, given how pointer-happy the ELISP data structures can be (this is somewhat based on my assumptions, I don’t actually know the memory layouts of the different Emacs data structures ;)).

But I don’t truly know, though. If I start a terminal-only Emacs without any additional lisp code it takes “only” 59232 kilobytes of resident memory. Still more than I’d expect. I’d expect something like 2 MB. But I’ll survive.

It comes from the words “Eight Megs And Constantly Swapping”.

Yeah, the name hasn’t aged well…

One other thing is that you can bulk create your own instances, and that’s a lot more effort to defederate. People could be creating those instances right now and just start using them after a year; at least they have incurred some costs during that…

I believe abuse management in openly federated systems (e.g. Lemmy, Mastodon, Matrix) is still an unsolved problem. I doubt good solutions will arrive before they become popular enough to attract commercial spammers.

There is the DJVU format for this exact use case, but you’d need to convert them to, say, pdf for many use case. Its also a bit old and perhaps not maintained, soo…

HEIF and other modern video encoders (HEIF=H265) should fare a lot better than JPEG, though.

No always-on display and waterproof rating only to 1m instead of 30m, though 😞.

Nevertheless, quite interesting. Maybe at some point new more capable hardware will arrive.