Nördnytt! 🤓Parley: Federated, decentralised chat that speaks plain IRC
- advisedwang - 9322 sekunder sedan> No channel modes and no channel operators, which is a decision rather than a gap: a global channel is owned by nobody, so there is nobody to be an operator of it. Blocking is per person and per instance instead
That's completely unworkable. Lets say I create #some_minority, and people from many different servers join. Some shithead comes and starts screaming slurs at us. Now the admin for every server must block that person. Multiply that by every channel, and every admin is responsible for moderating the entire ecosystem. The only way they can do this is with shared blocklists, which have been a nightmare on mastodon.
- xena - 32390 sekunder sedanHow do you plan to handle bad actors creating biblical amounts of servers dynamically and then spamming at line rate from all of those servers?
- plq - 4633 sekunder sedanHaha so this project speaks IRC, no less :) This is surely relevant then: https://www.mirc.com/split.html
- singpolyma3 - 35833 sekunder sedanSo rooms are "global" between whatever hosts your host happens to know about? So it's one giant netsplit party forever and only your server admin can ban someone?
- threecheese - 9862 sekunder sedanIs anyone leveraging IRC/XMPP/etc for agents or A2A communication? It seems like a natural fit; all the "human agents communicating" abstractions and underlying technology pieces are in place and mature, as are methods for dealing with unruly actors.
I've wondered why I haven't seen this everywhere.
- davidcollantes - 42678 sekunder sedanParley is a chat network with no centre.
Every person (or team) runs a small instance for their own domain. Instances find each other through DNS and well-known identity documents, exchange signed messages over HTTPS, and present the whole federated network to ordinary IRC clients such as Lurker, Mango, mIRC, WeeChat, Textual, etc., without the need of any plugins.
- Conlectus - 35676 sekunder sedanThere’s a specific downside to LLM-based development that people can get neck deep in a new project without interfacing with the existing work in the field.
In this case, this is basically a poorly specified implementation of half of XMPP. Of course, I half expect the LLM would have mentioned that at some point, but the repository does not.
- flymasterv - 19542 sekunder sedanI'm searching for a simple, self-hosted chat system that allows me to host unlimited bots and send messages (with notifications) to my iPhone easily.
I currently have an XMPP server running, which is fine, I guess. I've looked into chatMail. I have considered hosting an IRC server.
At this point, I'm considering just setting up my own NTFY server and writing a chat client for it.
Does anyone have any ideas for what the lightest weight, simplest solution might be?
- aunderscored - 38466 sekunder sedanInteresting. Why not use an open link network? These will result in around the same state. Spam _will_ be an issue here, in general. And with a different backend you're going to struggle to use preexisting tooling to handle it.
Using & channels is fun, I'd be interested to see how many bots and clients fall over dead when faced with that particular bit of IRC history.
- user2722 - 36540 sekunder sedanI had a pseudo-plan for something like this but for reasons related to privacy I had two types of chatrooms:
* regular chats, existing only on the server, no leaking the chat transcript except via users, but never via server to server.
* chambers: a global chatroom, located at a server, maybe with a MQTT anyone could subscribe to.
This never left the early planning stages though, but I thought the segregation between federated chatrooms and regular chatrooms was of interest to keep in sync with IRC open but closed nature of chats.
- myaccountonhn - 39970 sekunder sedanI quite like this, but it feels like spam could quickly become a concern.
- someonebaggy - 37523 sekunder sedanVibecoded?
- rixed - 34474 sekunder sedanInstead of a separate federated network for a single app, why not implement the app on top of a pre-existing federated network, so that nobody has to create yet another account? Like, on top of atproto or activitypods or...?
- ad_fontes - 18136 sekunder sedanThis is pretty much just a reinvented Matrix protocol. Nearly identical.
- - 41105 sekunder sedan
- Marlinski - 38153 sekunder sedanGive me a day and I'll implement it in my agent-oriented IRC server https://github.com/marlinski/airc !
- padolsey - 39751 sekunder sedanBoth cool and worryingly convenient for the botswarms we've been warned of...
- mococa - 33333 sekunder sedanBesides not having C runtime linked (which is great for scratch/distroless Docker images) - any other advantage of using a pure Go SQLite instead of the C binding?
- Klonoar - 15299 sekunder sedan> "Scrollback that follows you rather than your client"
This form of LLM speak annoys the absolute shit out of me. It's a bot trying to emulate the worst reassuring sales copy you could imagine.
- shreddit - 39866 sekunder sedanThis is exactly what i was thinking about for the last few weeks (but am too stupid to implement myself).
It’s like email just for IM…
- jagermo - 32990 sekunder sedanis there a list of public instances one could join somewhere? I kind of want to dip into irc again. it was peaceful.
- sailfast - 22722 sekunder sedanParlay?
- tonymet - 24366 sekunder sedanIRC is popular because it’s bad. I don’t believe there will ever be a replacement for this reason.
- - 28104 sekunder sedan
- lnxg33k1 - 29592 sekunder sedanBut isn't IRC already federated?
- pixel_popping - 35190 sekunder sedanThe connection to git.mills.io was interrupted while the page was loading.
- okwhateverdude - 39542 sekunder sedanlol, so XMPP, but instead of XML, it is IRC. Alright, I dig it.
- MMTlover - 24626 sekunder sedan[dead]
- corbinvachal - 25973 sekunder sedan[flagged]
- elkamiliyoussef - 23797 sekunder sedan[flagged]
- nahid-fahh - 38819 sekunder sedan[dead]
- thomasreiminger - 32775 sekunder sedan[dead]
- calvinmorrison - 36529 sekunder sedanI recall this bait and switch. It was called Slack