Ananace

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 compared to other software I run. 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.

One has super cow powers, the other one doesn’t.

Personal thoughts - being about 15 hours in; the exploration part is far from exciting, the gunplay is not much improved since Fallout 4, the crafting systems have not really evolved at all, the outpost construction system feels very disconnected from any other gameplay - being a completely optional resource sink more than anything else, the ship construction system is clunky as anything and has a bunch of drawbacks to it, the usability of the UI is mediocre at best - probably slightly worse than the original Skyrim UI, the economy seems completely broken - you’re very obviously meant to have 2-3 digits fewer in your credits than what the game awards you for regular play even without heavy looting, the characters are rather weakly written and seem strangely delayed in reactions to the story, your chosen backstory never has an actual role in gameplay - only been able to skip two 1k credit payments and a “put the cube in the cube hole” puzzle with it so far, etc.
It’s very much a Bethesda game. I’m definitely going to finish the main story - and probably poke into a bunch of the side content as well, but this is definitely not looking like a game I’ll have more than a single playthrough in.

I actually ended up bringing out a USB dancepad I’ve got laying about to play with, since I had to do a bunch of on-planet stuff, and standing and drinking tea while waiting through the traversal for those missions felt much nicer.

ZZT-OOP is fun to work with though, definitely not meant for doing anything more complex than light gameplay, and yet people have done ridiculous things with it.

Though I personally did most of my coding in that vein in MegaZeux with their Robotic language, which is basically ZZT-OOP++.

Doesn’t look like so in the beta at least, it will always launch in an SDL window - and doesn’t link to the curses libs either, which makes some sense with it being a Steam game.
Though using dfhack and the remote interface could probably still be used to have a tty client.

I use KeePassXC on the daily, so that’s definitely going on the list. Spectacle does screenshots amazingly well. neovim is a great fork of vim, handles all my text editing and IDE work. GIMP is basically a given for image editing. And also a fan of LMMS for whenever I work with audio/music.

I see some of these have already been mentioned, but they do deserve repeating;

• µBlock Origin - blocks ads, and does it well.
• Privacy Badger - blocks trackers, rewrites some tracking URLs, etc.
• Multi-Account Containers - for those places where you want to keep tabs separate, giving each container its own cookies/session/etc.
• Consent-O-Matic - automatically handles a lot of pages that shove annoying (and often technically GDPR-illegal due to lacking a quick “reject all” button) consent forms in your face.
• Imagus - shows linked images on hover, including support for galleries and scrolling through all the images contained.

Freelancer’s installer has had some issues with Linux in the past, it actually uses a couple of really odd side effects of Windows API calls as part of its functionality - which has caused issues on actual Windows as well for some people.

If you’re using Lutris, my suggestion is to use the add new game button in the interface - the plus in the top-left, and choose “Install a Windows game from an executable”, then you’ll get a perfectly clean prefix for that part.

And I’m also going to take the opportunity to add a link to Librelancer, an open-source remake of the Freelancer engine which has been going on for a while, not quite yet to the point where it can play the campaign though.

Tyskarna var tydligen mycket tidigare ute med att få igång sin flagga.

I don’t get the “Game Porting Toolkit” they made, content-wise it basically looks like a regular Wine packaging - much like what Proton is, but then it has one of the strangest licenses I’ve ever seen for something designed to help development and shipping.
To paraphrase, you can’t include any part of the toolkit with your product. Not the development components, the runtime components, the translation layers, nothing. So good luck using it to actually ship game ports, since that would be a license violation.

The only widget I’ve found in any way useful as a detached window like that has been the sticky note, and even there the usability is limited compared to just opening kwrite - or any other simple text editor.

It’s definitely an interesting - if quite useless and potentially confusing - feature, but it makes complete sense to drop it from core and instead let it live as an extension instead, since it’s quite literally just a krunner runner anyway.

Basically, you can open some widgets inside a standalone window instead of attaching them to a bar/desktop, making them act like some kind of standalone application instead - including losing all their state as soon as their window is closed.