Readit NewsHighly recommend for any graphics programmer that might think dithering is unnecessary or simply a "aesthetic choice".
Location is only used, in context, to help find healthy meals near you. (You can use the app with or without enabling this location-based feature; if you don't use it, then we don't ask for location.)
Where are you seeing messages? We don't track messages, so this is probably a mistake in our metadata.
Sorry for being pessimistic, it's just whenever I see a health related app I immediately look at the data collected and data shared sections and get concerned. Especially if it's being shared with insurance companies.
Quick edit: That "messages" part might be only in-app ones. Google does not word that well in the summary.
Trying to get that stuff resolved was such a pain that I eventually had to ask a friend who knew someone that worked at Google for assistance. Their support team had absolutely no public contact info available. I eventually managed to get my data and migrate the services I actually use (Google Fi and Youtube) to a non-workspace account.
The funny thing is that a few months later they tried to send a $60 bill to collections because they reopened the account for 2 days for me to migrate things off. I was originally going to pay it to just get them off my back, but Google's own collections agency wouldn't let me pay through card or check or anything. The only way I could pay was to "Log into your Google Workspace account" which NO LONGER EXISTED.
Now it's just an amusing story about incompetence to look back on, but at the time it was stressful because I almost lost my domains, cell phone number, and email addresses all at once. Now I never trust anything to a single company.
Maybe it's my fault for not making it to page 1357 (!) of the datasheet, where the issue is described as "RP2350-E9".
https://datasheets.raspberrypi.com/rp2350/rp2350-datasheet.p...
They don't work at all? How the heck did something that important get past testing?
Guess I'm not moving on from the RP2040 anytime soon...
https://m.youtube.com/watch?v=XKFwO4iMIgM&t=51s
It’s a great device and I wish people would be a little more open to taking the plunge with it. Forget boox—-you won’t be able to properly root it, they disrespect and even stole FOSS. Meanwhile, remarkable is cool, but anemic hardware compared to Pinenote.
Thank you for sharing this with me. This is the first time I've seen the `rnote` app on an E-ink device. I'm quite surprised in how functional it looks, though I can already tell the latency is quite high.
I'm definitely going to keep my eye on this device though. I think it will just be a few more years before the software has caught up with the hardware.
The fact that GNOME works well on typical tablets isn't really relevant here. The PineNote is an E-ink device with very specific hardware constraints and use cases. It's primarily meant for reading and writing, and these tasks require software specifically optimized for E-ink displays and low-power operation.
I've personally experimented with desktop environments like XFCE and i3 on a reMarkable 2. While it was an interesting technical exercise, the experience wasn't practical for daily use. For comparison, look at the reMarkable's unofficial/hacked ecosystem (https://github.com/reHackable/awesome-reMarkable) - it's full of applications and utilities specifically designed for E-ink displays and writing/reading workflows.
This is why I'm hesitant about the "community device" designation. Simply saying "it runs GNOME" doesn't tell us anything about the actual user experience for reading and writing on E-ink. To be clear, my concern isn't that it runs GNOME - it's that this seems to be the only information available about the software experience.
Does anyone have any information on the OS being developed looks like? I have not been able to find any videos or screenshots that indicate what interacting with the device is expected to look like. I found this blog post here, but it shows it running a GNOME environment which is... Not at all what I would hope for in this type of device: https://pine64.org/2024/10/02/september_2024/#pinenote
On Monday, we launched Determinate Nix to help make this promise more real: https://determinate.systems/posts/announcing-determinate-nix.... Note: Determinate Nix is not a fork, it is a downstream. Our plan, and intent, is to keep all our patches sent to the upstream project first.
And what happens if the Nix community doesn't pull those patches, and instead goes with a different solution? Will your downstream adapt to the upstream project, possibly breaking things for your customers?
Are there any actual services like this that work properly? I've noticed whenever it indicated that a service has removed my data, that same service would come back online as having my data a few weeks later.