Hold on, I’m a little confused. Are you talking about paperless the document management software (and it’s ng/ngx forks) or a different software with the same name?

Because you can set up mail inbox processing in that software but I’m not sure how that connects to forwarding to multiple different mailboxes, or vice versa profit from merging multiple forwards.

I’m not so sure.

The right wing would be instantly defederated from the rest while the left wing builds three identical versions that all say they wanna go forward while pulling the plane in different directions.

Everybody hates the huge central fuselage but can’t disconnect from it without falling from the sky.

Most of the discussion focuses on snide comments between the slightly different wing designs while all the critical tail components are held together by 3 single selfhosting admins. Then one of them goes on holiday and the tail fin just disappears.

That’s brilliant news!

I know this is still just very basic federation with mutual following of users, etc. - but having a working mvp implementation of this makes me really hopeful for the stepwise introduction of more and more federation goals to come to fruition.

Just throwing another alternative out there which I’ve been very happy with: lissen - ‘Clean audiobookshelf player’.

Has streaming/downloading for offline listening, sleep timer, custom bookmarks and custom speeds. Just the browsing functionality is at best ‘functional’ (nice search but if you don’t know what to listen to next just gives you one long list sorted by title)

I am one of those happy taskwarrior users. For more advanced recurrence syntax in taskwarrior there’s also the relatively new nautical extension. It essentially splits recurrence into things that recur based on calendar/clock events (e.g. every first workday of the month, every second Sunday, etc.) or based on previous completions (e.g. do something 3 days after last time, or every x hours after last doing it).

It’s pretty neat and functional but, fair warning, also early on in development and changing quite radically through its versions still.

Otherwise also codeberg.org has a pages feature for a while.

And others that come to mind are surge.sh, Netlify, and Vercel that I think all offer simple one-push static hosting. Vercel and Render can also do dynamic pages, not sure about the others.

Edit: oh and of course GitLab if you’re looking for an almost 1-to-1 Pages experience.

Whoa I didn’t know that was an option, is it part of the export menu? That would make some of my - we needed to change something after all - situations much easier at work.

Couple of days ago ‘honey I shrunk the vids’ was posted here, a very lightweight tdarr alternative. https://piefed.ca/c/selfhosted/p/571213/honey-i-shrunk-the-vids-mr-universe-edition-v1-0-5

But I haven’t tried it - I’m not sure if it’s perhaps gui-only, and it seems to be AI coded to a certain degree, so YMMV.

Conversations is working very well on my phone as UP distributor.

On a more personal note, still eagerly reading your updates here every couple of weeks. Sounds like it’s shaping up nicely!

Good luck with the api wiring to let people control the forges directly from the interface for 1.0 - if you ever need a tester for forgejo integration you can hit me up.

While the comment was obviously a bit rude, perhaps you can take something constructive out of it. I see that you have a nice compose file prepared as an example with postgres, and a curl into bash for ‘automatic installation’.

Many feel a bit uncomfortable with doing that - especially if the script ultimately just sets up docker containers again. Maybe you could add a ‘quickstart’ section there which just consists of a single docker run command setting up the sqlite version.

That way you have the best of both worlds and both people wanting a production setup example and those just wanting to quickly try are served.

I have long had a switch to pangolin for my homelab services on the roadmap. Can you explain what you mean with internal connections making more sense?

It uses a completely different paradigm of process chaining and management than POSIX and the underlying Unix architecture.

I think that’s exactly it for most people. The socket, mount, timer unit files; the path/socket activations; the After=, Wants=, Requires= dependency graph, and the overall architecture as a more unified ‘event’ manager are what feels really different than most everything else in the Linux world.

That coupled with the ini-style VerboseConfigurationNamesForThatOneThing and the binary journals made me choose a non-systemd distro for personal use - where I can tinker around and it all feels nice and unix-y. On the other hand I am really thankful to have systemd in the server space and for professional work.

That’s really cool. After I replied I also remembered you can have multiple libraries in audiobookshelf so even if side-by-side doesn’t work it shouldn’t be an issue.

Unfortunately I love my Readest reading app too much to switch away but it’s nevertheless good to know for other family members.

Wait you use it also for epub/pdf? How does that work, can you connect a client and grab it from there? Can you have both an audiobook and text version of the same book?

Just in case you wanna try again with readarr, after all the little drama and the main app being unmaintained, there’s 2 forks which are maintained and work pretty well

• Faustvii/readarr simply fixes the app to keep running
• pennydreadful/bookshelf adds a choice of metadata provider, so you can use hardcover (instead of goodreads) for really good metadata

I’ve successfully been running bookshelf for a bit now, after the original stopped working for me completely.

The code forge is gitea/forgejo, and the proxy in front used to be traefik. I tried fail2ban in front for a while as well but the issue was that everything appeared to come from different IPs.

The bots were also hitting my other public services pretty hard but nowhere near as bad. I think it’s a combination of 2 things:

• most things I host publicly beside git are smaller or static pages, so quickly served and not draining resources as much
• they try to hit all ‘exit nodes’ (i.e. links) off a page, and on repos with a couple hundred+ commits, with all the individual commits and diffs that are possible to hit that’s a lot.

A small interesting observation I made was that they also seemed to ‘focus’ on specific projects. So my guess would be you get unlucky once by having a large-ish repo targeted for crawling and then they just get stuck in there and get lost in the maze of possible pages. On the other hand it may make targeted blocking for certain routes more feasible…

I think there’s a lot to be gained here by everybody pooling their knowledge, but on the other hand it’s also an annoying topic and most selfhosting (including mine) is afaik done as a hobby, so most peeps will slap an Anubis-like PoW in front and call it a day.

twice

I’m providing hosting for a few FOSS services, relatively small scale, for around 7 years now and always thought the same for most of that time. People were complaining about their servers being hit but my traffic was alright and the server seemed bulky enough to have a lot of buffer.

Then, like a month or two ago, the fire nation attacked the bots came crawling. I had sudden traffic spikes of up to 1000x, memory was hogged and the CPU could barely keep up. The worst was the git forge, public repos with bots just continuously hammering away at diffs between random commits, repeatedly building out history graphs for different branches and so on - all fairly intense operations.

After the server went to its knees multiple times over a couple days I had to block public access. Only with proof of work in front could I finally open it again without destroying service uptime. And even weeks later, they were still trying to get at different project diffs whose links they collected earlier, it was honestly crazy.

I ended up adding go-away in front of my code forge and anything showing dynamic info, and it turned out to be way less of a hassle than I feared with two redirects and a couple custom rules.

If you already have traefik redirecting to your services, shouldn’t be too tough to get the extra layer of indirection added (even more so if it’s containerized).