Show HN: Florida HOAs are stealing homes
5 by lovewins | 0 comments on Hacker News.
Hack Nux
Watch the number of websites being hacked today, one by one on a page, increasing in real time.
New Show Hacker News story: Show HN: Keep your eyes in one place while typing
Show HN: Keep your eyes in one place while typing
2 by willthefirst | 0 comments on Hacker News.
I wanted a way of typing that's tuned towards stream of consciousness/get down a bunch of words quickly. And I'm too lazy to move my eyes, so I wanted something where I could relax my eyes/brain and just get words out.
2 by willthefirst | 0 comments on Hacker News.
I wanted a way of typing that's tuned towards stream of consciousness/get down a bunch of words quickly. And I'm too lazy to move my eyes, so I wanted something where I could relax my eyes/brain and just get words out.
New ask Hacker News story: Tell HN: ChatGPT on macOS grants local computer access to cloud account
Tell HN: ChatGPT on macOS grants local computer access to cloud account
4 by lxgr | 0 comments on Hacker News.
I recently started a conversation on ChatGPT for macOS in "Work" mode with the "In the Cloud" execution option enabled. I was expecting this to run on a cloud VM, just like "Work" conversations started on chatgpt.com When I continued it in the browser (e.g. via right clicking it on macOS and then selecting "Open on chatgpt.com"), I was pretty shocked to learn that it actually had (and still has) access to my local file system. I could just prompt it to list files in my home directory, in /Applications etc. I never have opted into this behavior in the macOS app, nor does there seem to be any way to deactivate it. It's somewhat documented for enterprise accounts [1], and it can be deactivated for those in the admin panel, but this seems like the wrong place: Why should this be possible to activate remotely? Can anybody confirm this behavior? Maybe I'm missing something, but this seems pretty concerning. [1] https://ift.tt/5PeUoKm
4 by lxgr | 0 comments on Hacker News.
I recently started a conversation on ChatGPT for macOS in "Work" mode with the "In the Cloud" execution option enabled. I was expecting this to run on a cloud VM, just like "Work" conversations started on chatgpt.com When I continued it in the browser (e.g. via right clicking it on macOS and then selecting "Open on chatgpt.com"), I was pretty shocked to learn that it actually had (and still has) access to my local file system. I could just prompt it to list files in my home directory, in /Applications etc. I never have opted into this behavior in the macOS app, nor does there seem to be any way to deactivate it. It's somewhat documented for enterprise accounts [1], and it can be deactivated for those in the admin panel, but this seems like the wrong place: Why should this be possible to activate remotely? Can anybody confirm this behavior? Maybe I'm missing something, but this seems pretty concerning. [1] https://ift.tt/5PeUoKm
New Show Hacker News story: Show HN: Chkit – Schema, migrations and backfills for ClickHouse (like Drizzle)
Show HN: Chkit – Schema, migrations and backfills for ClickHouse (like Drizzle)
4 by keks0r | 0 comments on Hacker News.
Hey HN, im Marc, co-founder of ObsessionDB. We are open sourcing ChKit, our tooling to manage schemas, migrations and backfills for clickhouse. I am a big fan of the type safety drizzle provides for the database. Manage the schema in typescript and generate migrations from it is a powerful workflow. I always wished something like it would exist for clickhouse, so we could manage our analytical workloads the same way. It didn't exist, so we build it. We build it after running ClickHouse at petabyte scale in our previous company, were we managed hundreds of tables, MVs and endpoints reading from them. The way it works: 1. You define your schema in typescript, with typed helpers for tables, mv, column types etc.. 2. You generate the migration, that contains the DDL, to get your clickhouse instance from status quo to what your current typescript schema defines 3. Your CI can check for drift 4. You run the generated migration against production 5. You use the defined types in your code, to ingest your data while making sure it has the correct type. Bonus: if your schema change was BC breaking, we generate the sequence on how to backfill the data, into the intermediate table to migrate (this is quite the hard problem with large tables and schema evolution) In case you have already a clickhouse instance with a schema, you can pull it down and start using ChKit from where you are. Run our generator to setup the boilerplate: npm create chkit@latest If you folks are running clickhouse in production, I am curious to hear what other challenges you are running into.
4 by keks0r | 0 comments on Hacker News.
Hey HN, im Marc, co-founder of ObsessionDB. We are open sourcing ChKit, our tooling to manage schemas, migrations and backfills for clickhouse. I am a big fan of the type safety drizzle provides for the database. Manage the schema in typescript and generate migrations from it is a powerful workflow. I always wished something like it would exist for clickhouse, so we could manage our analytical workloads the same way. It didn't exist, so we build it. We build it after running ClickHouse at petabyte scale in our previous company, were we managed hundreds of tables, MVs and endpoints reading from them. The way it works: 1. You define your schema in typescript, with typed helpers for tables, mv, column types etc.. 2. You generate the migration, that contains the DDL, to get your clickhouse instance from status quo to what your current typescript schema defines 3. Your CI can check for drift 4. You run the generated migration against production 5. You use the defined types in your code, to ingest your data while making sure it has the correct type. Bonus: if your schema change was BC breaking, we generate the sequence on how to backfill the data, into the intermediate table to migrate (this is quite the hard problem with large tables and schema evolution) In case you have already a clickhouse instance with a schema, you can pull it down and start using ChKit from where you are. Run our generator to setup the boilerplate: npm create chkit@latest If you folks are running clickhouse in production, I am curious to hear what other challenges you are running into.