Nothing wrong with having a key pair, but yeah, most of the content in Nostr is unfortunately cryptocurrency related.

You’re not wrong, but the oil and gas industry, and generations of families have made livings on it, and our resulting current world status and wealth is largely founded upon it.

It’s a problem; you can hate the problem, but ignoring it isn’t a solution, and it’s cost Democrats elections. This isn’t a handful of Klansmen; it’s an entire industry. The supply chain employs nearly 10M people in the US. Telling then you fuck off, relocate, and find different jobs doesn’t win any votes.

I was wondering if this was a pre-Thagomizer comic, or just a missed chance at self-reference.

Service was terrible when I went, too, and talk about dirty; the place must have been covered in like, 6 pes of dust, no joke!

Caffeine works. Melatonin has never done anything for me; maybe I’m immune, but I’ve put it in the same mental basket as homeopathy.

Well, duh. Anyone who didn’t know this hasn’t been paying attention. He’s (Trump) said as much, himself.

Yeah, despite the strong anti-crypto sentiment on Lemmy, this is exactly the problem that projects like Nostr is trying to solve by integrating Lighting as a first-class payment system in the ecosystem.

Services get paid for by one of four ways:

• Harvesting and reselling of user data. Which is wildly unpopular, and why a lot of people are on Lemmy and not Reddit or Facebook.
• Ads. Which is also unpopular and again why people come to services like Lemmy
• Pay-for-service, which is what you’re suggesting, only via crypto, which is easier than accepting credit card transactions, and safer for users.
• The hosted paying for it out of the goodness of their hearts. So, charity. Sometimes there’s corporate charity, and that’s nice, except for the potential for money coming with strings attached, now or eventually.

Someone always pays; its expensive to host a popular instance. People suggesting you should host for free are selfish freeloaders, so know that some people understand that hosting costs, and sympathize with with your desire to offset that cost.

I like the volunteer micro-transaction model. Those who can afford to pay some amount for good service, and hopefully this provides welfare for those who can’t afford to pay. But the cryptocurrency space is a mess at the moment, and an economical currency (probably proof-of-stake rather than proof-of-work) needs to gain some traction, and overcome a lot of ignorant bigotry.

Someone else pointed out that they blocked the fracking bill.

However, this is a tough topic for Dems, and it’s one of the reasons the Teamsters haven’t endorsed them; one of the reasons is because industries like fracking provides well-paying blue-collar jobs.

Remember, back in 2016, when Hillary said at a rally that if she was elected they were going to shut down the coal industry? That was a “they said the quiet part out loud” moment for blue-collar industry, and while it’s too much blame to lay on Hillary, it really did drive another nail in the coffin of blue-collar support for Democrats, which they’re still struggling to recover.

Democrats have two conflicting goals: support blue collar jobs, and stop environmental destruction. Actions like this benefit the environment, but cost them votes and the support of Unions.

It’s a catch-22. Biden did a fantastic thing showing up at that picket line, but there’s a long way to go to recover those blue-collar votes.

I like to internalize this as a victory, and the utter humiliation of the person who offended me. They said “Sorry.” That’s admitting defeat!

Status represented by hat size?

I agree. I do appreciate the spirit of OP’s comment, that we are agents. I observe a lot of people who blame everything but themselves for their circumstances, and take responsibility for nothing.

However, sometimes you get the meteorite, and sometimes the meteorite gets you; we’re none of us 100% in control of our fates.

To be fair, it is a very long-winded post. I think it’s not an uncommon use case, though, and so deserved a robust sketch of the desired solution; Farmville and chat are sideshows, and what the people left on Facebook are really there for are the Walls.

Compiling has never been the hard part. The challenge is making it through the entire configuration menu system before succumbing to the urge to gouge your own eyes out with blunt sticks.

Once that’s done, kick off make take a long break; it’ll be compiled by the time you get back to it.

I hear build times are getting longer with the Rust parts, though, so do it soon before you need mainframe access to get a compile within your lifetime.

There are some excellent apps out there, and by and large they look and work better than commercial apps, IME. So I disagree with the assertion that I have to stay with commercial software.

What I was asking for, in my post, was not which apps have better UX than Facebook, but rather which of the very many OSS, federated (although, not necessary for my use case), self-hosted platforms fit the specific use, and ideally with a straightforward iOS mobile app. Doesn’t have to be pretty; just has to be able to quickly take and post photos to a private channel/community/wall.

Circles really is quite nice in all respects. I think they’re hindered by their choice of backend. I’ve been using Matrix for years, and key management has always been a hot mess. I wouldn’t be surprised if the issues we encountered were related to Matrix’s god-awful and buggy PK negotiation & management process.

The AMD graphics driver is reputedly the biggest that mainstream Linux users will encounter, approaching six million lines of code.

That does seem a bit … excessive.

I stub my toe. Is that a “have to?”

That’s a lot of phaelenopsis.

It’s true some things are harder to do in the container configuration; it’s easier installed as an OS, especially integrations like Z-Wave, ZigBee, RTSP, Eufy, ESP, and so on. All of these require running other software, and in containers it’s a fair bit of fussing with port and host OS device connections.

I’ve always run it in a container, without issue. It works fine, but I’m comfortable with the command line and LXC. That said, flashing an ESP hardware device and getting it connected to HA running in a container has so far defeated me, because I have to give access to the device in the configuration of the container before I run it, but the device flashing process itself is time limited and expects a process to be waiting on it when it is connected. It’s a chicken/egg problem I haven’t yet figured out which wouldn’t be a problem if I were running the HA OS.

HA isn’t the only software that just works better when it controls the while OS. Kodi is another that encourages users heavily to running it as an OS.

Regardless, it runs fine via

podman pull ghcr.io/home-assistant/home-assistant: latest

and there’s a package in AUR that wraps the container up with a systemd service - it’s as close to a bare package install as you’re likely to get.

What’s a little funny to me is that, despite that I’ve been running HA in a container for the past 4 years, I’m working towards getting a dedicated device and running HA OS on it. If we ever move out of this house, I’m not going to spend weeks going around replacing all of the hardware - smart sockets, lights, garage door opener, security, etc etc - with dumb devices; and for any of that to be worth anything, it’s going to need a controller configured for it, which means, I’m planning on selling the HA server device with the house. For that case, I don’t want anything but HA running on that device, and for that, it’d just be easier and smoother to run HAOS.

My advice is to run HA in a container until you are sure that’s the direction you want to go, but not for so long that it’s going to be a PITA to migrate to a dedicated server. But - hey, just IMHO - plan on running HAOS. If I knew then what I know now, that’s what I would have done.

It looks utterly repulsive, but I kind of love the idea… the sheer convenience.

Right? Late 18th / early 19th century surgery was almost more dangerous than the wounds.