The page mentions sublevel, created by you, sharing the tech-stack. So I went to the sublevel site from the link in your profile and found a message stating it is “now open source”, but I can’t find a link to the source code repository, will you please share it here?
Django 2.0, PostgreSQL, Pillow for images, Gunicorn, Jinja2, Sass for themes, django-cleanup and django-simple-captcha. A VPS form DigitalOcean running Ubuntu 16.04 which is faster than 18.04.
Released the code for Sublevel then Microsoft acquired GitHub the next day, so I removed it.
Yeah, I get those vibes. - also quite like the extremely restrained design which adds to that perception. I wish a lot of webshits could be like this one in that sense.
Could you share a bit more of its story? I’m interested whether this service has any basic use case, or you just built it for the fun (which is perfectly fine!)
One of the messages says:
Messages are grouped in channels like they are on Slack and voted like they are on Reddit. It’s using mentions like on the first version of Twitter. The only thing in common with sublevel.net is the tech stack and the fact is they are both created by me. There’s filtering of bad messages and blocking of multiple consecutive messages. Private messaging will come later.
So it’s like Twitter, but messages can be voted, and hashtags define channels?
Congrats on the new project. Given you are the creator of the social site sublevel, which seems to still be alive, what was the impetus for going on to make this new one also?
The message posted about how the sign-up page contains a bug was the reason I also tried to sign up. After three times and being warped back to the homepage, I gave up. How ironic.
If personally like to see an account system using metamask, aka ethereum account Id. Its the same idea in essence as the failed browserId experiment from Mozilla a few years ago.
I think part of the issue is that lots of the bits of a social network are hard, so it’s hard to build one “your way” even though the hard parts could be a standalone library or microservice.
I’ve thought several times about a “social core” standalone library/microservice. Solving rich content, search, censorship, spam tools once and leaving authentication, authorisation, threading, moderation decisions to the app author.
What’s the use case here? Why marry these technologies? (I’m not criticizing; just confused)
Hi, the markup looks solid and neat.
Great job, thanks for posting!
Somehow, this reminds me of shoutboxes from back in the day.
Yeah, I get those vibes. - also quite like the extremely restrained design which adds to that perception. I wish a lot of webshits could be like this one in that sense.
Had a bit too much n-gate today?
I recently configured my RSS reader to email me n-gate on a regular basis. It’s not a good idea: help, I’m becoming too cynical…!
Thanks for reminder to check it. The repealing net neutrality one w/ “executive fiat’ was great haha.
No such thing in our industry, regrettably, due to the extensive marketing and cultural issues.
So it’s “IRC meets nothing else”?
Have you considered federation?
I would love something similar to this on the lobste.rs site.
First of all, congrats on launching!
Could you share a bit more of its story? I’m interested whether this service has any basic use case, or you just built it for the fun (which is perfectly fine!)
One of the messages says:
So it’s like Twitter, but messages can be voted, and hashtags define channels?
Exactly. It can be useful for live events, open source feedback like on Gitter, etc. I’m curious where it goes.
Congrats on the new project. Given you are the creator of the social site sublevel, which seems to still be alive, what was the impetus for going on to make this new one also?
Looks good. Definitely interested to hear if the project is open source. I like the snappiness and minimal amount of JavaScript
The message posted about how the sign-up page contains a bug was the reason I also tried to sign up. After three times and being warped back to the homepage, I gave up. How ironic.
It’s working fine for me
Why force people to create yet another password instead of letting them authenticate via Google/Github/Facebook/etc?
If personally like to see an account system using metamask, aka ethereum account Id. Its the same idea in essence as the failed browserId experiment from Mozilla a few years ago.
I think part of the issue is that lots of the bits of a social network are hard, so it’s hard to build one “your way” even though the hard parts could be a standalone library or microservice.
I’ve thought several times about a “social core” standalone library/microservice. Solving rich content, search, censorship, spam tools once and leaving authentication, authorisation, threading, moderation decisions to the app author.
Today, I’d rather have yet-another-password than GAMFA.
Some OAUTH type thing would be better, but I’m not aware of any such scheme that is practical today.
OpenID?
great work :)