eshol

joined 4 months ago
 

Hey, c/selfhosted! Thanks to all who participated in my recent '2026 Self-Host User Survey'. This community contributed a bunch to this year's increase in respondents (+52%), and I'm incredibly grateful for the support.

The results are visualized as usual via Chart.js. Happy to talk through any of the results or provide more details where things might not be clear.

New this year is a section on AI usage, a Linux distribution question, and the ability to overlay prior year responses on the charts for easier year-over-year comparisons.

Thanks again!

 

Hey, c/selfhosted! Thanks to all who participated in my recent '2026 Self-Host User Survey'. This community contributed a bunch to this year's increase in respondents (+52%), and I'm incredibly grateful for the support.

The results are visualized as usual via Chart.js. Happy to talk through any of the results or provide more details where things might not be clear.

New this year is a section on AI usage, a Linux distribution question, and the ability to overlay prior year responses on the charts for easier year-over-year comparisons.

Thanks again!

[–] eshol@lemmy.world 5 points 4 days ago (1 children)

There is at least one workaround, if you don't mind being a bit flexible.

GitHub lets users add multiple email addresses to their accounts and assign them as notification recipients. I've added a Kill-the-Newsletter (not affiliated) email to my account, and then use custom routing to route all emails for orgs I'm a part of to my email address - and everything else to Kill-the-Newsletter.

With this setup, all notifications related to orgs I specify come to my primary email address, anything else by default hits the RSS feed from Kill-the-Newsletter and keeps my inbox from getting slammed when a particular issue/etc. has a ton of activity.

[–] eshol@lemmy.world 7 points 5 days ago (1 children)

I'm working on them - hopefully next!

[–] eshol@lemmy.world 6 points 3 weeks ago* (last edited 3 weeks ago)

Good call-out. The directory pulls the prominent language from each project's repo, which is JavaScript for Mailcow.

I should update the dataset to grab any languages above a certain % threshold (25%?) to prevent instances like this where something might fall through the cracks.

[–] eshol@lemmy.world 44 points 3 weeks ago (3 children)

I also maintain a language filter over at selfh.st/apps that can be used to identify PHP-heavy platforms:

https://selfh.st/apps/?language=PHP

123
submitted 1 month ago* (last edited 1 month ago) by eshol@lemmy.world to c/selfhosted@lemmy.world
 

Hey, c/selfhosted! Every year I facilitate a 40-45 question user survey identifying habits, trends, and preferences across the self-hosting and homelab crowd.

I kicked off this year's survey this morning and would love for everyone to take 10-15 minutes to complete it!

The survey will remain open until October 31st, and results will be published in early November.

As usual, I've also published a separate form to collect feedback on this year's survey and ideas for future surveys, which I've linked to below.

Thanks!

[–] eshol@lemmy.world 35 points 1 month ago (1 children)

Thanks for always posting it in my absence!

186
submitted 1 month ago* (last edited 1 month ago) by eshol@lemmy.world to c/selfhosted@lemmy.world
 

Where we're going, we don't need Windows.

[–] eshol@lemmy.world 22 points 3 months ago (13 children)

Hey, I'm the editor/author. I may be overexaggerating the backlash a bit, likely because I spend so much time curating content for the newsletter each week that I'm constantly exposed to the worst-of-the-worst reactions.

[–] eshol@lemmy.world 6 points 3 months ago (1 children)

I believe it requires sidecar lyric files, although I'm not sure which formats it all supports.

You might try something like this to collect them: https://github.com/f1nniboy/lrcmux

[–] eshol@lemmy.world 2 points 3 months ago (1 children)

Would you mind sharing more about your experience with Simplefin? I've been looking to make the jump, but I've read a fair amount of feedback that seems to indicate it might not be worth it given issues with instability, inconsistency syncing, etc.