

So it’s like a LibraryBox with an Archiver?
So it’s like a LibraryBox with an Archiver?
It usually is with wine lol
You need calibre with the De-DRM extension and an old version of the kindle desktop app.
Hopefully matter casting will be a bit more fleshed out by then.
Yeah this terminology just gives me the impression they don’t consider the AGPL to an actual license
I use FreshRSS in a docker container both served and funneled from my tailscale network (can’t fetch feeds otherwise) and I read it on mobile with FeedMe. My main reason for using FeedMe is the customizable mobilizer though I’m pretty sure you can enable that in FreshRss as well.
This will save you a lot of pain lol
I recently fell into this rabbit hole myself! Though I decided against hosting the blog myself(because I don’t want to do anything stupid lol) Nowadays for sites like that you can install a static site generator to automatically build the site based off of markdown files. I personally use Hugo but I hear good things about Jekyll too.
The way mine is set up I make a post or a page on my machine and push it to my backend github repo. Github detects a change and rebuilds the site with the new content using a github action, then uploads the whole public folder to my host at neocities.
I just saw one in fdroid and I can’t remember it now, lemme see if I can find it.
EDIT: it was zulip
It should! As long as you can get it to the bios screen you should be able to get it to boot a live USB. I actually resurrected my EeePC1005 two weeks ago with DamnSmallLinux2024.
How I keep that sort of thing in a single automation is by using trigger IDs and a service call with a template for said trigger id.
Something like this:
alias: Hallway Motion Light
description: ""
trigger:
- platform: state
entity_id:
- binary_sensor.hallway_motion_occupancy
to: "on"
id: "on"
- platform: state
entity_id:
- binary_sensor.hallway_motion_occupancy
to: "off"
id: "off"
for:
hours: 0
minutes: 1
seconds: 0
condition: []
action:
- service: light.turn_{{ trigger.id }}
data:
transition: 3
target:
entity_id: light.hallway_light_2_2
mode: single
Yeah it looks like OP is using the device actions instead of dealing with the entity directly.
I can too, which is what gets me. Honestly after I think it might boil down to how far removed your provider is from directly getting the number from the FCC(or how trigger happy the entity they’re getting the number from). Also possibly if it’s considered a landline or mobile number, it looks like those are distributed differently.
Sort of? It looks like this is unique to SMS over VOIP. Which don’t get me wrong, it’s still fucking stupid. But maybe, just maybe there’s a middle ground between getting inundated in robocallers trying to reach us about our cars extended warranty and not being able to send the word Scunthorpe over SMS.
Yes and all that technical debt, complexity and loss in decentralization could be avoided by simply increasing the block size. BCH for example has zero-conf transactions and the average fee is also <$0.01.
But that would mean that you’d be able to use it as an actual means of exchange instead of this crippled “Internet gold” bastardization that BTC has become.
Yeah the fact that all the tipping is done off-chain via the lightning network is even more of a turn off. Did anyone else follow all that drama back on reddit?
Is abliteration based off the research by the Anthropic team? When they got Claude to say it was the golden gate bridge?
Well first off swarm doesn’t work with environment variables, so if you pass any in you’re going to need to pipe the output of docker compose read into docker swarm service create.
Your port settings are gonna give it a problem too, swarm doesn’t support that new syntax, and as a result you can only assign a single network interface to a service.
Regarding networking, since the whole paradigm is that you’re not defining a single container but a service that can live/move across multiple nodes; any traffic to any node in your swarm will be routed (round robin style) across the copies of that service. (This makes logging setup a PITA, ask me how I know!)
Bind mounts aren’t recommended, volumes are preferred. Otherwise everything needs to be mirrored across all nodes, depends on the use case.
That being said I’m not convinced that swarm is the right answer here, I concur with @talentedkiwi@sh.itjust.works. You should just install pangolin on your second machine.