Just this guy, you know?
Take it to an electronics recycling center. Seriously.
If you already have a homelab, you plan to replace it, you don’t want to repair it, and you don’t have an obvious use case for another machine (it’s just another computer; you either have the need for another computer or you don’t), then holding onto it is just hoarding.
deleted by creator
If you have an Android phone I can’t recommend Genius Scan enough. Fast, accurate, lots of features. I use it with syncthing by exporting the files to a folder that’s configured to sync the paperless input folder.
Just want to say thank you! Paperless is one of the first things I recommend to anyone considering self hosting their infra. Amazing piece of work!
deleted by creator
“Huh weird, I tried to use <insert service here> and it’s not working. Welp, guess I better fix it…”
That’s a goal, but it’s hardly the only goal.
My goal is to get a synthesis of search results across multiple engines while eliminating tracking URLs and other garbage. In short it’s a better UX for me first and foremost, and self-hosting allows me to customize that experience and also own uptime/availability. Privacy (through elimination of cookies and browser fingerprinting) is just a convenient side effect.
That said, on the topic of privacy, it’s absolutely false to say that by self-hosting you get the same effect as using the engines directly. Intermediating my access to those search engines means things like cookies and fingerprinting cannot be used to link my search history to my browsing activity.
Furthermore, in my case I host SearX on a VPS that’s independent of my broadband connection which means even IP can’t be used to correlate my activity.
Agreed, which is why you’ll find in a subsequent comment I allow for the fact that in a multi-user scenario, a support service on top of Git makes real sense.
Given this post is joking about being ashamed of their code, I can only surmise that, like I’m betting most self-hosters, they’re not dealing with a multi-user use case.
Well, that or they want to limit their shame to their close friends and/or colleagues…
The idea of “self-hosting” git is so incredibly weird to me. Somehow GitHub managed to convince everyone that Git requires some kind of backend service. Meanwhile, I just push private code to bare repositories on my NAS via SSH.
Honestly, for personal use I just switched to straight Markdown that I edit with Vim (w/ Vimwiki plugin) or Markor on Android and synchronize with Syncthing. Simple, low effort, portable, does enough of what I need to get the job done.
And if I wanna publish a read-only copy online I can always use an SSG.
It has the benefit that the container can’t start before the mount point is up without any additional scripts or kludges, so no race conditions or surprise behaviour. Using fstab alone can’t provide that guarantee. The other option is Autofs but it’s messier to configure and may not ship out of the box on modern distros.
Assuming systemd, create a file like
/etc/systemd/system/dir-to-mount.mount
And then configure it per the systemd docs:
https://www.freedesktop.org/software/systemd/man/latest/systemd.mount.html
Then modify the docker unit file to have a dependency on the mount unit so it’s guaranteed to be up before docker starts.
Any reason not to use something like Gotify and handle it as a notification instead?
Frankly, I’d rather pay a motivated and focused developer if the product is good. And Symfonium is fantastic.
My vote: not if you can avoid it.
For casual home admins docker containers are mysterious black boxes that are difficult to configure and even worse to inspect and debug.
I prefer lightweight VMs hosting one or more services on an OS I understand and control (in my case Debian stable), and only use docker images as a way to quickly try out something new before commiting time to deploying it properly.
I wonder how long it’ll take before we finally collectively reject the SV ethos that size is the only metric that matters and success is only achieved via monopoly…
There was a time when Usenet and BBBses and IRC was tiny and yet people still found value through community in those places.
Maybe, and I know this is a wild idea, platforms don’t have to include every human on the planet to be meaningful, relevant, or valuable.
Not if you use a Hurricane Electric tunnel for ipv6 transit. My ISP hands out V6 addresses and I still use HE so I get a stable, globally routable /48 that moves with me (I had to switch ISPs recently and I just had to update my tunnel and everything just worked).
Lol, they’re not? THIS WOULD BE YELLING AT YOU. This is me calmly explaining that “running for profit” and “running at a profit” isn’t the same thing.
No it doesn’t.
Syncthing only needs to remember the current state of the files/folders it’s syncing. Not everything it’s every sync’d.
It does that by either periodically scanning the filesystem to look for changes since it last scanned (based on the file creation and modification dates that are stored in the filesystem), or it registers with the operating system to receive events when files are created, modified, or deleted.
When Syncthing notices a create, update, or delete, it pushes those changes to the receiver and then updates it’s record of the filesystem state accordingly.
It also pushes whole files, not deltas. So it doesn’t care how the files changed, only that they did.
Even with hundreds of thousands of files to sync this is a relatively small amount of state as it’s just file paths and their create/modify dates.
I can say with confidence this is all 100% correct and also that as an IC you’re damned if you do and damned if you don’t.
Don’t use AI and your code output isn’t high enough, you’re flagged for underperformance and PIP’d unless you get onboard.
Use AI and you rapidly deskill. And if you’re a relative newcomer to the industry you never learn in the first place.
At this point all I can say is: ride it out by day. Practice the old fashioned way by night. Cuz either we have to keep our heads down until this blows over, or we move with times and accept that software development as we knew it is gone for good.