Confidence comes from statistics. The statistics say that smaller models are better than bigger ones, ergo I have I have confidence in saying what I did.
> Once conversational intelligence machines reach a sort of godlike generality,
Sums up fantastical inevitablism.
Why would they? How could they? The data is telling us that they won't. Anybody who believes otherwise is ignoring the science.
The assumed path to "AGI" was more tokens, but more tokens actually means worse output, and if LLMs aren't a total technological dead-end, period, then the data is supporting smaller models meant for more specific things, ergo, LLMs are not giving AGI any time, ever.
Pure fantasy. Can't even call it sci-fi when it ignores the science entirely.
Do what I couldn't with these supposedly capable LLMs:
- A Wear OS version of Element X for Matrix protocol that works like Apple Watch's Walkie Talkie and Orion—push-to-talk, easily switching between conversations/channels, sending and playing back voice messages via the existing spec implementation so it works on all clients. Like Orion, need to be able to replay missed messages. Initiating and declining real-time calls. Bonus points for messaging, reactions and switching between conversations via a list.
- Dependencies/task relationships in Nextcloud Deck and Nextcloud Tasks, e.g., `blocking`, `blocked by`, `follows` with support for more than one of each. A filtered view to show what's currently actionable and hide what isn't so people aren't scrolling through enormous lists of tasks.
- WearOS version of Nextcloud Tasks/Deck in a single app.
- Nextcloud Notes on WearOS with feature parity to Google Keep.
- Implement portable identities in Matrix protocol.
- Implement P2P in Matrix protocol.
- Implement push-to-talk in Element for Matrix protocol ala Discord, e.g., hold a key or press a button and start speaking.
- Implement message archiving in Element for Matrix protocol ala WhatsApp where a message that has been archived no longer appears in the user's list of conversations, and is instead in an `Archived` area of the UI, but when a new message is received in it, it comes out of the Archive view. Archive status needs to sync between devices.
Open source the repo(s) and issue pull requests to the main projects, provide the prompts and do a proper writeup. Pull requests for project additions need to be accepted and it all needs to respect existing specs. Otherwise, it's just yet more hot air in the comments section. Tired of all this empty bragging. It's a LARP and waste of time.
As far as I'm concerned, it is all slop and not fit for purpose. Unwarranted breathless hype akin to crypto with zero substance and endless gimmicks and kidology to appeal to hacks.
Guarantee you can't meaningfully do any of the above and get it into public builds with an LLM, but would love to be proven wrong.
If they were so capable, it would be a revolution in FOSS, and yet anyone who heavily uses it produces a mix of inefficient, insecure, idiotic, bizarre code.
Ah yes, truly impressive, Pong. A game that countless textbooks et al have recreated numerous times. There's a mountain of training data for something so unoriginal.
This has been one of the most rewarding comment threads on HN I've read in a long while. Lots of learning even for me in terms of what the current state of things is in terms of cost and choice.
But do they run FOSS software? And can they thus be trusted? Lots of network gear gets zero day'd and exploited. I can understand the sentiment of wanting to run something that can potentially be fixed and fixed quickly.
The average American or British living room with even a cheap surround system is going to run rings around anything in-ear or on-ear.
There's many reasons that people warn newbies not to mix or master on cans and to use speakers.
For people who care about going beyond stereo, budget is going to be a much larger problem for most folks than space or technical knowhow. And anybody who cares about going beyond stereo probably cares about quality.
With tight deadlines, there frequently isn't the time to not be working concurrently on the same doc, especially when it comes to anything technical.