I would go even further, I want a browser extension that scans all words on every page and colours them more and more transparent as the likelihood of llm prose is increased.
Years ago I used a rudimentary (text matching) Greasemonkey script that hid Reddit posts and comments from accounts matching a few behavioral/history signals.
I wonder if that idea could be modernized now for this.
Are you footing the bill yourself, or would you be supporting BYOK? Not sure whether logging in with user's account would also be a good workaround or not.
Pi is a great example of this. I've used it as the basis for a fleet of agents I'm running on my server, but rather than using the Pi TUI I run it in headless-mode and have extended it to use XMPP as its communication layer so I can use any device with the same sessions, and so agents can talk to each other.
The Pi harness is built to be extended like this, and it's a joy to work with.
I've come to a similar lofi solution for my agent fleet. Markdown wiki with simple querying is decently effective as a memory system. Setting up a skill that can effectively reduce a session into useful long term lessons is the easiest unlock for these systems.
I ran into this exact problem. I needed to fork Conversations to add a lot of polish. My fork is definitely improved but still has a few rough edges I'm chipping away at.
I have recently picked up XMPP as my agent communication layer, and its worked great. Each pi agent is given an account and wrapped in an XMPP client[0] that lets it speak to me and other agents when needed.
This has worked well since I can spin up new accounts on demand and I can use existing server software (ejabberd, perfect) and clients (Fluux, great; Conversations, okay). I've had to make a few custom modifications to each client to make agent comms a bit nicer (e.g. exposing status messages more prominently since I use that to expose current agent commands), but the XMPP layer has had pretty much everything I could have wanted.
Controlling a chat service is a bit intoxicating, I'm now using it as my notification service over a bunch of different projects.
I used Google Chat way back, its nice that the tech is still around and great as ever.
This is really neat. I've recently been watching people use custom pi harnesses and thinking of jumping in, but I was dreaming of a way to do essentially what pi-msg does so that I could drive it remotely in a more full-featured way. Thanks for sharing.
Thanks! I had the same urge, I didn't want to be responsible for an entire GUI and communication layer but I did want to have a remotely controllable extensible harness, this was the perfect middle ground.
The benefit beyond that was having agents running on my server directly so they can do a lot of sysadmin and monitoring tasks, as well as suggesting config changes through PRs to my nix config.
Letting the agents bang their heads against the wall hunting down a config fix for a random malfunctioning piece of my homelab instead of me is by far my favorite part of the AI present.
pi-msg doesn't support bonjour, I'm running it on a nixos server (nix is the real secret ingredient of my whole setup) the xmpp server is the same machine as the agents. I'm almost always on a different network to the one where the server is. If the server goes down the agents and ejabberd are coming down simultaneously.
I recently had to rebuild a jira frontend from scratch just so a single jira tab didn't take down my 8gb MacBook. Support only the subset of features I actually use and it's great. Makes me hate jira even more.
> Update - We are seeing an approximate 20% error rate across numerous experiences including Pull Requests, Issues, and others. Investigations are currently under way and we will be posting updates as they become available
The error rate is 100% on the service that allows you to create PRs in the web site. Actual remote git service is working just fine. I might try the API to make a PR, see if that's working.
Update: yes that worked. gh CLI using the API was able to make a PR while the web interface was inoperable.
Second update: defeat from the jaws of victory -- the page that displays open PRs is also down.
Third update: CI isn't working anyway, so the CLI PR creation workaround doesn't achieve much.
It seems vastly higher on every region and VPN I've tested, so I think this is a case of the "technicalies".
It is technically 20%, because a bunch of the requests that happen on page load do succeed. Just not the few crucial ones that are required for the page to load correctly - those return a 500 the vast supermajority of the time.
Feel free to disregard this because ultimately its a tangent that doesn't matter; but supermajority is specifically a political term referring to the required threshold to advance legislation when simple majority isn't procedurally enough. It doesn't mean simply a greater share of.a majority
For supermajority: the construction means “beyond majority” or “above majority”, it is implemented as a higher percentage in most systems, and there is a utility in being able to refer to high ratio majority.
So people have repurposed a technical word to a general word, of roughly the same meaning.
It's neither. If you accept and approve of people wearing their pants around their knees, its a fashion evolution. If you think pants should cover your ass, it's just poor behavior. Analogous to the use of language.
Farid Zakaria's recent nix saga is insane
- unifying all versions of all packages into one resolution tree
- making executables out of sqlite databases
- adding API routes to a sqlite executable with an insert statement ?!?!?
- making one flake that contains all flakes
- adding version ranges to nix
- run any nix package any nix version in your browser (this one)
reply