u/HackTheDev

Over time DCTS has changed a lot from being one big, modular project into many flexible code packages that can be reused elsewhere. This opened the door to create apps and features easier, quicker and with a lot less overall maintenance.

Because of recent developments, like the messenger feature, DCTS itself has been evolving and is becoming more than "just a group chat app" like discord. It will significantly expand the scope and reach of DCTS. You can think of the upcoming messenger being like Signal, but easily self-hostable and account-less. Some more details can be found on our forum.

In addition to that there is a new ticket system in the works where a prototype was briefly showcased here. The goal is to make it work as a standalone application and with direct, flexible integrations so it can be used seamlessly for dcts as well. There are also plans to possibly implement some form of API as well.

All these awesome systems were made possible by creating these flexible code packages and while its a lot of work at first it starts to pay off later. The long term vision for DCTS is to make more free open source software, evolving more and creating a bigger ecosystem of cool stuff!

I also wanna thank all donators in helping raising 1,069.00€ since Jan 2025!! You too can donate here on ko-fi and "invest" into a bright future :D

The messenger features are finally working! Now i need to finish up the finer details like message editing/deleting/replying, embed support and all that. It shouldnt be too hard as its already done in the server chat and dms, so i just need to extract it, likely turning it into a new library.

Other than that i will improve the styling more and add some client settings like profile pic, username, delete chat, rename etc.

The hardest part is done!!

I can say that quite some stuff is going to change like the navigation on the left and styling, but this is the general concept as of right now.

Im making it so it can be integrated into "services" like a DCTS instance or used standalone. Additionally the idea is to add optional End-to-end encryption just like with the DMs in DCTS.

Speaking of that, a lot of work is still going into it, mostly concepts and theory on how to best implement it, but almost everything is sorted and im working more on the prototype again.

I would assume the "offline" messenger feature should be done in about a week or two as its mostly done now.

A lot of work was concepts and doing a lot of backend work which is why i cant show much yet (its literally just code), but soon i can reveal this new awesome feature!

now i just need to add the chatting mechanism itself. shouldnt be all to hard since a lot of stuff is already taken care off and just needs to be plugged together correctly-

The idea is to add a messaging function to the desktop client that can use existing dcts instances to transport encrypted messages to lets say a friend. this way if you dont need the community and server aspect of dcts you can still use it as decentralized, e2ee messaging app.

The screenshot is still very early, but thats kinda the vision im having for it and i think its gonna be a pretty cool feature too.

You wont need to have an account on an server for your message to be transported and servers will be opt out since bandwidth doesnt grow on trees.

https://play.google.com/store/apps/details?id=community.dcts.app

I had this planned for a while and the cool thing is as long as you dont lose your key file you wont have to remember any username or password at all.

Just gonna note that while i wont actively pursue the google play store stuff i will occasionally try to re-submit it from time to time. i submitted this new ui and if we're lucky they may actually accept it for once.

if not i will try another time but getting it on to google play isnt the core focus for now

https://github.com/hackthedev/dcts-client-shipping