My take, is that this effect has removed a lot of the micro communications we make - not necessarily random conversations. It’s taken away random moments that may trigger a short small conversation with strangers.
In part it’s taking away the shared experience in public and making it “my” experience.
Singapore to a tea. Spooky that I had a similar path, Sydney -> HK -> New York -> Singapore. Crescendo-ing up to New York, then off a cliff into a full blow school-like world (but great trains).
Super strange when there are several on the front page, older, with less votes and less comments. To say it’s off topic is a little narrow minded given the current environment
Anecdata- I did this as a 13 year old in the 90s. My old man came upon it after I was repeatedly ending up in hospital in Australia with asthma as a kid. I think there was a presentation in a local scout hall!
I didn’t understand the history at the time - but it stopped me going to hospital, I ended up being able to do a controlled hold (no discomfort) of around 1:30 min and a max hold of just shy of 5 mins.
So for me it had a big impact.
I stopped in my 20s and now I am no where near able to get those numbers.
"DuckDB offers robust capabilities for querying data stored partially on S3, particularly when dealing with Parquet files. This is achieved through several optimization techniques:
Predicate Pushdown: When you apply a WHERE clause to filter data, DuckDB can "push down" this filter directly into the Parquet file scan. If the Parquet file contains zonemaps (metadata about value ranges within columns), DuckDB can use this information to skip reading entire sections of the file that do not contain relevant data, significantly reducing the amount of data transferred from S3.
Projection Pushdown: When you select only specific columns in your SELECT statement, DuckDB automatically reads only those required columns from the Parquet file. This means you avoid downloading and processing unnecessary data, leading to faster queries and reduced S3 transfer costs.
HTTP Range Reads: DuckDB leverages HTTP range headers when interacting with S3 (or other object storage supporting range reads). This allows it to fetch only the necessary parts of the Parquet file, such as metadata or specific column chunks, rather than downloading the entire file."
started with overland (was great, but hurt the battery a lot) - there was an iOS app for it. I then just moved on to PSObserver as it was self contained, I could export off my phone. I also augmented with running google maps background for a few years as well. Think I have over 5m data points now. I user Kepler.gl originally + with iPhone photos as well overlayed.
Don’t know if you have seen the work DuckDB is doing on ducklake. Maybe there is an overlap in vision for versioning data across multiple data sources - and similar to SQLite it’s not proprietary and easily drilled down on. I’m sorry, don’t have technical knowledge :/
Working on an AI/Governance and compliance system that also integrates with the cli for teams developing the actual code and the systems that are commonly used, GitHub, bitbucket, open policy agent, collibra etc..
Used by enterprises for compliance, reporting and answering questions like, who owns this ai model, whats the monitoring plans, where is it running, what approvals does it have, what policies are applicable (geographic etc).
I use them too for similar uses. Brilliant. I also use zero AI. I don’t care. I totally understand ppl not buying them because they are meta. I get it.
Been using iPhone for years and I swear the keyboards accuracy has turned to absolute shit. I am convinced through my experience that they have definitely changed something and made it terrible. It’s making me consider getting an android cos that’s how we use our phones - with a keyboard.
In part it’s taking away the shared experience in public and making it “my” experience.