Lucian Marin
Why Subreply?
Subreply is to Twitter what Pinboard is to Delicious, Reddit to Digg, Linux to Windows, Android to iOS, and so on.
Here are the project requirements for Subreply:
- No JavaScript. Subreply works with JavaScript disabled.
- Dumb phones supported. Subreply works with Opera Mini.
- Responsive design. Subreply works on any device with a modern browser, from smartphones to TVs.
- Elegant design. Subreply needs to feel as good as — or better than — a native app.
- Powerful web app. Subreply uses design hacks to improve performance.
- Different than Twitter. Subreply is not a clone of Twitter the way App.net was, nor is it trying to reinvent the wheel. There is no character limit; Subreply is limited by design only.
- No user tracking. Subreply doesn’t store any metadata associated with users or replies.
- Discoverable. Subreply uses an explore page to keep people informed, similar to HN, DN or Reddit.
- Clear searching. Subreply lets you independently search for replies or for people’s usernames, bios and locations.
- Just text. Subreply won’t provide support for images, videos, gifs or mp3s — third-party services do a better job. Subreply provides support for links, mentions and hashtags.
- Threaded conversations. Subreply’s reply system is clear, so there is no need for mentions. It lets you join any conversation.
- Less spam. Subreply prevents spam with two features. First, it lets the parent of a reply delete any children replies. Second, it lets people send just one reply, expecting answers back from the other participants in the conversation.
- No API. Subreply doesn’t need an API, just better web browsers. Instead of an API, Subreply will try to have an open database.
- Powered by mini ads. Subreply is free, and the ads will never be intrusive — actually, they look quite good.
The idea behind Subreply is to have a public network with no hidden tricks, gimmicks or any other crap like that.
Have some fun on subreply.com :)