Sir… You came to us for these comments this time. Are you just here for a fight? It’s not clear what you want from us.
I don’t find your project interesting enough for me, but I was happy you did it. I prefer to keep my infrastructure at home in a controlled environment and take my maps out with me, but I don’t use navigation, I just record GPS tracks.
Now with this post, I’m starting to wonder what your motivations are altogether, particularly considering your responses here.
Eleventy works for me.
Most of what you do is a web app.
deleted by creator
This isn’t the same thing as making VCRs cheap enough that every home has one. There is no FOMO wirh AI at the consumer level, no one knows what to do with it. The only people who want it are the ones who male it!!
🎶🎵 Just Follow the Moneeeyyy… 🎵🎶🎵
Op specifically asked for resources for learning and not sparse answers from users.
research on your own
Come on, man. Did you even read the post.
Really narrow view of knowledge.
The danger of catapulting an entire generation into ai-fed answers isn’t the amount or quality of knowledge, it’s training people to ask and NOT verify, a pillar of attaining wisdom and true expertise.
I’ll have to check this out, I use Kobo sync extensively.
I had some catastrophic docker updates that destroyed my wanderer instance, forcing me to revert to backups. Twice, I’ve had to export all my tracks, reinstall, and re-import the tracks. Both times, the web component broke.
Have these breaking changes been addressed?
Oooh, good one.
From a security perspective, it’s a big mess of inputs and can have really inappropriate access to local filesystem on the web server unless you really know what you’re doing. Combine that with Perl (also a pita to secure), and it’s now a liability.
These are good tech, I used them a lot myself. But the structure of a language and how it builds things is important too, and that’s why very few ppl bother with Perl or CGI now (besides them also being fails on certain security audits.)
Sorry, no disrespect intended, but I’m shocked. It’s like hearing someone say they drive a 1988 Toyota Cressida because it’s great… It was great at the time, but we’ve moved on and the smokeping website should tell you how ancient it is; sponsors from 2007 by companies that don’t exist anymore.
Still alive & still maintained
Alive, maybe. I think any maintenance is down to bodges to keep it running in modern environments. Neither Toby nor Niko have worked on sp in over a decade.
Smokeping is fine if all you do is look at its own graphs and you have enough traffic to see patterns in latency.
But:
I had to retire 2 smokeping monitors because their CGI implementations were security risks. That was 2015. Not a good reason for homelab, but CGI is a pretty ancient and insecure way to interact with the web server.
Smokeping is good in a big organization with lots of traffic and a few broadcast domains. It isn’t really great at monitoring remote sites because ICMP doesn’t tell you what segment in route is causing the issue, even with rping.
I used smokeping a lot in my career from about 2005 to 2015, when security audits made me retire it. Just even using rrdtool with an exporter and graphana would be preferable to smokeping itself.
I pick mad max. In the end, it will come down to oil.
Smokeping? In 2026? Jesus…
I deploy with ansible keys and install ssh with a keys-only config and only ansible access.
Then I run some standard installs and configs with ansible and all future updates to apt, apk and docker are done with one ansible playbook.
I don’t include the ansible host itself in the automation, nor my workstation, just to prevent everything from being broken at once if something goes wrong.
Nice.
There is often a check for battery that is effectively a check of resistance between sense and ground. Looks like that battery is labelled, you might be able to bodge a resistor between sense and ground on the phone and get it to boot without the battery?
Xmpp. Used to be called Google Chat
Holy shit, this is awesome. You had me at combined Fourrier channels.
I just looked back over your post and your answers there and in here. With respect, your writing style sounds combative. I would never ask you to change it for anyone, but you should understand how it comes across.
Regarding the AI disclosure stuff, you aren’t the first burgeoning dev posting to Lemmy to go through this exact gauntlet of “AI slop” accusations. You are on a platform used by a fairly specific group of people who were pissed off enough to leave reddit, so not the usual general “tech enthusiast” crowd, and a fairly militant bunch.
The way I see it, AI is 1) already here and 2) just a tool. It’s being used in the background of a LOT of projects and there is by now simply no way to cover our ears and pretend it doesn’t exist. For better or worse, it’s also changing the pace of development, check out how fast PS5 emulation is happening because of AI tooling.
That said, developer practices that took us 40 years to make standard are still valuable, so folks have legitimate reason to call out your commit and documentation practices. If there is anything I objected to in your project, it might be that.
Ultimately, a created work starts to live a different life once it is public. You started without sharing it, shared the source, and now you have to make a decision: continue sharing and accept that not everyone will like it, or stop sharing. It’s really that simple.