Weekly Challenge #4 - Encrypted Thread

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.

Winners

• @luisperezphd wins $150 as this submission is going above and beyond: there's a full UI, account management, multi-thread support... Really impressive work! #5

week4-1.mp4

• Second place, @IamRstha wins $90! One of the trickiest aspect of this challenge is how do you share the URL and the flow around it. This submission decided to have a real time collaboration aspect in addition of the pure URL. #2

week4-2.mp4

• Third place, @tobua wins $45! This entry has a really interesting use of localstorage and password protection for this entry. #3

• Runner up, @alcpereira. This one implemented the challenge to the letter. It has encryption and compression in the url and is fully functional. #4

week4-4.mp4

• Last but not least, @Uzo2005. This didn't quite follow the rules as the server is holding the content, but cool solution nonetheless! #1

week4-5.mp4

Prizes:

• Winner: $150
• 2nd: $90
• 3rd: $45

Rules:

• The winners will be evaluated based on how creative and interesting the solution is. @vjeux has full discretion on how the winners are selected.
• Multiple people can work on a single submission. If it wins, the reward will be split based on the team preferences.
• If a winner doesn't want to take the money, it'll be reinjected in the next week prize pool.
• The solution must be open sourced.
• There are no restrictions in terms of tech stack.

How to submit a solution:

• Deadline to submit is Sunday Febrary 11th evening at Midnight PST (US West Coast).
• Open an issue on this repo titled "Submission - <Name of your submission>"
• It must contain a short video showing the submission in action
• It must contain an explanation on how to try it
• It must contain a link with the source code