What Twitter's IPO Means

http://qz.com/140197/what-twitters-ipo-means/ #socialmedia #startup

"Not a word about last month’s wildly successful IPO by Potbelly, a 36-year-old sandwich purveyor that actually makes money."

"Nothing about the Container Store, which went public last week and promptly doubled in value thanks to enthusiasm for ingenious home organization products."

http://www.slideshare.net/adamnash/personal-finance-for-engineers-twitter-2013

http://finance.yahoo.com/news/potbelly-shares-double-ipo-142516400.html

---

Thinking about something different instead of doing this, which is using the "reply" feature to add quotes from a story or related links.

http://jothut.com/cgi-bin/junco.pl/replies/19772

Social features that exist in the Junco code, powering JotHut includes:

• multiple user account creation (disabled)
• following users
• following tags
• replies
• webmentions, which are a form of replies

If I want to remove the social features, then I would need to change how I add info to a microblog/note post.

I've been using the "reply" function in an unintended way at JotHut. I like creating related microblog posts with the reply function. It makes it easier to view the posts within the same thread or on the same page.

Sometimes, I add a related microblog/note to an old microblog/note with the reply function.

Instead of trying to find and read the related notes on the stream page, which displays posts from youngest to oldest, I can click on the thread link for one of the related replies, and I see all the notes displayed on one page in order from oldest to newest.

And if I removed the reply function, I would need to support webmentions differently. I would probably have to create a webmentions database table to store the content and the id of the target post being replied to.

The content table stores info per a user id. I guess I could keep the multi-user account creation function and process webmentions as I do now. But that basically means the reply function remains, although I could hide/remove the reply link, so that I cannot manually use the reply function.

I'm guessing that I'll keep following and reply functions a little longer. It will be easier to decouple the code that supports the following functions. The reply code is a bit more ingrained in modules and templates.

Maybe this winter when I'm in a code-trimming mood, then I'll consider purging the code, provided I enable a different way to add to a microblog post.

I could add a feature where an existing microblog post is expanded/changed to a blog post.
#juncotodo