Ananace @ ace @lemmy.ananace.dev

Just another Swedish programming sysadmin person.

---

Read more

Posts

60

Comments

245

Joined

2 yr. ago

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.

Thank you so much, especially for the private instance improvement.

It's sad when it's revealing that ~80% of all traffic to my home instance is garbage.

Default block for incoming traffic is always a good starting point.
I'm personally using crowdsec to good results, but still need to add some more to it as I keep seeing failed attacks that should be blocked much quicker.

10-20% of year-over-year revenue is the going rate.

Honestly, the two reasons I've been sticking with Plex is the federated/shared libraries and watch together.

If they're starting to axe those then I see no reason to continue using it.

The Librelancer project is working on this.

There are actually a few projects doing exactly that, at least for the early entries;

• FreeSO - Open-source version of The Sims: Online but with a bunch of modern improvements, main server shut down at the end of last year
• Simitone - Single-player interface for FreeSO
• FreeSims - Open-source engine for The Sims
• OpenTS2 - Open-source implementation of The Sims 2 engine in Unity

Development pace for them is somewhat slow due apparent lack of interest - and a healthy dose of fear of EA interference - though.

Calling it a "Lemmy/Mastodon bridge" sounds off, it's like saying "Gmail/Outlook bridge" when discussing the sending of emails between the two.

I'd use the word "interoperability" instead, or maybe "interaction" for something slightly less technical.

I might be slightly biased, but I can also recommend OpenMW for Deck.

Been enjoying Aloft, a pretty cozy exploration/survival game about restoring the environment of various floating islands.

Also started working my way through Disco Elysium.

Eurofighter Typhoon

Eurofighter Typhoon

Apparently posting it caused enough load to take down my pict-rs server, sorry about that.

Ended up oversleeping somewhat, so I did the first part on the way to work using flood fills over a global visited set, and now that work's over I've sat down to expand that solution to do corner counting for part two as well.

Well, there's the ALFIS project

And now we get into the days where caching really is king. My first attempt didn't go so well, I tried to handle the full list result as one cache step, instead of individually caching the result of calculating each stone per step.

I think my original attempt is still calculating at home, but I finished up this much better version on the trip to work.
All hail public transport.

Nice to have a really simple one for a change, both my day 1 and 2 solutions worked on their very first attempts.
I rewrote the code to combine the two though, since the implementations were almost identical for both solutions, and also to replace the recursion with a search list instead.

Was really blanking on how to do this one nicely, so a bunch of stacked loops it is...
Also ended up writing two separate solutions for the first and second part, since I couldn't get acceptable performance otherwise. Still takes half a second on my machine, mainly on the second part.

This is technically the second implementation, the first one took minutes to calculate, so I wasn't really okay with stamping it as my solution-of-choice.

Can definitely still be improved, but I've been poking and prodding at this code for hours on end now, so it's long past time to let it sit for a while and see if I get any better ideas later.

And I of course misread and wasted a bunch of time debugging the second part, entirely missed the fact that antinodes occurred on top of the emanating antennae as well...