An 8 switch relay, old Pi, and 8 hardware store outlets can be had for not much more. I did that and let PiKVM control my outlets directly.

This is the back of my 10" rack before it was cleaned up. Lots of custom work on this that I’ll be posting a page on my site about when complete.

@tal@lemmy.today in case you are interested

I built an 8 outlet version of those with relays and wall outlets for… a lot less.

A matrix bridge would be nice and could open up a large user base.

Ahh definately not my problem after figuring this out (couldn’t find a guide but looked at the source). My instance is private so this isn’t impacting my non-Google results.

Why do these docs look like code? So odd… For my dumb brain trying to absorb this from a phone, is there a doc for what to enable in the Docker container that I’m not seeing?

Oh yea, I’m still going to try it out the next time I need to page watch.

Loaded very quickly for me, just a few seconds. I’m guessing it was overloaded for a bit.

Last year, I was tearing apart some of these fancier pacifiers for adults when I noticed something

When you know you’re going to enjoy the article.

Yea, no links to any of the tools.

Oh wow… My 10 year old python script may be replaced now.

Edit: And I already had it starred, because it works just like my 10 year old python script.

This is the biggest release I’ve ever done on the server. It’s 14,997 added lines of code, and 10,202 lines removed

Upvote and comment on: https://github.com/binwiederhier/ntfy/issues/1645

Uovote and comment on: https://github.com/binwiederhier/ntfy/issues/1645

Please add this to the post.

My partner might volunteer to try it out, but since she is very regular it probably wouldn’t help much for input.

The main feature she says she misses from Flo (we are also data savy, so she left it), was for when things were irregular, the ability for it to predict the why’s and when’s like stress, etc.

In the current iteration, if something is irregular can you put in what happened and have it auto-adjust?

Also, reminder notifications a couple of days out were helpful.

I had been considering a project like this as well, but one that uses on-device analytics to record the why’s and when’s, then allowing for scrubbed anonymous submissions (date adjusting/etc like you do in a clinical trial) to allow for algorithm development while preserving privacy.

Happy to have a conversation about this for future potential PRs (I am an avid FOSS contributor in both planning and code, even working on a project for the Linux Foundation kernel dev team now).

If you are willing, I would love to see a blog post, video, or repo of exactly how you conducted this audit. Great read, and would like to learn more of your specific process (beyond the readmes and man pages).

Eh, that post title is quite sensationalistic.

No it’s not? The issue is on Awesome Self-hosted, where they had Mattermost listed in FOSS instead of non-free.

Also, if you read the ticket, you can see why people feel the way they do. They’re skirting AGPL rules with the compiled requirement.

Hello Chuck.

Great answers, thank you.

Question: Are failures due to issues on a specific platter? Meaning, could a ZRAID theoretically use specific platters as a way to replicate data and not require 140TB of resilvering on a failure?

While many in fedi will say the above, a simple federated search model could increase adoption. I.E. don’t bother going crazy with it, just add a discovery platform where you can search “your own” or “the network”.