Well, you see, that would fall under the “well regulated” part of the 2A which always seems to be ignored.
Even worse, the fancy smart display doesn’t even have to physically break to become inoperable.
Most smart devices connect and are locked to a single company’s servers and become e-waste the moment they decide to pull the plug.
If you’re lucky, you or a techy friend can flash an open firmware to them, but that’s not always possible.
If you meant instance admins, is there any particular customization? Mine has a unique name but the PWA still created the launcher as “Lemmy”
I’m assuming that’s coming from a static value in the served manifest.json but I haven’t really investigated or thought about the launcher name until you mentioned it.
I joined, but I’m definitely going to be a lurker. It’s not a hobby I ever got into, but I enjoy seeing other people show off their work.
It might be shocking to hear, but most places could have nice things like this if the majority of people would get out and vote. I could not be happier for Minnesotans.
I work in IT, and Jurassic Park (novel) was a big influence.
Basically it taught me to not assume any system or process is infallible and to always expect the unexpected.
I’m pretty sure the slip started back in 1954 when ‘under god’ was added to the pledge of allegiance. We’ve managed to keep it mostly limited to that until relatively recently, but their foot has been in the door for decades.
To expand on that, I do a join between the local_user
and person
tables so I can grab the name and display names for the local users:
select
p.name,
p.display_name,
a.person_id,
a.email,
a.email_verified,
a.accepted_application
from
local_user a,
person p
where
a.person_id = p.id;
Do you run your own Firefox sync service or use Mozilla’s?
I’ve wanted to set my own sync up but never got around to it. The few times I’ve skimmed over the setup process, it looked pretty rough.
I just used the Docker logging options to cap the stdout/stderr log to a reasonable size. Just add logging
options to each chatty service and change 25m
to whatever makes sense for your environment.
docker-compose.yml
:
services:
....
lemmy:
...
logging:
options:
max-size: 25m
pictrs:
...
logging:
options:
max-size: 25m
Yeah, for sure. Even though I disagree with it, I understand it (despire her seemingly going for the nuclear option).
It’s an apartment complex which likely is already a no-smoking environment. Logically speaking, cannabis smoke shouldn’t get an exception. The order just seems to prohibit the man from smoking, so I assume other methods are still on the table.
Pretty much everyone I know with a medical card uses a vaporizer. Little to no smell and much easier on the lungs. That, or edibles.
I feel like there’s got to be a middle ground between, “I don’t want to smell this” and getting a court order to stop someone from taking their medicine in their own home.
I found this post, and it was useful.
I’d heard about Lemmy a good while back, but there wasn’t much interest in it until the Reddit API kerfuffle.
I really like the concept of federated social networks and breaking free of the big tech rage-baiting algorithms. Just give me a list of topics I can follow and let me sort and filter them how I want. Don’t suggest or recommend things to me, especially if they’re designed to make me angry just for sake of engagement.
Lemmy seems like it has a lot of potential in that regard, and I’m hopeful it’s able to build a respectful user base. I’m primarily here to feel out the landscape and be the change I hope to see in the world.
For #3, as far as the instance lists and the Lemmy Community Browser are concerned, I believe a 301 redirect should work as long as it redirects with the URI. e.g. old.lemmy.tld/c/Hangout -> new.lemmy.tld/c/Hangout . Eventually my new instance will be picked up by those, but I’m still not sure if/when my old instance would drop off (see question #1)
That would allow anyone clicking into my old instance from any of the currently published instance lists to land on the new domain. But I’m not sure how currently federated instances would handle that.