farcaller

joined 2 years ago
[–] farcaller@fstab.sh 15 points 6 days ago (2 children)

Next step is discovering atuin! https://atuin.sh/

[–] farcaller@fstab.sh 21 points 2 weeks ago (9 children)

You can absolutely run your own CA and even get your friends to trust it.

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

I don’t think that's plausible.

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

I’m in a same boat, honestly.

Matrix has decent clients but managing a matrix instance is a world of pain, especially if you federate. And its resource use is really bad then: a single user instance can easily demand 4gb ram if you are in a couple popular chatrooms. Key propagation is oftentimes broken. Clients all have mixed support of features.

Xmpp is a joy to host, but there are no decent clients for iOS.

IRC is easy to host, but the IRCv3 coverage for clients is also meh.

I was looking for something that I could throw at casual people with relative ease and there's just not a thing. Even the "techy" chat is in discord nowadays.

 

Federation is eventually consistent, but when we're talking practical terms, how long is too long for a node to be offline?

I suffered a bit of a data loss and while I was able to recover my mastodon instance within 2 days, lemmy took me a week and I don't see anyone spamming the inboxes again.

Should I expect that other servers effectively defederated me and should I resubscribe to my communities or I should give it a few days?

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

I’ll chime in: simplicity. It's much easier to keep a few patches that apply to local OS builds: I use Nix, so my Mastodon microVM config just has an extra patch line. If there's a new Mastodon update, the patch most probably will work for it too.

Yes, I could build my own Docker container, but you can’t easily build it with a patch (for Mastodon specifically, you need to patch js pre-minification). It's doable, but it's quite annoying. And then you need to keep track of upstream and update your Dockerfile with new versions.

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

OP should have vibecoded the title, chatbots know how to use apostrophes.

[–] farcaller@fstab.sh 9 points 3 months ago* (last edited 3 months ago)

Let’s be fair, OAuth is very hard. And requires a web server to make work :-)

This is not a password manager, this is IdP roughly like Authelia, Auth0, etc.

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

While it’s nice, lightweight, and simple, it still blows my mind that a security product has no means for logs audit and the logs themselves are very hard to deal with programmatically.

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

That's not the best example, because CP2077 has its own launcher (at least the steam one)

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

If you want to go the "packaging way", you could use nix's nixCats-nvim to make a fully hermetic nvim installation where you track the origin of all the dependencies (LSPs too) and plugins, all with receipts and hashes and all the good stuff of a reproducible build system. The security industry likes reproducible build systems because there's only one way you can go from source to the artifact.

Then, you package that in e.g. a docker container (which nix can build for you, too) and ship where you need it.

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

One thing about grafana, though, is that you get logs, metrics and monitoring in the same package. You can use loki as the actual log store and it's easy to integrate it with the likes of journald and docker.

Yes, you will have to spend more time learning LogQL, but it can be very handy where you don’t have metrics (or don’t want to implement them) and still want some useful data from logs.

After all, text logs are just very raw, unstructured events in time. You may think that you only look into them very occasionally when things break and you would be correct. But if you want to alert on them, oftentimes that means you’re going from raw logs to structured data. Loki's LogQL does that, and it's still ten times easier to manage than the elastic stack.

VictoriaMetrics has its own logging product too, now, and while I didn’t try it yet, VM for metrics is probably the best thing ever happened since Prometheus. Especially for resource constrained homelabs.

[–] farcaller@fstab.sh 1 points 5 months 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.

 

I finally got to cleaning up the metrics in my homelab and researched the means to separate my long-term and short-term data. This way you can scrape all kinds of noisy sources (e.g. kubernetes) while having a separate store for things you want to observe on longer time windows (months and years). The best thing? It's transparent for grafana and the like, so you can keep all your dashboards intact.

 

I moved off a Synology NAS to a self-managed machine and one thing I still struggle to replace is something like a synology drive. Here are my requirements:

  • server side store data in a plain FS (I want transparency)
  • client side (windows), it must support VFS (download files when needed, support offloading of large files)
  • having snapshots of data is a must

I have a 40gbit uplink to my desktop, so if everything else fails I’ll just use samba with zfs snapshots exposed to VSS, but we’re talking some large files still (think several hundreds of MBs) and I’m not sure Blender will be happy working off a network disk.

I’ve been pointed to next/own-cloud previously, but they don’t seem to cover my use case, I think. Should I actually try one of those? I browsed around owncloud's storage bit (which is written in go), and it seems mostly fitting, but I’ve been told I should steer away from ownCloud towards nextCloud.

 

I’m reading the ActivityPub spec here and it seems pretty fit for client-to-server communications. Yeah, it might be somewhat bulkier than your typical rest api, but it's more universal, which begs the question: why do mastodon and lemmy both decided to implement custom (and incompatible) APIs for their clients to talk to the servers? Wouldn’t it be more straightforward if e.g. my voyager app talked ActivityPub to lemmy.world which then talked ActivityPub to lemmy.ml or something.

What am I missing?

75
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 ›