Admin on the slrpnk.net Lemmy instance.

He/Him or what ever you feel like.

XMPP: [email protected]

Lemmy alt: @[email protected]

Avatar is an image of a baby octopus.

  • 12 posts
  • 11 comments
Joined 4 years ago
Cake day: September 19th, 2022
  • Right AC. Was a typo, corrected now.

    As for running nominally 12V stuff directly of a battery… you got lucky with your router then. I had the same idea with various mini PCs and ARM SBCs, and the majority absolutely should not be run directly off a battery where the voltage fluctuates so much. And it gets even worse when you try to solar charge the batteries.

  • When charging, 12V lead acid batteries have significant higher voltages (>14V), so you basically need a DC to DC converter to make sure you get a stable 12V supply. Some (typically industrial/automotive grade) systems have that built into their internal power supply and can work directly off a 12V battery, but with consumer routers I would assume that not to be the case.

  • While there is DC AC power the battery in a UPS isn’t used. It’s not a constant AC-DC-AC conversion, that conversion only happens when there is a power outage.

    The problem is that lead-acid batteries are a really shitty technology with high self discharge rates and short overall life span (their only advantage is high burst capacity that’s good for starting motors).

    I would look for 12V LiFePO4 batteries in a standard lead-acid form factor that are meant as drop in replacements. Those are somewhat more expensive (like 2-3x the price) but will likely last a quarter century or more.

    I am currently using an interim solution where my solar inverter has an seperate emergeny power outlet that works even when power is cut. Sadly it doesn’t switch to battery fast enough (like half a second delay 😓) for it to work as a UPS directly. But in combination with some old regular UPS that have spend batteries that only last a few minutes it works ok. But yeah, not the most efficient option conversion wise, but solar power is free 🤷

As you likely know we are running several alternative web front ends for Lemmy. Currently they are:

Of these Alexandrite and Mlmym have not been updated and maintained for more than one year now and the original authors have likely lost interest. I also assume that once we upgrade to Lemmy 1.0 they will stop working properly.

In addition I think only Photon and maybe Voyager have added support for the Piefed API, should we switch to that in the future (but it seems like Lemmy 1.0 might solve our main technical concerns with it, and the memory consumption recently got quite a bit better).

So all in all, we will probably sunset Mlmym and Alexandrite soon.

There is also a new frontend called Blorp that we could set up. It seems quite nice, but also very similar to Photon. But let me know if you are interested in using this frontend.

Edit: I was made aware of an somewhat maintained fork of Mlmym that we are now using, so that one can stay a bit longer then.

Edit2: We switched to an even better maintained mlmym fork that even plans to support the Lemmy 1.0 api v4, so I think that one should be good to keep for a while.

We are finally moving to a better container format for our Movim instance later this week. This will hopefully fix those persistent image preview issues we started having ever since switching to the old container format that lacks an image proxy.

The instance will be probably down for an hour or so as we need to reorganize a few things with the storage and overall setup.

Your access to the XMPP server with other apps should be unaffected.

Oh and in case you didn’t notice yet, Movim recently added Discord like voice channels that you should definitely give a try 👍

After a long hiatus of security fixes only the development of Etherpad has recently taken up speed again. But it seems to be nearly fully vibe coded with the help of Anthropic Claude and the amount of new features added makes it very unlikely that there is sufficient human code review.

I bring this up because as you probably know we host an instance of it over at https://pads.slrpnk.net/

Aside from the general issues with AI assisted code development and corporate capture through closed AI models like Claude, I consider it also a security risk as the NodeJS ecosystem (Etherpad is using that) is especially vulnerable to supply-chain attacks and AI halluciations make this issue significantly worse.

So basically this means we will probably have to shut down this service soon (stopping to update it is not a good option due to the many security issues found in NodeJS packages all the time), and look for an alternative.

If you have any important collaborative documents on our Etherpad instance, it would be good to export them in the near future. Best would be probably to export it as Markdown, as most alternatives seem to use that syntax.

As for alternatives, suggestions are welcome, but I did look into other options before (Hedgedoc, Cryptpad etc.) and was not so convinced by them either.