Ananace

There are no screens in the lenses, but you can interact with the AI system via voice or by activating the integrated camera.

So the reason to make them glasses is…?

If I’m going to put a pair of smartglasses on, they better be doing all manner of cool XR Iron Man stuff for me, not be just a set of privacy invading cameras and an open mic fitted into a pair of frames.

The fact that simply opening the store gives you a faceful of AI slop (12 out of 15 apps on the front page), and the editor picks are almost exclusively slop or partially slopped (one application without explicit AI code in it), it does paint a pretty clear picture of them allowing more of it compared to flathub.

So; flathub, but with less polished packaging, and more AI slop.

So, this is basically like flathub except filled with more AI slop?

Been using Yggdrasil for quite a while at this point, both for encrypted service communication and also as unbreakable VPN links to various places where I don’t want to have to mess about with NAT traversal.

It’s been nice to be able to just drop it onto my router, add an ALFIS DNS entry, and have all my devices just work with Yggdrasil with no additional configuration.

I’m holding off on Fluxer until they decide how they’re going to implement federation, since the designs they’ve communicated publicly so far have all seemed like they prioritize siloing and putting excessive load on self-hosted nodes.
Their first proposed solution would’ve required each self-hosted server to be able to handle every user on every other server in the network - a proposal which they’ve since scrubbed from their page.
The latest proposal I can find at least speaks about aggregating connections through the users server, so it’s not as insane (Only requiring each self-hosted server to be able to handle requests from every other server on the network). But it still forbids intelligent caching, and instead seems to consider recommending the use of cloudflare to reduce the load from their design to be a good solution.

I made an NFC/QR code card for my wifi details at home, and that also includes the details written in clear text on the card, since some devices simply don’t do QR (or NFC in my case).

It doesn’t really solve my use-case, since we do a combination of direct stream when possible, as well as local sync/cache but only for transcoding purposes. As well as local users only, with the federated sharing taking care of permissions, so that we don’t transfer user information between eachother.

Jellyswarrm is certainly a lot closer than other solutions people have suggested though.

The lack of library sharing is what’s keeping me on Plex.

The ability to watch media across servers, and even transparently pull it for local transcode when necessary is just an amazing feature.

I absolutely love that zip-tie mounting solution, it’s the kind of thing I wish I saw in more homelab setups.

I really do hope that Funkwhale get their 2.0 release out soon, should make self-hosted Spotify-like stacks simpler to do, and the fact that it works for creation and distribution as well is great.

Interesting, that’s definitely not what I’m seeing from regular use. Are you running any added applications? LDAP? SSO? External mounts?

Are you looking at data rates or IO operations? Because this is almost exclusively stat queries, i.e. inode queries.

Oh yeah, CPU usage is basically zero, and memory usage of the PHP code itself is also basically nil. It’s just the sudden storms of IO requests that causes issues, and since those come over a network pipe it causes issues for other pieces of software as well.

Again, it works until it requires reloading, i.e. the next update of any component or the next restart of the server.

I’m also running an inode cache on the client side, on top of the persistent opcache, but due to the sheer number of files that Nextcloud consists of it still generates a frankly ridiculous amount of calls when it needs to invalidate the cache. If you’re running on local drives then that’s likely much less of an issue, regardless of what kind of drive it is, but this is hosted on machines that do not have any local storage.

Yep, those values are actually somewhat tame compared to my own cache tuning, the issue remains that the code requires reloading PHP files from disk during runtime in order to support applications and updates, which - even if it doesn’t happen often - causes IO storms that temporarily break both Nextcloud as well as other software.

Currently working to move away from Nextcloud myself, it’s PHP nature causes IO storms when it tries to check if it needs to reload any code for incoming requests.

All OpenWRT-based routers have the option of built-in DNS-based adblock, can thoroughly recommend the Turris routers for such things.

It’s worth noting that the ESS suite Chart is absolutely not built to be community-viable, it’s built for the kind of single-purpose deployments that Element offer hosting for, and it also breaks almost all Kubernetes best practices. Which is actually not wrong per-se. Element need to be able to maintain it after all, and since they don’t have the Kubernetes know-how to build generic components, it makes sense to instead bundle a fully integrated solution which they are comfortable with developing and debugging.

They’re definitely slowly but steadily rewriting Synapse in Rust as well, that’s been an open and ongoing project for a while now. You can see that just by looking in the Rust folder in the Synapse sources.
I strongly doubt that they have the “rest” of the application rewritten internally and keeping it hostage for paid hosting though, it’d cost them too much to keep separate codebases for such a thing.

The “Synapse Pro” offering is most likely just the regular Python+Rust Synapse, but with a few additional HA components and some workers written in Rust for efficiency, just like how there’s community workers written in both C# and Go for performance reasons.

If you don’t have a hard requirement for the Helm Chart to be written by Element themselves, I’ve been maintaining some Charts for Matrix components for almost six years - which have also ended up being used as the base for the German BundesMessenger project. Unfortunately free time hasn’t allowed me to do nearly as much as I want with it, especially since it continues to work for the use-cases for my job.

We do have a room on Matrix for dealing with Kubernetes setups though.

I also ended up chatting with one of the core devs of Synapse about ways to improve regular Python Synapse for use with Kubernetes back in the ending of January, so hopefully it’ll improve in that direction when time allows. They have the exact same problems with providing hosted setups after all, so they too want to make the open-source version easier to run.