🌸🌹2ck 🌱🐇 @2ck@social.cleverlibre.org

https://www.nasa.gov/feature/jpl/seeing-nasa-s-ingenuity-mars-helicopter-fly-in-3d
#nasa #mars #NASAIngenuity

@georgios disambiguation of author names. It's somewhat better with ORCID and tools like research gate, but not every index recognizes ORCIDs and not every one has one (and might have more than one, which is also a problem)

@normandc
I did read the product page. I didn't use the word "consumer". I understand that it's a community project (and that many people in that community are on Mastodon). On Masto, I'm seeing a lot of folks talking like Pinephone is a useable smartphone ("daily driver"), but having now used it, I'd say it's pretty far off the mark. Maybe the Pinephone is just meant to stay as a community project for computer geeks like us to tinker with: that's fine.
@jawsh @linmob

@jawsh I wasn't able to use the SMS app, KDE Connect SMS, to send text messages. That's the biggest. The contacts app doesn't pull my SIM card contacts. The screen sleep settings aren't effective - the screen just turns off while I'm using the phone. The screen doesn't reliably turn on when I press the power button.
There are other first-boot issues I wrote down
@linmob

@jawsh I wasn't expecting a showstopper, but it's really lacking functionality that I'd consider basic for a smartphone product. It makes me wonder who managed product design and testing - do they not have enough issues already to keep devs busy for a while that they need to farm more issues from customers?
@linmob

@ivanrancic no, seriously: I'd like to know what makes it the best in your eyes.

As a usable product, it falls flat in several ways. It couldn't read my SIM card's contacts. The UI is laggy. Touch screen has too much friction. Remaining charge estimation is unstable (moves up and down without charging the phone). Temperature control seems insufficient: the phone heats up when I'm doing hardly anything. Several of the default apps are, as admitted on the wiki, are either partially implementing features or only stubbing them out.

I think several issues can be resolved with a more polished OS. Yes, I can install a different OS, but Pine64 *chose* the OS to put on as a default, so I would hope the picked the best they could find/build for the hardware: If not, then WTF are they thinking?

@ivanrancic best on what metrics?

Calling #pinephone "beta" is really generous. It would be a crap smartphone for 8 years ago.

@izaya
You mean like:
Did Dillon say, "I walked to the store?"
vs
Did Dillon say, "I walked to the store"?
Honestly, I do the second since leaving school, but I think the first is what my high school English teacher wants me to do.

@trinsec BSL is *very* different from ASL, I'm finding out

@trinsec ah, cool. Yeah that makes sense. The emoji suggests the ASL sign for "deaf person" (https://www.handspeak.com/word/search/index.php?id=539 (handspeak.com is a really cool resource for me, learning ASL)). I'd like to learn other sign languages, buuut I'm having enough challenge just learning one. Do you know multiple sign languages? I'm curious how much overlap there is, practically.

I just realized there's a deaf person emoji 🧏. I never noticed it before since I didn't know the sign for "deaf person".

Google Warranty:
> If there are any differences between this online Limited Warranty and the Limited Warranty included in the box with your product then this online Limited Warranty will supersede the terms of your in-the-box warranty.

Is there a good reason for this from a customer perspective? It seems to me like Google could just change the warranty terms arbitrarily after sale.

@Canageek@cybre.space @tindall@cybre.space Is there actually a problem or just a potential problem though? I haven't had much exposure to radio standards development, but no one wants that, so if it's known it would be a problem, wouldn't manufacturers be required to build non-interfering transceivers?