That, or the watchmakers of old didn’t have to worry about wiring actuators, speakers, and heart rate monitors on the back plate. Or is that against nature and shouldn’t be done in the first place anyway?
For what it’s worth, my F91W has Philips screws on the back plate exactly like this and I never had a problem, and I’ve taken it apart more than a few times (it’s a Sensor Watch!)
The grand promise of FOSS: Surely, somebody else has checked it! (something something log4j)
I wonder if it will be less annoying with a point cloud. You’ll still need to model it, only with a digital reference, correct?
Unsurprisingly but not exactly obvious when I first read about it, alcohol addiction is strongly correlated with alcohol tolerance. I have come to understand intolerances like yours as protection mechanisms of the body (not a scientific claim!)
Similar story here- 34 at the time and a regular social drinker, I decided not to drink one day on a whim (actually just intended to see how hard it would be to abstain for a while) but felt so great without hangovers and just generally so much more energy that I stuck with it. 5 years now and really happy with that development. I have book club 9am on Sundays now, that would have absolutely been out of the question in the before-time.
It really feels like an insane hack in the beginning, how much more time and energy there is.
The guy is many things but unimaginative is not one of them. One of the people who really understood where technology was headed, in the worst way possible.
Tinfoil hat fixes this!
Airtable or nocodb might be suitable for this. Or Nextcloud Forms. But hard to advise since it’s not clear if your focus is on data entry or visualization.
I’m low key on the lookout for something like this as well, to gain independence from mail providers, and I’ve had a browser tab for Mail Archiver open for a few months now but never got around to trying it out. Maybe this would solve your problem?
This looks friendly. I gave up setting up Authelia after my last attempt, but I might give it another go with this when motivation hits me. Some documentation for Traefik integration would be nice.
What a perfectly reasonable headline to read.
Good tires and adequate pressure and I haven’t had a single puncture in years. But I get your sentiment, and of course it’s not for everybody. Although for me, the number one best way to get away from cars is gravel and single trails. So that, and being in the woods, are the main reasons for my love of gravel riding.
Where I’m from, the Eurovelos actually live up to their grand concept and are fully developed and paved as far as I’ve seen (and therefore a bit boring for me), but I don’t have to go far (a day’s ride across a border) and our “pan-european cycle path” is actually “the perfectly good street we happened to have lying around here; have fun!”
I agree with your take on Osmand; a problem many big FOSS projects seem to share. I’m almost certain that there must be a way to properly penalise unpaved roads for routing with brouter, by the way. I’d check it out for you, but I truly dread the settings menus of those two apps…
My main motivation for trying out brouter was to prepare for the Komoot exodus when it will inevitably happen, and I have a different experience to yours. I find the routing to be on par with Komoot (often nearly identical routes, actually), and that’s been the best I’ve seen for my purposes so far. My main priority is to avoid roads for my gravel tours as much as possible (the larger the more urgently) with trail and woods segments actually being a plus and direct path not being important at all.
That said, I do hate the user experience with brouter+Osmand. I have no clue why brouter has to be a separate app. I have no clue how to properly configure it, and I am completely overwhelmed with Osmand’s millions of options, views, and settings. Software that makes me feel dumb and inadequate.
Ah, I see. I thought this was about an issue with FreeCAD, but it is actually a process problem. (Why wouldn’t FreeCAD allow me to stuff arbitrarily complex meshes into a model, and of course that can lead to slow computation times.)
That said, analysis tools built into the software would probably be a useful thing to investigate what makes a file “slow.”
There’s also brouter which acts as a routing companion app to Osmand. It’s a bit of a pain to set up, but gives very good results.
Thanks for writing it up, although the blog post raises more questions for me than it answers. Is that a common thing? I’ve never noticed overly large files, but maybe I wasn’t paying attention? What is the cause of it, complex geometries? What can be done in such a case to optimise?
I wasn’t advocating to get a J4125 in 2025, I was sharing my experience with it. I can’t confirm it choking with Jellyfin.
I’m doing everything you list and quite a bit more on a QNAP with a Celeron J4125. A fraction of the cpu performance you’ll have, yet very capable of all the tasks I ask of it. 16gb of memory is a good starting point I think.
What does your build come out at?
In my experience, that’s something integtators/odoo partners do for you for a lot of money.