[-] farcaller@fstab.sh 2 points 3 days ago
[-] farcaller@fstab.sh 4 points 5 days ago

I had exactly the same use case and I ended up with a 40G DAC fiber for that case. It ended up cheaper than converting the whole lan to 10G.

That said, it feels like used 10G equipment is easier to come by than 2.5G for now, and if you have 2G fiber uplink and only 1G past the router then it’s a waste.

[-] farcaller@fstab.sh 17 points 2 weeks ago

Garage is trivial to get up and running and it’s more lightweight than minio nowadays.

[-] farcaller@fstab.sh 17 points 2 months ago

I remember when minio just started and it was small and easy to run. Nowadays, it's a full-blown enterprise product, though, full of features you’ll never care about in a homelab eating on your cpu and ram.

Garage is small and easy to run. I’ve been toying with it for several months and I’m more than happy with its simple API and tiny footprint. I even run my (static html) blog off it because it's just easier to deploy it to a S3-compatible API.

[-] farcaller@fstab.sh 16 points 3 months ago

Looking at the resource usage of mine, a tiny cheap VPS for $4/mo would be enough, sans the image store. But it's not a hard requirement unless you expect to have lots of local communities posting pictures.

Lemmy's issue is that it's non-trivial to deploy and oftentimes painful to upgrade.

7
submitted 3 months ago by farcaller@fstab.sh to c/selfhosted@lemmy.world

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.

[-] farcaller@fstab.sh 25 points 3 months ago

If you drop the projector, then airpods already do it better when paired with the watch. There's no point in such a device at all, then.

24
submitted 4 months ago by farcaller@fstab.sh to c/selfhosted@lemmy.world

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.

[-] farcaller@fstab.sh 28 points 4 months ago

By all means, use the publicly available code within the limits its license permits. Always strive to give credit back (I oftentimes add notes to where I took config bits even in my private my-eyes-only repos to have some breadcrumbs).

Remember that licensing and copyrights are kind of separate things. People own copyright to their work (unless they explicitly give it up), and licenses are the terms on which you can use their copyrighted work.

Know the basics of the OSS licenses and know which ones you can copy things from verbatim (e.g. don’t touch AGPL code unless you also use AGPL). Generally, I just keep the original license and add a note to my license file saying that e.g. this code is licensed under Apache 2.0, but some parts are MIT.

It gets somewhat murkier when you use someone's code and base yours on that. IANAL, and that's very much the legal territory. If at all possible, just reuse the original copyright and license and then derive your work (given the license allows that).

Being on the receiving side of this a few times (people using my code verbatim in their projects I stumbled upon) it leaves a bit of a sour taste in the mouth when you see your copyright header replaced with someone else's completely. Don’t do that. All the three times it happened to me, the other party was quick to remedy the situation, though (2 added the original copyright note back, 1 removed all my code). So just don’t do that. Make a habit to read that dumb tall copyright notice at the top of the file every time and you’ll quickly learn what to expect.

[-] farcaller@fstab.sh 18 points 7 months ago

I'd be curious to see comparison with Logseq. As it's rightly mentioned, there are thousands of note taking apps and I’m not quite sure I see the selling point of SB. I really love the idea of notes as a database, but the query langauage seems subpar, more akin to obsidian's dataview than the overwhelming power of tiddlywiki's filters or Logseq's queries.

I went from evernote to tiddlywiki to Obsidian to Logseq and somewhat stuck here now because I got the powerful queries in a very neat UI. With the market oversaturated as it is, I'd be nice to see what Silverbullet brings to the game that others don’t, what are the distinguishing features.

[-] farcaller@fstab.sh 45 points 9 months ago

However, XAMPP didn’t just die because it opened itself up to Microsoft and got extinguished

So, we went from the somewhat imaginary “google killed xmpp” to fully fictional “Microsoft killed xampp” now? it's almost like the fedipact people literally have no clue what they are talking about.

[-] farcaller@fstab.sh 50 points 1 year ago

iOS 17 installs on a 5 years old iPhone though. I don’t think that's an unreasonable window of deceives supported.

39

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?

[-] farcaller@fstab.sh 15 points 1 year ago

The codebase is actually vastly more readable. I’m going to take it for a spin tomorrow and see how well it behaves, but so far it sounds like a much better deal deployment-wide for small instances.

72
submitted 1 year ago* (last edited 1 year 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
[-] farcaller@fstab.sh 56 points 1 year ago

Email is the original fediverse. Just spin off your MTA of choice and suffer trying to convince everyone else you’re not in it for spam.

view more: next ›

farcaller

joined 1 year ago