You can set this up yourself with API keys to the corresponding providers and creating an Agent Group in https://github.com/lobehub/lobehub. Agent groups allow you to easily create a room of agents and have them discuss any of your topics. Easily make agents with types and skills, it even assists in drafting starting prompts and even team members depending what your query (and selected model) is.
You can self-host as well, but not via desktop app. Sever setup required.
Be careful of your token context, you can easily rack up costs if you leave Opus selected as the model and get lost in some rabbit hole of results.
Nothing stops that from happening. Just needs to be trained in that DSL. Though at that point it returns to it's original form as a better autocomplete/IntelliSense :).
That will likely happen in the specialized fields. We can already see tools like Figma, Mira, and others that generate functional-ish frontend components in full typescript and corresponding styles (that are also selectable and configurable in the interface). Though, not quite as free, since they do load their base framework and components to ensure consistency and sanity / error-checking, etc., but even then it is in fact generating you useable, modifiable components that you can engage with in precision in your normal DSL.
For video, this likely exists, or is being worked on as we speak. All specialized domain tools will go towards this model to allow those domain experts to use the tools with the precision they expect AND the agentic gains we already take for granted.
Despite their confusion as to whether they want to really support their free and open source versions (without some absurd user count cliff), Mattermost (https://mattermost.com) is quite excellent and IMO is better than Slack. For example, editor leans towards native Markdown so things like syntax highlighting with backticks work as you expect.
Their recent update removed the paywall from SSO (and unfortunately the Gitlab SSO workaround) for social logins up to 100 seats, afterwards there's an absurd per seat cost similar to its non-open source brethren. One day if needed, I plan to drop-in an SSO middleman allowing anyone to leverage their own SSO layer (which will map to the login form with username/password) to avoid the SSO limits altogether. Though good enough for my needs, and likely yours too. Especially if you're open to paying for their seats.
Unfortunately there are many companies that actually rely on SMS confirmation codes in real-time, which include reading it back to them.
A legitimate and generally well liked company, and its real helpful service representative used this method to verify my identify before they could finish their support effort.
I've mistakenly given Chatbox a new feature, sorry :). In LobeChat, after you select a particular model, it enables a mini-settings menu next to the model that lets you set caching, deep thinking, and thinking token consumption.
Been using both, like Chatbox for how snappy it is, but is local only, vs Lobechat which allows you to setup centralized host to have shared host across clients but feels a bit clunkier.
#freenode was generally the main IRC node I used with all the good dev rooms.
Seems to still be chugging along. You can even join directly via their web-client: https://freenode.net.
Personally I still use pidgin.im to connect to all the relevant #freenode goodness. Seems people forget it still works and is pretty great even all these years later :).
Seems to be missing quite a bit of history. As many here mention, there was an entire ecosystem of tools to convert PSDs to HTML such as CSSHat, Engima64, etc., and its evolution into Avocode, Sketch, Zeplin, Invision Craft & Inspect, and other preview/prototyping/inspect/export tools.
Eventually all roads led to Figma somehow, which honestly I would've never expected. Still surprised Figma became Sketch before Sketch could become Figma.
There's also open-source solutions such as rocket.chat, Mattermost, and likely a few more I haven't played with.
I wish Mattermost wasn't always trying to nudge you out of community version, but otherwise pretty solid, better than Slack IMO. Is unfortunate they require weird gitlab spoof bypass to use SSO in community version. Shameful it's not out of the box.
Many years ago Pidgin with multi-channel IRC was all I needed, but seems Slack killed that whole party, which brings us to the current situation :(.
I know Liveblocks.io has been making this very easy and accessible over the last few years. They recently introduced AI, and are promoting that of course, but as I understand it multiplayer collaboration (https://liveblocks.io/multiplayer-editing) is their meat and potatoes.
Not affiliated with Liveblocks, just aware of its existence.
Opening up one's device does not void the warranty in the US. We have the Magnuson-Moss Warranty Act which forbids this, despite manufactures trying to groom us otherwise with those void if removed or broken stickers.
Will take a long time to de-program and by that time nothing will be replaceable to matter due to industries march towards preventing repair altogether.
There's also https://openobserve.ai, while not as stable as Grafana/Prometheus/Clickhouse, feels a bit easier to setup and manage. Though has a bit of ways to go, does the basics and more without issue.
Crazy crazy they spent so much on observability. Even with DataDog they could've optimized that spend. DataDog does lots of bad things with billing where by default, especially with on-demand instances you get charged significantly more than you should as they have (had?) pretty deficient counting towards instance hours and instances.
For example, rather than run the agent (which counts as an instance regardless of if it's on for a minute), you can send the logs, metrics, etc. directly to their ingestion endpoints and not have those instances counted towards their usage other than log and metric usage.
Maybe at that level they don't even get into actual by usage anymore, and they just negotiate arbitrary amounts for some absurd quota of use.
Nope, is completely the same base. Scroll the homepage, and you'll see an example of Livecode (updated HyperTalk).
You can open your HyperCard stacks, or MetaCard stacks, or Runtime/Livecode Stacks in their IDE, code, edit, etc, similar to what you would have back in Hypercard days, but with modern features, updates, and additions.
It's backwards compatible with HyperTalk, its current language is an updated HyperTalk (i.e. an updated MetaTalk), that incorporates all that was, but adds new features for today.
Your Livecode apps can be deployed and run as cross-platform desktop applications (Mac, Win, *nix) , mobile applications, and as far as I remember, web applications with HTML5 deployment (so they say).
Not affiliated with them in any way, just sharing my understanding and memories.
His legacy still exists and continues today. Even updated to modern sensibilities, cross-platform, and compatible with all your legacy Hypercard stacks!
As far as I remember, progression was Hypercard -> Metacard -> Runtime Revolution -> Livecode.
I was a kid when this progression first happened, my older brother Tuviah Snyder (now at Apple), was responsible for much of these updates and changes first at Metacard and then at its acquirer Runtime Revolution.
I even wrote some of my first programs as Hypercard compatible stacks. Was quite fun to see my apps on download.com, back in the day when that meant something :).
I always joked it required please and thank you due to its verbosity, but was super simple, accessible, and worked!
How nice, that even today one can take their legacy Hypercard Stacks and run them in the web, mobile, etc. Or create something new in what was more structured vibecoding before vibecoding :).
Seems there's either too much supply of drivers, and/or this whole cat/mouse gambling game, is overall adding waste and inefficiencies in the system. Seemingly by design to hold on to the driver pool while the drivers not realizing they're cogs being shelved in the system at the drivers own cost time and monetarily.
Pretty amazing how far behind regulation is compared to all these dynamic dark patterns. Not only in Uber, but in most everything we encounter these days, we're being guided, routed, or decided upon by unregulated dark patterns that would clearly be illegal if the details of which were exposed and explained in a way that anyone could understand.
You can self-host as well, but not via desktop app. Sever setup required.
Be careful of your token context, you can easily rack up costs if you leave Opus selected as the model and get lost in some rabbit hole of results.
Enjoy enjoy!