Inclusive tax, but exclusive service fee, handling fee, network fee, administrative fee, etc. You get the picture.
We are getting screwed by the energy companies and the infrastructure companies. Everyone wants a piece of the pie.
At least (some of us) are getting money back, when your solar production exceeds your consumption. But that is going to change soon.
Dynamic pricing contract. Planning when to charge the car, running dishwasher etc is small effort.
Adding 5KW solar panels and a change of contract, from >€500 to something like €75. Family of 4, pretty heavy usage.
Vic-20, Atari 600 XL, zx-81.
In that order
Asked several to write a c implementation of some basic networking stuff.
ChatGPT: needed to refine my input, got reasonable output. Complete answers, just compile and run.
Google: the output was just a few snippets, nothing to be used as-is.
MSFT: terrible output, and -no suprise here- the compiled code crashed with null pointer references etc. The worst answers ever.
For simple problems (programming low-level microcontrollers), my go to will be ChatGPT everytime.
Google should get it’s act together, Microsoft can exit the stage.
Yes this.
Check out the don’t vacuum me site and pick a ‘hackable’ robot. Add Valetudo and you’re set.
Using a Roborock S6 here, started by home assistant when no one is home.
For the occasional jobs/accidents, we use a Hyundai cordless. Really robust, easy to clean and properly designed.
That’s my understanding.
And I think a small fee to get out of the googlyclaws. Paying $100 once, to host immich for the family and supporting development is a no brainer to me.
But I understand not everyone has the resources or is willing to donate.
This is just the beginning…
Cars.
You get it…
Thanks for this. Finamp looks really nice.
NetApp makes storage devices, just like Dell’s DataDomain.
Looks like the ad is referring to a ST6000NM0034, a drive from Seagate. Personally, I like to stay away from that brand as far as possible.
Have had good experiences with WD.
Weighted blanket.
Vlans firewall rules and something to route between the different networks.
This can all be achieved with pretty much every Linux installation.
Easydns.ca, no privacy issues. Nothing about me personally in the who’s db (.net tld)
Still testing and fiddling, but I’m using the forgejo-runner. Renovate is just another repository, with a workflow to get it started:
on:
schedule:
- cron: '5 2 * * *'
- cron: '5 14 * * *'
jobs:
build:
runs-on: docker
container:
image: renovate/renovate:37.140-full
steps:
- name: Checkout
uses: actions/checkout@v3
- name: Run renovate
env:
PAT: ${{ secrets.PAT }}
GITHUB_COM_TOKEN: ${{ secrets.GITHUB }}
run: |
echo "Running renovate"
cd ${GITHUB_WORKSPACE}
renovate --token ${PAT}
The renovate image has been pulled by hand and the forgejo-runner will happily start the image. Both PAT and GITHUB secrets are configured as ‘action secrets’ within the renovate repository.
Besides the workflow, the repository contains renovate.json and config.js, so renovate has the correct configuration.
Absolutely!
Running local, self hosted forgejo with a few runners.
Now my code is neatly checked with pre-commit and linters, build when new tags are pushed, renovate is scheduled every 24 hours to check for new releases of stuff etc.
Just a few containers and a happy user :-)
Well, early '90s and pretty much without any documentation apart from the source it was quite a struggle.
I totally agree, but this depends. It helps if you have backups already in place, if a few additional containers or VM’s won’t matter much etc.
Running forgejo and runners took me way less effort than properly setting up sendmail for instance.
It all depends on skills, resources etc. Everyone needs to make these decisions themselves.
Be the cool kid on the block and start hosting your own forgejo instance.
Did Azure DevOps (yuck), did GitHub (meh) now very happy with forgejo.
Not medically trained or experiencing any illnesses, but keep this in mind:
In just a few years, the medical world made huge steps in treating a lot of things using RNA techniques.
Don’t compare a situation 10 or 20 years ago with the possibilities today.