You are browsing as a guest. Sign up (or log in) to start making projects!

One-To-One

By @tiyas

  • 12 Devlogs
  • 35 Total hours

A serverless walkie-talkie. Built for people who don't want to save their talks anywhere. Especially when i started building it , my motivation was to make a chat system where teen couples can talk without the risk of getting exposed... The use case of it is like, when two people trust each other and know each other but dont trust the servers, or maybe a group of friends wants to gossip, then they can use it to play truth dare or share their thoughts without exposing their identity completely. This is a type of game-like stuff...

Source
Ship #1 Changes requested

@tiyas on One-To-One

i have made a simple webRtc bassed chat app. the special thing of this webside is that, as soon as both friends will close the chat the messages are gone for forever, no scope of being stored anywhere. and even no servers in between, i would call it power-user stuff, because it is so bare-metal that you have to exchange the WebRTC tokens yourself.

if you are testing this, try this in two different tabs insted of running on two devices. it will work perfectly fine.

i am proud of,

  • its my first react app, and i have made it quite good enough
  • i have fixed some of them myself
  • i have spent a lot of time in it and build sucessful running app
  • i have completed it within 20 days…

The improvements in quality of life are,

  • got one private and secure and serverless chatting platform
  • one more step towards off-grid life
  • improvement in privacy.
  • data will be stored nowhere

to be honest, my true motivation was,

  • to give young couples a platform to talk privately and with zero risk of someone seeing their old messages…

  • and i think, from a psychological point of view, most of the fight happens in young couples when they see some hurtful message again and again, but this has no way to see that, when you talk , only then you are able to see the chat , as soon as that ends, your brain also stops processing those , because you know they are completely gone..

  • these messages are stored in your device’s ram,

  • and as soon as the program stops running, the data are gone.

Try project → See source code →
Open comments for this post

@tiyas on One-To-One

1h 23m 49s logged

i have added the loading animations, and now i am filling out the docs a little.

  • i have also published it onto my own domain,
  • chat.tiyas.uk

next i am going to ship it.

0
0
29
Open comments for this post

@tiyas on One-To-One

2h 2m 39s logged

I have ran the 2ed successful test. and now its live at,

“https://tiyasbanerjee.github.io/One-To-One/”

  • i have added some features
  • like sending messages on enter press,
  • scrool at the end as soon as new message comes or send.
  • set up the github stuffs for deploying.
  • and fixed some bugs
  • like some scroll bars were showing where they should not..

its still not ready to ship now, i want it to look better and be more robust towards edge cases.

0
0
59
Open comments for this post

@tiyas on One-To-One

5h 4m 36s logged

at last!! at last i have fixed the bugs 😭😭😭😭. i cant explain the satisfaction level. now messages are sent successfully. But it is still not ready to ship now. i need to harden the logic and count all the edge cases too… but i cant explain the joy i am feeling. it might took 50% of the total time spent on this project. i thought that Ui would be the hardest part. but no, establishing the connections and managing states and variables and logic flow was the hardest, i mean most draining. while doing this i had lost my motivation many times, i thought i cant do, i am failing… but i stick to it. and it worked😭 ohh man!!!!

0
0
46
Open comments for this post

@tiyas on One-To-One

8h 53m 31s logged

It took me quite some time to stitch the underlying connections. these includes,

  • token compressition
  • showing token on linkbox
  • writing the logic of the information flow.
  • writing the logic of showing a message on the message box.
  • some Ui fixes
    etc etc…
    i think this is the hardest part…
    and still its not done, i still have to write the logic of how to take input of peer token, and then have to cheak if things are working properly, i think it would have lots of bugs, i have to fix them…
0
0
20
Open comments for this post

@tiyas on One-To-One

1h 0m 46s logged

worked on the message layouts,

  • worked on the incoming and outgoing message layouts
  • did some styling modifications on the connect page
  • spend time learning about back-end connections…
0
0
53
Open comments for this post

@tiyas on One-To-One

1h 46m 45s logged

deigned some amount of the chat interface.

  • like adding the input field , making it responsive
  • making the button responsive.
    next steps are,
  • making the layout for the messages, like how they user will see messages…
  • receiving the messages and sending it…
0
0
84
Open comments for this post

@tiyas on One-To-One

5h 31m 42s logged

new updates are

  • worked on responsiveness
  • Worked on degine and styleings
  • Worked on annimations.
    and next steps are
  • establishing the webRtc conection
  • building the chat interface.
0
0
21
Open comments for this post

@tiyas on One-To-One

4h 31m 59s logged

i have switched from basic html css to React. and i have made the first page/welcome page of it. Next, I will make the connection establishment page, and then the chart interface..

0
0
16
Open comments for this post

@tiyas on One-To-One

2h 0m 6s logged

i have Build some of the UI for the chart interface and wrote some docs… will work farther on the WebRtc connection next.

0
0
32
Open comments for this post

@tiyas on One-To-One

1h 17m 17s logged

trying to code the handshake part but i am facing a lot of issues in this webrtc connections ,mainly in the handshake process…

0
0
21

Delete project?

Are you sure you want to permanently delete this project? This action cannot be undone.

All devlogs, followers, and associated data will be removed.

Followers

Loading…