There are a lot of instances where the Enterprise crew wanted to do the ethical thing, and Picard stops it or tries to. For example, when Dr. Crusher wanted to help when that planet population was addicted to drugs, and Picard wouldn't let her do that or communicate anything to them.
Also, Data once found humans frozen in space, and when he helped them, Picard was annoyed; it wasn't even a Prime Directive issue!
I wonder why they're doing this.
I was really looking forward to the Balmuda phone, but it also disappeared from the market https://arstechnica.com/gadgets/2021/11/meet-this-unique-compact-android-phone-from-a-japanese-toaster-company/
I'd like to see a more ergonomic phone; it's time to evolve from just a thin slab.
So what is this made of if not lithium?
The one that irrationally bugged me was when Tripp told the captain that he lowered the chair by 1cm, and the chair was still too high for everyone who sat there.. I know it's not supposed to be noticable but I could tell somehow that it wasn't lowered at all
This is a Kendall Roy move.
Warrants are required for U.S. Mail. Likewise, the government should not have warrantless access to all electronic communication. It's an outrageous position.
The Xbox 360 remake is awesome. Sadly, it is not available for purchase or backwards compatibility, as the publisher dissolved.
Anyway, I recommend this trailer: https://youtu.be/6pDy-CSFsPs
I really don't even think the votes table would need to itself be federated; it could just be on the user's instance. Upvote/downvote would be a call, but it should really only require the post or comment ID and voter instance. If an instance spams votes, those upvotes/downvotes could be deleted and the instance defederated
There might be possible technical solutions to this using hashing. Hashing is like encryption in that the original cannot be extracted, but the hashed result is unique.
For example, a solution would be to have a VOTES table with an indexed column that is a hash of a combination of the user ID, post ID, (and perhaps another "salt", not sure). When a vote is made, the VOTES table is checked that the record (vote) does not already exist, gets an insert, and then a COUNTER is triggered for the actual vote count. (COUNTER is a db command that simply updates a counter). The hash would prevent multiple votes from the same user (as the salted hash is unique), and it would also prevent identifying who the user is from the table.
I returned a Gameboy Micro. I really want one now and I could have just kept mine from back then
Not just a small phone, but an ergonomically shaped phone is missing from the market. It would be great to have devices again that you can cradle in your hand and slip into a small pocket. Thin slabs are nice on a display shelf, but they aren't human-centered. Give me a phone with a curved and grippy back and a 5.x inch display.