farcaller

joined 2 years ago
[–] farcaller@fstab.sh 1 points 1 week ago

Storage box networking can be hit and miss. It's ok for incremental uploads, but I went through hell and back to get the initial backup finish, which makes me wonder what it would take to download it in case I have to.

Scp breaks off once in a while, and WebDAV terminates the session. I didn’t try smb as I feel it's a rather weird protocol for the public internet. In the end, I figured it's not the networking per se, it's something with the timeouts on the remote, and I was able to finish the backup using a Hetzner-hosted server as a jumpbox.

But it's cheap, yeah.

[–] farcaller@fstab.sh 2 points 3 weeks ago

Voyager pulls /.well-known/nodeinfo now, if you don’t proxy that to your backend (I didn’t), it will fail.

[–] farcaller@fstab.sh 22 points 1 month ago (2 children)

Isn’t kagi's point that they store very little about you to the point there no search history and you have to pay for the service provided?

[–] farcaller@fstab.sh 8 points 1 month ago

That's not exactly true, synology doesn’t do anything you can’t access from an off the shelf linux (it's your usual mdraid and btrfs). But you better know what you’re doing if you go that route.

[–] farcaller@fstab.sh 4 points 3 months ago

What's going to pay for the search part, then?

[–] farcaller@fstab.sh 6 points 3 months ago (7 children)

Conduit is in no way compact either. I tuned its caches because two gigs of ram seemed ridiculous for a single-user instance but I only got the mobile client sync lag as a result.

XMPP used to be so much nicer...

[–] farcaller@fstab.sh 6 points 4 months ago (2 children)

I think the point here is moving away from long-lived ssh keys and using whatever IdP you have (enterprise cloud or local oidc) to provide short-term ssh keys. It generally improves the security posture as it's similar to ssh with certs but less painful to set up.

[–] farcaller@fstab.sh 31 points 4 months ago

This is the best answer. Your router protects you from the outside, but a local firewall can protect you from someone prodding your lan from a hacked camera or some other IoT device. By having a firewall locally you just minimize the attack surface further.

[–] farcaller@fstab.sh 1 points 4 months ago

Unfortunately, matrix doesn’t have a viable plan for federation, meaning that you'd better onboard on matrix.org or else.

People saying self-hosting mastodon is hard never had to touch matrix. It's not hard, the protocol is literally broken to the point where starting again is not an option.

I’m all in for ditching discord, but matrix is at most mediocre in almost every aspect. It's wild how much easier it used to be with xmpp.

[–] farcaller@fstab.sh 3 points 4 months ago

First party app, yes. Thanks for the recommendation, I’ll give swiftfin a try.

[–] farcaller@fstab.sh 9 points 4 months ago (2 children)

Jellyfin looks pretty bad on an iPad. Subtitles setting keep getting reset on their own, it doesn’t understand basic keyboard controls (spacebar to pause), the UI is overall tiny. Oftentimes it will forget to save the spot where I finished watching and on the next launch will happily play the movie from beginning.

[–] farcaller@fstab.sh 7 points 4 months ago

Matrix is spectacularly cursed to the point of being unusable if you self-host it. The protocol is dumb enough to lock you out of rooms hosted on another server forever if anything goes wrong with the key rotation.

0
submitted 2 years ago* (last edited 2 years ago) by farcaller@fstab.sh to c/fediverse@lemmy.world
 

I wasn't sure how to find the communities I'm interested in, so I quickly hacked together a scraper that makes a list of all the communities(1) of all the servers mine is federating to(2).

You can find it (with a very trivial UI) at directory.fstab.sh. Hover over the link to see the description. Use the search bar to search by text.

Is this something useful or there was a better way to do the same?

  • (1) it does its best to scrape them all but incidents might happen
  • (2) updated nightly
view more: next ›