noaheverett

edit: one thing I forgot to mention is, when creating your pool make sure to import your drives by ID (zpool import -d /dev/disk/by-id/ <poolname>) instead of name in case name assignments change somehow [1]

[1] https://superuser.com/questions/1732532/zfs-disk-drive-lette...

Comment · 3 years ago

I do appreciate the response and feedback. You are right, the network effect is the hardest challenge to a social platform. A way to bootstrap is to treat Glue as a "blog" or a personal website where one can post content in a stand-alone manner, while hosting it under their own domain so it feels like a personal website. I haven't really done any marketing to this effect, but I probably should.

Regarding distributed protocols: I am interested/watching those, especially the domain based handles, to see if there is a way to integrate as Glue already supports custom domains. Short answer: Yes, I'm watching to see if there are ways that fit Glue's use-case to tap into those protocols.

Glue is one app in an ecosystem of apps I'm working on under Ark (https://ark.fm): Pingly: email / calendar / team chat, Glue: social networking / blogging and a third in progress. I haven't really said what Ark is going to be as what connects all these apps is still in works and honestly is evolving as I go :)

Thank you again for your comment, cheers

Show HN: I created Twitpic, now I've launched Glue

8 noaheverett 3 years ago 2 comments

Comment · 3 years ago

Been working on one since last year https://glue.im/noah

Comment · 4 years ago

Crystalist?

See https://en.m.wiktionary.org/wiki/Rubyist

Comment · 4 years ago

Currently building a back-end API with Kemal, highly recommend. Also has easy to use websocket events built-in.

Comment · 4 years ago

Can speak to the DB side of things: Redis in front of an RDBMS scaled well for me at https://glue.im/noah

Timlines/activity are built from the RDBMS and served from Redis as a cache. New posts are added to the cache directly as well so only needs to rebuild if you lose the entire cache which only happens if we need to restart the server. Also not storing full posts in Redis, just IDs, pulling via primary key from DB is very fast.

That same setup was used for a previous app that had a few million user base (don’t remember the concurrent user numbers though) and it ran well with a clear path to scale it up.

More thoughts: build a mobile friendly web app first, you’re gonna need some sort of back-end to run the iOS app anyways and tweaking a web app UI is much quicker than resubmitting iOS builds to the App Store.

Comment · 4 years ago

They’re all good to try IMO, another is https://kemalcr.com which is akin to Sinatra if you just want to get an HTTP server with routes setup quickly.