For this challenge, you need to implement a Twitter/X/Threads experience where you can see a thread and reply to it. The entire data of the thread must live in the URL and be end to end encrypted. You can take inspiration from this blog post that explains how it works on Excalidraw. The hashtag part of the URL must be below 2000 characters. The idea of this challenge is to raise awareness on the fact that we can do end to end encryption in the browser and using data compression to make a large amount of content available, as well as figuring out how to work out data sharing.
Third place, @tobua wins $45! This entry has a really interesting use of localstorage and password protection for this entry. https://github.com/Algorithm-Arena/weekly-challenge-4-encrypted-thread/issues/3
Runner up, @alcpereira. This one implemented the challenge to the letter. It has encryption and compression in the url and is fully functional. https://github.com/Algorithm-Arena/weekly-challenge-4-encrypted-thread/issues/4