farcaller

joined 2 years ago
[–] [email protected] 3 points 1 month ago* (last edited 1 month ago) (1 children)

I just made a mirror out of two NVMes―they got cheap enough not to bother too much with the loss of capacity. Of course, that limits what I can put there, so I use a bit of a tiered storage between my NVMe and HDD pools.

Just think in terms of data loss: are you going to be ok if you lost the data between backups? If the answer is yes, one NVMe is enough.

[–] [email protected] 0 points 1 month ago* (last edited 1 month ago)
[–] [email protected] 3 points 1 month ago

the issues related to that macro still exist, but the author seemed to call it out and link to an article about it (which doesn't seem disingenuous at all to me).

That's fair, I stand corrected and I overreacted a bit.

I stumbled on the unintended cancellation a few times, but I’m used to select! paradigm from the other languages (and not used to how differently it behaves). I suppose I just expect the examples of its usage to be explicit and actually show what it takes to make select! behave in a way that doesn’t abruptly drop your async function after only going though half of it.

[–] [email protected] 4 points 1 month ago (2 children)

What I find slightly dishonest is bits like

This way of using select in a loop could potentially cause issues regarding cancellation of futures (although in this case it’s fine)

The select example is pretty straightforward and comparable to such in other languages, even to Go's switching on channels. But rust hides an extra bit of complexity with the cancellation concerns that people don’t want to talk about unless absolutely necessary, and it is necessary in so many cases!

[–] [email protected] 13 points 2 months ago (2 children)

You don’t need -it because you don’t run an interactive session in docker. It might be failing because you ask for a pseudoterminal in an environment where it doesn’t make sense.

[–] [email protected] 2 points 2 months ago

Seq is expecting structured logs which yours aren’t. So you want to either convert your app's logs into a structured format (which is generally hard for a random third-party application) or use a log collector that's fine with non-structured logs (e.g. Loki+grafana don’t care about the shape is your logs and you can format the output while querying).

[–] [email protected] 1 points 2 months ago

How does it compare to archivebox in regards to specifically saving content that's a mix of websites and YT videos?

[–] [email protected] 4 points 2 months ago

I’ve been using FreshRSS and Reeder (now Reeder Classic) since google reader stopped being a thing. It's pretty great.

[–] [email protected] 3 points 2 months ago

It's reasonably doable, I migrated a while ago after logseq decided to destroy my data once again.

I'd say obsidian is not really any more a walled garden than logseq is―the storage is a rather common markdown. If anything, obsidian abuses commonmark less. It's way better as a product, though and it's experience is rock solid.

[–] [email protected] 4 points 2 months ago (1 children)

There were quite a few games using the same formula (and improving on it), to the point where I feel Desperados would be my favorite in that genre, not Commandos itself.

I still remember having to reparation my drive and reinstall windows, upgrading from fat16, because commandos wouldn’t fit on either partition.

[–] [email protected] 1 points 3 months ago

It'd be hard to find an actual product because your use case is rather niche and all of those platforms have and expensive certification process. You can DIY a matter solution the easiest, though, there's plenty of devkits for standalone matter devices.

[–] [email protected] 2 points 3 months ago (2 children)

You can (trivially) spin up a fake matter switch from one of their examples. It requires a service running on a Raspi.

Otherwise, what was wrong with a virtual switch in homebridge? I’ve been using one of those for years now to do a bunch of homekit automatons.

 

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 [email protected] to c/[email protected]
 

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
 

Is there any way to see the “all” stream from another instance (pretty much what wefwef does for lemmy.world when there's no account) when I’m logged into my instance?

view more: next ›