jfkw

The idea never made sense to me, the car couldn't earn enough money to overcome the hassle and risk. I would never let random strangers ride in a car I owned without supervision. There would be a daily mess to clean up, often damage. What happens when a passenger does something that gets the car and owner caught up in civil forfeiture laws?

I was hopeful this would be minimalist, secured contacts version of general purpose OS used in more powerful smartwatches. Regular phone and message apps, parent-limited contacts, communications logged where the parent can review/block it.

We are currently sharing a Verizon Gizmo 3 among multiple children. The GizmoHub app is not bad but its mandatory use is frustrating. Friends need substantial parental help to start communicating with the Gizmo user (account creation with Verizon). Forcing all communications through a dedicated and clunky app is a non-starter.

Battery life is the other challenge. Kids don't heed advice to conserve the less than all day battery life. Later when communications for pick-up are most needed, the watch is often low on power.

I couldn't figure out what software is being developed to pass the sqllogittest suite here. Will this be a SQLite-like database or SQL parser implemented Zig?

Glad to see Lichess mentioned here. I have been trying without success to log in or password reset using a Gmail account. Messages from Lichess never seem to be delivered to Gmail, even to the Spam folder. Short of creating a throwaway account to access the forums, is there any alternate way to contact Lichess admins to ask if this is a known issue?

Does jpm have an option install packages to a local environment (virtualenv)?

I've never understood what motivated financial institutions to grant Mint access to account transactions and balances? Did pre-acquisition Mint somehow reach a tipping point in active users where financial institutions decided their customers would choose other banks if theirs wasn't accessible through Mint?

Are there other competing tools that have similar reach connecting to financial institution accounts?

Of all the free services to kill, this one really hurts. I just got my parents migrated to using Cloud Print with their Chromebooks and iStuff. As I am providing the usual family-plan IT advice from several timezones away, Cloud Print solved the biggest headache of getting their current project printed to their house or office from wherever they are (or me, if I am helping them). Supporting local printers was a time sink, and remote printing is the logical complement to cloud applications. It seems shortsighted to give it up when there is no real competition in this space AFAICT.

From the article "... To make GitLab better faster, we need more data on how users are using GitLab. SaaS telemetry products, which provide analytics on user behavior inside web-based applications, have come a long way in the past few years. They are an important tool for rapidly improving user experiences because you can understand what users are doing (or not doing) in the app. GitLab has a lot of features, and a lot of users, and it is time that we use telemetry to get the data we need for our product managers to improve the experience."

This doesn't seem like a sufficiently good justification add telemetry features which some users may find objectionable.

Perhaps those resources would be better spent on a feature that let the user who is annoyed by a slow operation to:

- Begin recording user interaction telemetry locally - Perform the slow or buggy operation - Stop recording, generating a data bundle file. - Allow the user to review the data bundle in human-readable format - Optionally take the data bundle to a less secured system as needed - Submit the data bundle to GitLab engineering as a well-filed issue

Done that way, I think most users would welcome the interaction with Gitlab. For telemetry, not so much.

I also favor issue tracking integrated with the source code and experimented with most of these systems. The first roadblock I noticed to using distributed issue trackers was that the client programs need to be extremely convenient to install on the personal OS and mobile device of everyone involved in the project, something which is very difficult to deliver. A web interface with editing capability could cover some cases, but then you're obliged to host it on a server somewhere.