I assume end to end encryption would help mitigate this. Breaking E2E encryption would require a client side update that could be hard to implement if the company has already gone belly up.
Probably, business-as-usual systems and policies make it harder for anyone to argue the "debtor in possession" [0] violated their fiduciary duty to do their best to ensure creditors get paid.
In other words, having a "smash glass in case of insolvency" button might do the job of protecting customers, but a judge could decide it looks too much like a shopkeeper screaming "if I can't have it nobody can" before lighting everything valuable on fire.
I admit that vibe coding was kind of a clickbaity way to frame this, but I couldn't think of a better way to describe it. That might just underscore my ignorance in this domain.
One problem I personally have here is that I write code as a way to reason through and think about a problem. It's hard for me to grasp the best solution in a space until I try some things out first.
Here’s another question. Has anyone been able to get an agent to produce reliable high quality code?
My first experience with it was a year ago and the tests it produced were so horrendously hard to maintain that I kinda gave up, but I imagine that things have gotten a lot better in the last year.
It's a cross platform productivity app that lets you block apps, websites and games until you reach a set of verifiable goals such as walking 10,000 steps, physically going to the gym or finishing all your tasks on your to-do list.
I just finished the Android version a few weeks ago!
There was a project at Ansible that aimed to address this kinda thing when I worked there. The idea was to write policy as code definitions that would prevent users (or AI) from running certain types of automation. I don’t know where that project ended up but reading about this makes me think that they were on to something.
I would also love to hear what kinds of plugins the HN Community would like to see. At the moment I'm thinking about the following:
- Github: this would allow you to set goals based on reviewing PRs, closing tickets, reading GH notifications etc.
- Homelab/Zapier/IFTTT: this would allow some kind of funny things like turning off lights or locking locks if you don't complete your goals. I don't have any smarthome stuff, so this would be hard for me to personally build.
- Notion/Obsidian/Jira/Trello
- Google/Apple Calendar: this could help people focus on meetings instead of (for example) scrolling HN
I wonder if you could set it as a sensor for Home Assistant, then we could build our own smart home automations outside of the app instead of you needing to do anything.
I was thinking about ways for the app to receive webhooks, but being able to send webhooks is an even better idea! I'm going to start writing down some thoughts for creating generic webhook triggers. That should also work for zapier (and possibly IFTTT) as well.
I'm working on something like this for Android. My goal is to build a system where plugins can selectively block parts of apps based on a set of rules. I can't promise that this will end up making it into the final version because the Android documentation states that the accessibility APIs may only be used for accessibility tools, but it's what all of the other app blockers on android do so fingers crossed they let me do it as well.
This would also be possible for desktop, since I'm using browser plugins to block websites on Desktop at the moment. I don't think that this is possible on iOS, but there may be APIs that could enable something like it that I'm not aware of. As much as I like Apple's commitment to privacy, the way that they've locked down a lot of their APIs has been a real thorn in my side for enabling some of these more advanced use cases.
At the moment pretty much everything automatically resets at midnight, including any timers. It's not an issue for me since I rarely stay up past midnight, but I did notice one problem where my step goal reset on New Years eve and I wasn't able to watch my sleep videos on youtube because of it, so I'd like to find a way to make this more configurable.
I would LOVE to be able to open source this project at some point, but I also want to be able to make a living off of maintaining it. I've been reading up on some source available licenses such as Polyform, which can contain clauses that trigger the code to go open source at some point. If I get some traction, I'd really like to make a similar commitment where we will open source this in X months/years. Does anyone have experience with this sort of thing? Is this a good idea?
I'm a former Red Hatter, so I'm all too familiar with the revenue hits a product can take when they go open source, but I have no ambition to turn this into a big business, so I think that should be acceptable (unless revenue dips to zero).
reply