Bilbo Baggins

I assumed it was intentional.

I never thought of Sin City being different in that way. But it is. Whole sections are just the current character talking to themselves.

I hated the Mule in the books. Wrecked the books from that point on in my opinion. But, loved everything in foundation before that.

Every instance just needs to store the communities they use, just like now. But once cached, any other instance could grab those messages from any of those instances. It’d be a peer to peer sort of organization.

I can think of lots of caveats regarding freshness of content and trust and ensuring the tree of instances is auto organized to minimize depth. Maybe for trust you could have signatures for all content signed using keys that every instance could pull from the original instance just once every now and then.

Upvotes and responses would just travel up the tree in the reverse trip from the way content came down.

But, I think it’s similar to other things that already exist. These problems seem solvable.

If it worked like torrenting where you have seeds, etc, it’d scale almost infinitely. I don’t think we should change to fit the algorithm. We should change the algorithm to make it scale.

I noticed that occasionally. I just assumed it differed based on the instance of the post or something. My Lemmy experience has been a lot better since I switched away from lemmy.world. Used to have crashes but haven’t crashed since switching.But, lots of stuff is changing, so maybe it was something else.

The Connect client can hide posts based on keywords. I switched from Jerboa purely for that one feature.

In summary, for our mental health, delete nextdoor and never look at national news. One is populated by busybodies and the other is just cancer.

We actually do own the airspace over our houses. Not as high as planes or space, but a drone probably would from my skimming of this article.

https://www.google.com/amp/s/aviation.uslegal.com/ownership-of-airspace-over-property/%3Famp

I hope you’re wrong. If there’s one job I want AI to do, it’s to improve health care.

There are many excellent doctors, but also many very average doctors. And even the best doctors seem to be biased towards the most common illnesses.

And I’ve read that many people with persistent pain, especially people of color, cannot get medicine because doctors suspect everyone of being abusers. But, giving it out like candy isn’t great either.

We need AI doctors.

Optoma GT1090HDR

I’m pretty happy with it, although it doesn’t do 4k. But, it’s super bright at 4200 lumens.

You’re right, although if you ever get the chance to browse a real physical encyclopedia, it’s a unique experience.

Not practical, but it’s a bit like playing a record or playing a game on a real NES. It’s a unique experience.

I have a full 2007 set of Encyclopedia Brittanica in the same room as my vintage computer collection. I browse it occasionally.

Projector beating is a bold claim! I doubt I’ll ever get a big TV again. The idea of trying to move a 98" TV up the stairs seems crazy. I’ve got my 120" retractable projection screen and I’m happy.

Totally agree about the amount of coordination overhead. That is a huge amount of time to do anything.

But even so, it’s even slower, by a lot, once you pull the ripcord and need to keep the site working while you update it.

Prior to release you don’t need to have branch and release then QA then deploy. You can just modify schemas and drop existing user data without needing to migrate anything. You can change the look of the interface without angering users who generally hate change.

Just the cycle of releasing new features carefully is a ton of overhead.

I’ve spent entire days just rolling out code to change which domain name is used to refer to some images because doing it quickly would overwhelm the image servers due to the caches being unpopulated. 100% of that would be unnecessary prior to going live.

Honestly, most dev effort at big companies goes into ensuring nothing breaks or slows performance. When news articles are written about your mistakes, most developers and managers try not to break things.

Making new stuff happens, but it just can’t happen as fast as at small companies where 90% uptime is good enough.

That said, it doesn’t excuse launching products half baked. No reason an unlaunched product can’t be iterated on quickly during dev.