HN user
I second that, I have an EzSBC ESP32 board [1] that wakes up twice a day to fetch data through WiFi and three standard mini 1.5V, non rechargeable batteries are still going strong after almost one year. The power supply stage is truly the most important bit when it comes to deep sleep power consumption.
[1] https://www.ezsbc.com/product/esp32-breakout-and-development...
Nice to see the MPCNC here!
Some time ago I have in fact written a small utility based on fzf that solves this problem by letting you comment aliases in your shell config file and fuzzy-search through them:
https://github.com/nmaggioni/wat
The tag system is especially useful to me when I know the general concept I'm after but don't remember the exact wording of the command.
Thanks for chiming in. Any chance that you tried an older, pre-v1.0 version? I used to share some of your considerations, but lately I've seen Nomad evolve at a quicker pace and catch up with some of the features I wanted/liked (ex.: readiness checks were introduced in May 2021 with v1.1, going by the changelog).
As others have already said and basing on the official docs (https://www.nomadproject.io/docs/enterprise), the few Enterprise-only features left don't really feel necessary to me for small-medium deployments; especially when there's an Ops team that can oversee things anyway.
Not trying to play the devil's advocate here, I'm genuinely interested in what I might be missing with my current approach.
Nomad isn’t much better (or free)
"Better" is quite subjective, in my experience I've had workloads that were a breeze to setup in Nomad and painful enough to replicate in K8S that I haven't followed through with the latter. That is especially true in a home server/lab environment where things change and break all the time. I still run Nomad and K3S back-to-back to re-evaluate them periodically for my production needs, but so far my take on the matter hasn't changed.
"Free" puzzles me as well. Free as in open and hackable? The source and buildfiles are all publicly available, hack away to your heart's content. Free as in free beer? The same concept still applies, and if paid support is being referred to here, how's that different from paying any cloud provider to use their managed K8S services?
Have you ever experienced spikes in the S8's readings? Mine seems to underflow and wraparound every once in a while for no apparent reason or when exposed to fresh air for prolonged periods of time. I tried recalibrating it on the 400ppm baseline a few times but the issue hasn't gone away.
Lower the temperature or turn off when not moved for some time, better temperature control via PIDs, set a voltage cutoff when running off battery packs...
Great execution, and the author's blog has a bunch of other very interesting HID-related posts.
From last time I hacked something up with a Sphero [1] I remember having to lock the motors to read the raw gyro/acc data, this would make the ball itself quite unbalanced but it's an interesting idea nonetheless.
Did you even skim through the article? That's not the point at all :)
gPodder is already pretty great at this and doesn't require per-podcast config files. Some time ago I even made a simple WebUI for it: https://github.com/nmaggioni/dashpodder
I had the same exact concern, and I haven't been able to find reliable confirmations on this being completely impossible either.
It's easily testable, though, that a webpage that isn't focused (because an extension's pane is open) doesn't receive input events. Likewise, Chrome [1] and Firefox [2] extensions themselves cannot bind to relevant keys for example. All in all I would say that going through an empty tab is unnecessary - even though I got into the habit of doing it as well - and even if this wasn't true 2FA should be enough to thwart most malicious actors.
[1] https://developer.chrome.com/extensions/commands [2]: https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/Web...
AFAIK every user with a supported wallet received it, the airdrops started way before Keybase supported XLM. See earlier blog articles: https://www.stellar.org/blog/bitcoin-claim-lumens-2/ and https://www.stellar.org/blog/bringing-lumens-to-millions/
Stellar (https://www.stellar.org/overview) isn't part of Keybase per se, they've just developed an integration - or better said, a wallet - for that system. To me Stellar's mission doesn't seem too far apart from Keybase's, I can understand why they see value in it for their users.
LXC Containers:
- Koel (Web-based music player; https://github.com/phanan/koel)
- Aria2 (generic downloader; https://aria2.github.io/)
- GPodder (podcast downloader; https://gpodder.github.io/)
- PiHole (mostly for curiosity, I now use full-blown DNS & DHCP servers; https://pi-hole.net/)
- OpenVPN (https://openvpn.net/)
- Pritunl (OpenVPN failover; https://pritunl.com/)
- PlexPy (Plex monitoring; https://github.com/JonnyWong16/plexpy)
- BIND (DNS server; https://wiki.debian.org/Bind9)
- ISC-DHCP (https://wiki.debian.org/DHCP_Server)
- Smokeping (connection monitoring; https://oss.oetiker.ch/smokeping/)
- Ansible (central host with playbooks; https://www.ansible.com/)
- Graylog (log aggregation; https://www.graylog.org/)
- Wallabag ("read it later"; https://wallabag.org/en)
- Home Assistant (home automation; https://home-assistant.io/)
- Bookstack (documentation; https://www.bookstackapp.com/)
- Observium (network devices monitoring; https://www.observium.org/)
VMs:
- PfSense (firewall & permanent VPN for some containers; https://www.pfsense.org/)
- Rancher (Docker orchestration; http://rancher.com/)
Rancher (Cattle environment):
+ ELK stack (https://www.elastic.co/)
+ Concourse CI (just to experiment, I prefer GitLab's CI; https://concourse.ci/)
+ Dumpster (my own temporary file upload platform, with additional YubiKey support; https://github.com/nmaggioni/dumpster)
+ Own Telegram bot (talks with ELK)
+ Let's Encrypt renewal daemon
+ FaaS (either https://github.com/iron-io/functions or https://github.com/alexellis/faas, even though I'm actually waiting for https://openwhisk.incubator.apache.org/)
+ Private Docker registry
I may have left something out, some more services/containers/VMs are disabled due to low usage.
[Syncthing](https://syncthing.net/) is the perfect tool for the job. Set Calibre's directory on your PC as the main folder, and it'll propagate changes wherever you want.
Section gone. Thank you for having found the time to report back, anyway.
I wan't focusing on hardening a server, my point was avoiding simple random scans for the sake of log management. Maybe I've used the word "security" too lightheartedly?
Last year I made a pseudo-random text generator based on Markov Chains as a summer project to learn C++: https://github.com/nmaggioni/MarkovText
It's in Italian since it just was an hobby project and I didn't spend too much time adapting it for the public domain, but it may be interesting for someone.
This is my first API-based NodeJS project, I use it daily on my team's production server. Any feedback is gladly accepted!