Also check out the SmoothTrack mobile app. Same use case but the compute is done on a phone instead of the gaming machine. Head position data can be sent over local network or USB.
There are a ton of brands and I got a random knock off so I can only report on that one. I would recommend putting some thought and research into what size you think you'll need. I got a 58mm printer and I'm realizing it's quite narrow.
Also you might want to consider the size of the printer itself. I bought a open-box new printer off ebay and the seller's photos didn't give any sense of scale. I was surprised how big this "mini" printer is. It's about the standard size of a printer you'd see at a grocery store, so I don't think I'll be keeping it on my desk.
In the US my impression is that printers marketed with a size in inches are quality printers from reputable brands but bottom feeding Chinese printers are marketed with a size in mm.
If it gets someone to watch the show for the first time then that's a win in my book. I think every young student should be exposed to Connections at various stages of their education.
Addressing the end of the article, I think that we are all very much still learning how to use AI responsibly. It's like we just discovered alcohol and we're going on a rager every night because we don't know any better yet.
It's too easy to buy €100 of Claude tokens and burn through them to make those dream projects appear as if by magic. There's a middle ground where, for example, instead of building a whole project it could produce a project template and provide guidance as you build. That should take the edge off the task paralysis and hopefully disrupt the addiction loop.
That's how I use LLMs for programming. I predominately use the chatbots instead of the CLI tools. Every so often, I'll ask for a one-shot of some MVP, but then I take that MVP and make all the changes myself. However, I must say that I rarely do the one-shot-and-edit style of development. I find that such a process can save time, but not always.
People usually put pretty intimate private thoughts in diaries so I'm curious how your app handles preserving each user's privacy. Are files encrypted or only stored on a user's local machine or something?
Self-hosted: your data lives entirely on your own machine/server and obviously I never see it.
That's the primary privacy model the app is designed around.
piruet.app (my hosted instance): you're basically trusting me. (I know, trusting a random stranger on the internet... right?)
Other things I can tell you:
Passwords are bcrypt-hashed and I can't recover them, but journal entries are stored in a SQLite database on the server.
There's no at-rest encryption of content, so in principle the server's administrator could access the entries.
I don't do it on principle and there's no infrastructure set up to do so, but I can't make a technical guarantee of that.
If you just don't trust the person hosting it, I'd honestly recommend self-hosting yourself.
At-rest encryption of entries is something I'd like to add, it's just not there yet.
In the meantime, piruet.app is best treated as a demo/trial environment rather than a permanent home for sensitive writing.
If you have thoughts on how to approach encryption in a way that doesn't break usability (search, rich text, etc.) I'd genuinely love to hear them.
reply