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?

Am I to understand correctly that if you are running Gtk+ apps in the Gnome compositor, you get this working, but if you are running non-Gnome compositor with Gtk+ apps, it will not work? Or is it independent of the compositor?

You should have backups. Preferably also snapshots. Then rm will feel less scary.

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.

That was a Firefox bug, based on one comment in the Bitwarden isue tracker . It should be fixed now in Firefox 116.

Boox Tab Ultra

Looks pretty nice device! Even the camera makes a bit sense in the demo they give (though apparently in practice the scanning rarely works). And cheaper to boot as well. I might consider getting this one.

But is the display really better quality? Atleast the DPI is slightly higher at 219 on the Boox Tab Ultra vs 190 on the Daylight. And Boox weighs 70 grams less, and that's the device some reviews call heavy (and some lightweight..).

These reviews mention the slow display speed:

• https://www.xda-developers.com/boox-tab-ultra-review/
• https://www.techradar.com/reviews/onyx-boox-tab-ultra-review-an-e-ink-peg-in-an-ipad-hole even goes to describe it "distracting" and "Performance can’t keep up with fast typing"
• https://www.trustedreviews.com/reviews/onyx-boox-tab-ultra "Tab Ultra does let you choose between several refresh modes" and https://www.makeuseof.com/onyx-boox-tab-ultra-review/ "The HD preset works fine for casual reading, whereas the balanced mode works better when thumbing through documents or typing. Meanwhile, the fast mode is suggested for general website browsing, and ultrafast is more useful for video playback. "—surely if the display was always fast and working, this fidgeting would be pointless?

So perhaps there is some room for improvement? That being said, some other reviews don't mention it and one says it's faster than typical e-ink display, though that doesn't sound immediately purely praising.

---

In the end it probably comes to the software: how fast it is, it well it works, how nice it is to use. It seems both have customized the standard Android, so I suppose the difference is in which one has done it better and which one has better custom apps. Per the reviews Boox doesn't fare too well in this aspect. Maybe someone will make a comparative review of the devices.

As opposed to buing a separate display for the computer?

I like to think this thing would be nice reading the news while having a breakfast or reading an e-book outside or at the bed, not near my computer. So it makes a lot of sense to build a tablet with this display technology.

Zooming and panning a pdf is arguably more comfortable with higher frame rate.

What a nice succinct explanation!

But also completely useless. Run0 ignores the suid bit for the same reason as 99% of command line apps do: it ignores because it isn't relevant to its functionality.

Would that kind of provision allow me to have my code removed from a git repository history, if that git repository is hosted by a company?

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 think the second point is the biggest for me: it's almost like Canonical wanted to have a single dominant store for apps, as the ecosystem they are building supports only one. And, apparently, that one server is also closed?

So if you try to make an alternative source and give instructions to people how to configure their snap installation to use it (I found this information very hard to find for some reason..), your "store" probably won't have the same packages Canonical's has, so users won't be able to find the packages and I imagine updates are also now broken?

Contrasting this with flatpak: you just install apps from wherever. Or from flathub. Or your own site. Doesn't matter. No business incentive behind—built into the tools—to make everyone use flathub.org.

Does finding the guilty party solve the issue?

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.

The pins are part of the window, so.. You can access old closed windows through the history menu, which I believe works after starting a new session after quitting it.

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.