This project has been deleted.
a usenet-like application where you get to talk with other people in rooms with four dot identifiers. SEE README
No followers yet
Once you ship this you can't edit the description of the project, but you'll be able to add more devlogs and re-ship it as you add new features!
oh my god... turns out going from pretty much done to mass production ready takes a lot of time - Linus Sebastian. Server hosting was a nightmare. First, image hosting completely broke because the build folder had a different hierarchy. Then web sockets was broken for a week because Caddy wouldn't accept same-origin requests to connect to a websocket. Finally changing domains, this ship is finally ready for human consumption. Enjoy!
Funtime! Just got the basics of AtomChatDB fully working and fixed the stuff that gives the app proper usability and demo-ability. There is now a working bot that helps create groups, a bunch of text boxes now work when press enter, and I also made everything a lot more uniform. This version of the app is going to be shipped, so please check out this app because it's very cool!!!!
finished the chatrooms and newsgroups for the most part so almost ready to ship, but the images turned out to be a pain.
The way I was transmitting user images and message images before was stupid... User images were encoded in base64 and attached by the server to every message sent. This would obviously add up to way too much space taken by duplicate base64 images. Message images were also in base64, which made implementation easy but couldn't be cached like normal images.
I ended up redesigning the way images are uploaded, which is that display pictures go through a pipe that compresses images into a jpeg and saves them locally. If a user doesn't have a profile picture, the server hook will auto-redirect to a generated one on-the-fly. This way, users don't need a special key for images, seeing as usernames are supposed to be unique anyways.
For messages, there is a unique key. Images are thrown into the /parseimage API endpoint which checks for authentication before compressing and saving their image. It then returns a unique key that is saved along with the message, which can be easily accessed by the client to display images.
The plus with having files is that the database doesn't get slower and slower. Base64 strings are the same size as the images they take part with (around 20kb for the compressed files I'm using), so there isn't much of an advantage unless I literally cannot store files on a server. Also, web browsers have much better caching now.
Hopefully tomorrow will be the finishing touches day.
no common cold's gonna stop me from grinding that 💰 web socket implementation!!! just got messages sending and receiving so yea that's cool!!!
slight crash: so I unified the SQL tables so chatrooms and newsgroups share the same layout. surprisingly the beta version of sveltekit with websockiets is working pretty well, now I'm working on the chatgroup api for real-time communication.
finished up the forum implementation, now just have to add realtime chat using a pull-request version of sveltekit to get websockets support 😭
sooo just got the logic for deleting and auto-updating!!!! it seems like we got some good progress rolling, and we're 40% of the way done with the app
got some work done into creating forum posts. wasn't all good, had to completely redo a portion of the code to make the code less janky and reliant on the worst sql you'd have ever seen.
just set up guest accounts so you don't need to create an account to participate in chats, but gotta think about how to fix the spam 🙏