klangcola

joined 3 years ago
[–] klangcola@reddthat.com 6 points 2 days ago

Thanks for sharing the knowledge:)

[–] klangcola@reddthat.com 11 points 5 days ago

Honestly 20km/h seems kinda slow. As a kid I'd do 20-25, and these days most European countries have a 25km/h limit on e-bikes. So 20km/h seems just low enough to be a hindrene.

Ultimately it depends on the bicycle lane or road though, just like for cars. There a huge difference between a crowded narrow inner-city cycle lane with immediate adjacent houses and other things obstructing vision, compared to a suburban cycle path with less traffic and completely unobstructed vision

[–] klangcola@reddthat.com 4 points 2 weeks ago (1 children)

That sounds wonderful. And awful. Weather pending

[–] klangcola@reddthat.com 32 points 2 weeks ago

Also I feel confident Prusa will not try a rug-pull enshitification move in 6 months time after buying their printer, unlike certain other manufacturers (Bamboo)

[–] klangcola@reddthat.com 2 points 2 weeks ago (1 children)

Yeah that was my assumption. But I hadn't considered WOL being broadcast, so now I'm not so sure. I would assume it's broadcast on both IP and Ethernet layer. It's time to do some wiresharking :)

[–] klangcola@reddthat.com 20 points 2 weeks ago (2 children)

Not exactly a new book, but All Quiet on the Western Front was a fantastic read. It's a grotesquely frank depiction of the unfortunate "Have Not"s fighting a meaningless war for the "Have"s in society, set in the german trenches of WW1.

[–] klangcola@reddthat.com 1 points 3 weeks ago (4 children)

Maybe something else going on then, but ive never gotten WOL to work after a blackout when there's two switches between sender and receiver. After powering up the receiver once, WOL works again

[–] klangcola@reddthat.com 3 points 3 weeks ago* (last edited 3 weeks ago) (7 children)

If you're already using node-red, the Wake On Lan node works well, and with node-red it's easy to trigger the magic packet based on whatever trigger condition you want.

The only limitation I know is WOL doesn't work after a power outage, because the switch and RPI doesn't know where to find the target machine

Thanks for the tips on reusable enterprise cards btw

[–] klangcola@reddthat.com 19 points 3 weeks ago (1 children)

I'm surprised they chose MIT licence rather than AGPL or GPL

[–] klangcola@reddthat.com 4 points 3 weeks ago (1 children)

In math class when learning statistics we learned "the law of large numbers" , how with enough samples the average approaches the probability. Then applied it to two real world examples, gambling (lottery and roulette) and insurance. The math was the same, and the house always wins because the house deals in large numbers.

The takeaway is that gambling is stupid because the house always wins.

But also, statistics do not apply to individuals, so insurance is not stupid. At least not for life-altering expenses, like home, medical and traffic.

[–] klangcola@reddthat.com 1 points 1 month ago

The 'old' Phillips is not the same as the current. The original Phillips is now doing medical equipment mainly, selling to hospitals etc. Phillips Lighting is now Signify, though as far as I can tell that's still a Dutch company. Phillips consumer electronics where spun of and sold out, to a Chinese buyer I believe. TVs and monitors I think were sold out separately from general consumer electronics.

[–] klangcola@reddthat.com 3 points 1 month ago

Zim Desktop Wiki is absolutely excellent

 

On windows, Notepad++ compare plugin let's you compare unsaved files. So to compare two texts copied from elsewhere, just make two new tabs and paste the texts. Compare plugin will happily compare line by line.

On Linux I havent found something similar. The closes is Kate, but you still have to save tmp1.txt and tmp2.txt , and remove the clutter when finished.

Does anybody know a compare app that just lets you paste two text blocks without saving files first?

 

What are the pros and cons of using Named vs Anonymous volumes in Docker for self-hosting?

I've always used "regular" Anonymous volumes, and that's what is usually in official docker-compose.yml examples for various apps:

volumes:
  - ./myAppDataFolder:/data

where myAppDataFolder/ is in the same folder as the docker-compose.yml file.

As a self-hoster I find this neat and tidy; my docker folder has a subfolder for each app. Each app folder has a docker-compose.yml, .env and one or more data-folders. I version-control the compose files, and back up the data folders.

However some apps have docker-compose.yml examples using named volumes:

services:
  mealie:
    volumes:
      - mealie-data:/app/data/
volumes:
  mealie-data:

I had to google documentation https://docs.docker.com/engine/storage/volumes/ to find that the volume is actually called mealie_mealie-data

$ docker volume ls
DRIVER    VOLUME NAME
...
local     mealie_mealie-data

and it is stored in /var/lib/docker/volumes/mealie_mealie-data/_data

$ docker volume inspect mealie_mealie-data
...
  "Mountpoint": "/var/lib/docker/volumes/mealie_mealie-data/_data",
...

I tried googling the why of named volumes, but most answers were talking about things that sounded very enterprise'y, docker swarms, and how all state information should be stored in "the database" so you shouldnt need to ever touch the actual files backing the volume for any container.

So to summarize: Named volumes, why? Or why not? What are your preferences? Given the context that we are self-hosting, and not running huge enterprise clusters.

view more: next ›