writing a chat thingy in NodeJS + clientside JS.. the idea is to make it as simple and foolproof as possible, easy to host, with optional end to end encryption that's entirely taken care of on the client. The server will just forward what it receives, optionally caching it and allowing clients to pull messages based on a timestamp delta. Everything will be 'groups', a DM with a friend is a 2 person group, a groupchat is a 3 person group, etc, to keep things simple. Probably add file/images later
@anthropy This reminds me of one of the first projects I was working on when I learned programming in C#, a socket based chat client/server. The good old days when software was much more simple. :drgn_flat:
"This line of code [...] was the place that caused our CI/CD envs to be exposed to the world."
(Code explicitly turns off any safeguards)
"Yes, we *** up using chatgpt generated config and doing code review."
Good guy ChatGPT teaching people lessons in verifying information
So turns out RSS is a most likely a pretty fucking good solution to get rid of the dozens of different kinds of emails I was about to implement for a work project. People need a way to keep track of queues and Outlook has an integrated RSS reader. I love RSS.
Outlook has an option to re-insert updated feed items. So my options for updated feed items is that you either don't see them at all, or you may get multiple versions of the same item. The latter is fine I guess (people would've gotten the same experience with emails), but why not simply mark updated items as unread again?