1,346 karma · joined May 9, 2012
I agree that the price is the barrier. If it was around $1k I would MAYBE think about buying one. I'm curious to see what the newer Valve headset retails at, even though that's more for play than for work.
> When performing his work as an undercover agent, Arctor goes by the name "Fred" and wears a "scramble suit" that conceals his identity from other officers. Then he is able to sit in a police facility and observe his housemates through "holo-scanners", audio-visual surveillance devices that are placed throughout the house.
When will we need to start wearing "scramble suits"
I'm not sure that there's really a "bomb" hiding in here anywhere. The issue is that it IS "reasonable" now to expect big features to be done within a week.
We were doing that over at Vowel a few years back, unfortunately it didn't pan out because you're competing directly against Zoom, Google Meet, Microsoft Teams, etc. They are all (slowly) catching up to where we were as a scrappy startup 4 years ago.
It was truly game-changing to have all of your meetings in an easily searchable database. Even as a human.
I don't think a majority of people will find it actually useful in the long run. I do game development as a hobby outside of work and every artist I know is outright hostile towards any sort of AI, to the point that they are dropping out of any community that so much as allows any mention of AI workflows.
I know that OpenAI is at least exploring "AI as entertainment" (Sora) but it has yet to be seen if that will be widely accepted or profitable. I've also been reading about teens talking to chatbots more and more rather than talking to real people, which seems like it will only end in mental health disasters.
We have things like dependebot for this.
https://docs.github.com/en/code-security/tutorials/secure-yo...
Immich automatically dumps its DB every day, for Forgejo I have a little script that runs as part of the Backrest backup that does a pgdumb of the database before doing the backup.
It works great, I even had to do disaster recovery on it once and it went smooth.
https://github.com/sindresorhus/ky
From the readme:
- Simpler API
- Method shortcuts (ky.post())
- Treats non-2xx status codes as errors (after redirects)
- Retries failed requests
- JSON option
- Timeout support
- Upload and download progress
- Base URL option
- Instances with custom defaults
- Hooks
- Response validation with Standard Schema (Zod, Valibot, etc.)
- TypeScript niceties (e.g., .json() supports generics and defaults to unknown, not any)
Of course, this is only for projects where I have to make a lot of HTTP requests to a lot of different places where these niceties make sense. In most cases, we're usually using a library generated from an OpenAPI specification and fall back to `fetch` only as an escape hatch.
Much like giving a codebase to a newbie developer, whatever patterns exist will proliferate and the lack of good patterns means that patterns will just be made up in an ad-hoc and messy way.
At work, we just have what we call "brain" repos where we all just dump notes and commit straight to the main branch. They are just collections of markdown files that we use Obsidian to view/edit.