That’s highly dependent on the hardware. My router only has two ports.

Just to make sure you know this, routers are not switches. You might get some of them to sort behave like switches with careful configuration, but most of the time it’s asking for a lot of trouble.

You have three routers? Why?

Throw 2 of them out and get actual switches.

It’s really well documented and easy to config. You just open the page for your IDP, follow the instructions, set a few config setting and you’re off.

The user interface is also really good at this. Often custom identity providers feel hacked on, here it’s integrated really well.

I believe the implementation is based on nextauth.js

It depends on what you mean by seamlessly. I have the Safari bookmarklet menu thingy on iOS and it works great.

I’m using it 99% for recipes. But, I haven’t lost a recipe since I started using it!

All self-hostable software should do single sign-on the way Linkwarden does.

If you are wondering whether or how to support OIDC or SAML or other SSO, look no further for inspiration.

Store torrent files. The magnet links are just the hashes of the torrent files.

Yes, the magnet link points to a specific torrent file, but you will only be able to get them if anyone is still sharing it and currently online.

If you have the torrent file and the content, you can start a new swarm if the old one is dead. If you only have the magnet link and the content, you can’t.

Why?

That’s a rather absolutist claim when you don’t know the orgs threat model.

My recommendation would be to use a hard disk in a single computer, and to use a single operating system for a single computer.

Then you pick the most capable, fastest, native FS that fits your bill.

If you need to transmit data between computers, use the network. It’s that it’s there for.

deleted by creator

Often I already have nginx running for serving some static content anyway.

Otherwise, I’m traefik all the way.

Abortion rights.

Ugh. I know that feeling. That’s why I’ve blacklisted salt stack.

https://news.ycombinator.com/item?id=5993959

There’s a particularly toxic combination of ignorance, laziness, NIH and hubris that you need to make a mistake like that, and I want it nowhere near my servers.

Now, I admit, I’m not one to get carried by the drama in the FOSS sphere (still use Gitea)

This is a bit of a “bell curve meme” situation. I’m extremely about the drama, and I’m back to gitea. The forgejo guys are good at branding, but I’m not seeing great project stewardship. I’ll take my chances with the commercial guys for now.

There was something wonky with the mapping of OIDC attributes to user properties, so I decided to look at the seahub source and see if it would be easy to fix.

Turns out, the whole thing is held together with hope and spit. Literal beginner code.

I run seafile, but holy shit do I regret looking at the source code.

Yes. Very slow. And only accessible from tor clients or tor2web/onion.to-like constructions. Which adds additional delay and errors.

There are things for which onion addresses are the right solution. This is not one of them.

It’s very possible. If you carefully manage your attack surface and update your software regularly, you can mitigate your security risks quite a bit.

The main problem is going to be email. I have found no reliable way to send email that does not start with “have someone else do it for you” or “obtain an IP block delegation”.

That sure does seem to tick a lot of boxes. I’m going to check it out!