Skip to content
C

communIIITy

Discussions, by students, for students.

Created on 16th April 2021

C

communIIITy

Discussions, by students, for students.

The problem communIIITy solves

We started our B. Tech classes in the December of 2020, and 3-4 lectures into our Introduction to Programming (ITP) course, we were already out of platforms to discuss questions among ourselves. We realised the magnitude of this problem when our ITP Professor Saurabh Sir started receiving near identical queries from multiple students. The online mode of learning was bringing up new problems, so we came up with a bunch of ideas. One of them being StackOverflow - The saviour of every software engineer. But the teams option in stackoverflow was free only for 3 months and then we were back to square one. So we decided to take the matter into our own hands and develop a solution for it.

We present communIIITy, a platform where students and instructors from an institute can easily interact with each other, be it via asking questions or posting answers. Unlike platforms like StackOverflow, communIIITy is primarily geared towards people from individual organizations. This provides an exclusive communIIITy (pun intended!) platform customized to its unique needs, it also gives liberty to have discussions among people with a similar knowledge level and helps avoid the financial overhead of buying a teams subscription on StackOverflow. communIIITy is based upon the decentralised matrix protocol, which means lower downtime when compared to websites such as StackOverflow which can face outages.
communIIITy uses Tezos blockchain for peer discovery, and uses that data to exchange information with its peers. The peer-to-peer exchange is cryptographically secured and authenticated via signed trusted certificates. Highest upvoted questions and answers are shared with other institutes.

Challenges we ran into

We accidentally set two different variables to point to the same button, so we were making duplicate database transactions. This was, however, a blessing in disguise as we realised that the backend was allowing duplicate transactions, which could be a security risk.

Discussion

Builders also viewed

See more projects on Devfolio