

Well that certainly makes a lot more sense now. I wasn’t familiar with Philips shavers with replacement blades. 🙄
Well that certainly makes a lot more sense now. I wasn’t familiar with Philips shavers with replacement blades. 🙄
Making their product live longer is not usually the top priority for manufacturers. I like the initiative, of course, but I’m sort of waiting for the other shoe to drop. Sounds too good not to be a greenwashing gimmick.
I mean there are robot arms for a lot more than that, but that’s not the point. It’s like saying a Parol 6 costs 5 bucks, but it’s actually the price of the mounting screws.
Their build instructions state 242 for a single arm. Lots of contradicting information. Maybe they are betting on insane economies of scale… 🙄
Edit: Haha, I think I figured it out. USD 120 are the 3d print parts alone. That’s not a false promise at all!
The BOM for the components alone without the print is USD240. Why is the article talking about USD100?
Freecad is well worth your time. Yes it is a bit unwieldy at first, but once it starts to click you can be fast. For me, the most time consuming aspect is usually wrapping my brain around what the model should look like. Achieving it is then either trivial or you quickly look it up if it isn’t. There are lots of good tutorials.
If you’re trying to design anything functional, you should really go with a parametric modeller.
I’m a big fan of Radiohole, especially their song Grape (“I’m a grape, I’m a raisin.”)
Does this do/can it be used for keeping track of bicycle maintenance? Mostly which components are used (tires, brake pads,…) and when maintenance was done and so on?
I never designed a speaker. I have been looking for designs a few weeks ago, and there’s too much stuff out there and too little to go on if it’s actually worth it/better than HiFi speakers I already have. Maybe some day, if I find a good bookshelf speaker project that seems achievable.
Awesome, thanks for the reply. I’ve been curious about printing speakers myself, but it seems like a daunting task.
Do tell about the speaker. Did you design it yourself? What does it sound like?
I think OSMC does this.
You can set up your project in a private repo and in your deploy action push it to the main branch of your public Pages repo. I agree it’s not a huge deal to show the source, but I prefer it like that.
name: Deploy Hugo site to Github Pages
on:
push:
branches:
- main
workflow_dispatch:
jobs:
build:
runs-on: ubuntu-latest
steps:
- name: Checkout repository
uses: actions/checkout@v4
- name: Set up Hugo
uses: peaceiris/actions-hugo@v3
with:
hugo-version: "0.119.0"
extended: true
- name: Build
run: hugo --minify
- name: Configure Git
run: |
git config --global user.email "you@example.com"
git config --global user.name "Your Name"
- name: Deploy to GitHub Pages
env:
GITHUB_TOKEN: ${{ secrets.DEPLOY_TOKEN }}
run: |
cd public
git init
git remote add origin https://user/:${{ secrets.DEPLOY_TOKEN }}@github.com/USER/USER.github.io.git
git checkout -b main
git add .
git commit -m "Deploy site"
git push -f origin main
edit: Markdown is adding a / after “user” in above git remote
command. Don’t know how to get rid of it.
Thanks, good read. Which dryer does everybody use?
My Nextcloud journey went from a Raspberry Pi 2B with a single USB HDD over a Pi 3B to a QNAP 2bay NAS on RAID 1 with a proper backup strategy including daily encrypted cloud backup. Having come to rely on the setup much more than when I was starting out playing with it years ago, I sleep much easier now. That said, I never lost any data, even on very questionable hardware without any redundancy whatsoever.
If you’re not very set on hosting at home, hosting a static Hugo page directly on Github Pages is incredibly convenient and easy (and free.) With the right Github Action, updating the site is as simple as pushing content to the main branch and it automatically deploys. And should Github ever give you a reason to do so, moving away is as simple as copying your static files to any other webhost and pointing your domain there instead.
Edit: It’s of course equally easy to deploy on your NAS - just a basic nginx serving the directory with your static site that Hugo generated.
Are you looking for advice regarding administration or the platform?
I say for a simple blog it’s hard to beat Hugo. There are plenty of nice themes and easily adjustable, too with a bit of html/css.
Is it? 😂
Short blogs with few but high quality articles are actually the salt of the earth.
I encourage you to do it, there are many options like Hugo, and your intellectual property will never be locked in a company’s app store (Prusa seems trustworthy for now, but as we’ve seen, lockout is always just a TOS change away.)
You already have the writeup and hosting a static site on github pages or similar doesn’t incur costs, so the only thing you need is some time and a domain. 🙂
A Bambulab A1 Mini costs 200 bucks and churns out incredible prints with zero hassle. There’s literally next to no barrier to entry anymore.