It is. I think Ethan is joking, see the other links in the same paragraph

Thanks for all the feedback. I’m not the author, just a fan re-sharing Ethan Sholly’s posts here on Lemmy because I prefer it to reddit.

If you like This Week in Self-Hosted, send some love Ethan’s way and let him know you want him to keep doing what he does by subscribing (free) and/or becoming a paid supporter – see https://selfh.st/#/portal for more info.

I do author other stuff, elsewhere. I have worked with Ethan in the past and I hope we’re able to do more together in the future!

Heads up re: Actual: 25.2.1 bugfix release dropped yesterday. https://actualbudget.org/blog

Thanks for all the kind words. Agreed, I love this newsletter too!

I’m not the author, just a fan re-sharing Ethan Sholly’s posts here on Lemmy.

If you like This Week in Self-Hosted, let Ethan know you want him to keep doing it by subscribing (free) and/or becoming a paid supporter.

Hopefully Fork recipes also tries reading schema.org recipe json-ld data directly? I doubt AI is necessary for screen-scraping online recipes.

https://selfh.st/apps/ is a nice list

This.

Shameless promo for a book I wrote featuring same: https://selfhostbook.com/

Probably. It is FOSS so it seems unlikely that it would include malware since that would be a massive fiasco if any malware were found. But of course the only way to know for sure is to review the code yourself.

For what it’s worth, the promise right in the source is:

Jellyfin Wrapped is an entirely client-side application. Your data stays private and is never sent to any external service.

I tried it. I first opened my browser developer tools and watched network activity and, after downloading the app from https://jellyfin-wrapped.jpc.io/ , only saw traffic to my own Jellyfin server.

I’m not the author, just a fan re-sharing Ethan Sholly’s posts here on Lemmy.

“What’s the better Git? // GitLab vs Gitea” - Forgejo. :-)

Hi! Author here. I added a http → https redirect to my book website, thanks all. I do intend to always serve public content via https to (as other smart folks have thoughtfully mentioned) guard against stuff getting messed with between my server and your browser (however unlikely that may be). In this case I thought my server was redirecting to https, but turns out my Firefox was forcing https (again, same as other smart folks said).

re: “expert”, ugh, I’m embarrassed to even use that word, but someone else graciously called me that (so I intended to remove “self-proclaimed”), and it supposedly helps for sales. All I know is I’m growing and learning just like you, the more I know the less I know I know, and I make mistakes all the time. I always appreciate kind corrections/feedback/comments/patches/suggestions/etc.

That includes feedback on https://github.com/meonkeys/shb/blob/main/pelican/website/content/extra/.htaccess … I feel clever fixing two things in a single redirect (getting rid of www. and forcing https), but I’m not sure if I’m doing something silly or dangerous here. I’m definitely not an expert at Apache mod_rewrite, I just cobbled that together from official docs and stackoverflow posts.