Skip to content
This repository has been archived by the owner on Feb 8, 2018. It is now read-only.

rename toots to ... anything #1075

Closed
chadwhitacre opened this issue Jun 24, 2013 · 17 comments
Closed

rename toots to ... anything #1075

chadwhitacre opened this issue Jun 24, 2013 · 17 comments

Comments

@chadwhitacre
Copy link
Contributor

What was I thinking?

@chadwhitacre
Copy link
Contributor Author

Or just drop it and integrate more tightly with Twitter? I'm so torn!

@ehmatthes
Copy link

I haven't used it yet, but something within gittip sounds useful. I never use features on one site that require broadcasting to external sites such as twitter and facebook.

I agree completely on the name change.

@DamosDaze
Copy link

Well the site is called gitTIP. How bout calling them hattips? ;)


Damien Michael Nichols
[email protected]
301.485.9232

Sent from my HAL 9000, Dave.
On Jun 25, 2013 10:25 AM, "Eric Matthes" [email protected] wrote:

I haven't used it yet, but something within gittip sounds useful. I never
use features on one site that require broadcasting to external sites such
as twitter and facebook.

I agree completely on the name change.


Reply to this email directly or view it on GitHubhttps://github.com//issues/1075#issuecomment-19979537
.

@cattsmall
Copy link

Is the purpose of a toot supposed to be like tooting your own horn? Or a hattip like @DamosDaze suggests?

@chadwhitacre
Copy link
Contributor Author

@cattsmall The purpose is to toot your own horn and the horns of others. It's a way to tell the rest of us about the awesome stuff you do, and a way for the rest of us to thank and encourage you.

@timothyfcook
Copy link
Contributor

There's really two separate purposes here:

  1. Let gittipees LOG their progress, so that supporters can see what they're working on.
  2. Let supporters THANK folks working on great projects by leaving them some written encouragement. This could be in response to a recent LOG posting or as an isolated thread.

Example:
"The Gittip Team just launched the new Teams functions check it out here: https://medium.com/building-gittip"
In early talks, this function was supposed to enable a form of accountability, and a past/present/future log or portfolio of what folks are producing that is of value/interest to their gittip supporters.


Here's an idea on some new language:

Just call it "The Book" or "Logbook" or just "Log"

Both parties (supporters and recipients) can "Write in The Book" or "Leave a Note". I also like the idea of supporters being able to give Heart-Coins (as a sort of +1) to recipients in response to their updates. I would Heart-Coin your recent update on adding the Team functionality.

Recipients can write a short log of a recent project; supporters can write encouraging thank you notes and Heart-Coin things.

Functionally it's kind of like a guestbook/mini-blog. It's not very different than Facebook's "Wall" although now, it seems, that the content of Horn (Book) postings are only viewable by the Horn's owner; that seems like fine logic moving forward, as long as the public can see that others have left notes/heart-coins.

Being able to see that others have encouraged/hearted something would make me feel good about supporting something/someone that sounds cool, if I don't know the person.

@chadwhitacre
Copy link
Contributor Author

Or maybe we should just make it bone-simple and call it "Updates" and allow comments as our "thank you" outlet. I do like the heart-coin idea though.

@chadwhitacre
Copy link
Contributor Author

@tshepang
Copy link
Contributor

tshepang commented Jul 9, 2013

@whit537 great humor; thanks

@singpolyma
Copy link

I don't really see the point of this feature. Links to social media profiles you already have seems more productive.

@timothyfcook
Copy link
Contributor

I think the feature has serious value; a feed of someone's twitter profile
could be full of all sorts of content. It seems important for Gittip
supporters to be able to have a consistent mini-news feed of projects that
people are working on that deserve Gittip support and/or work they've been
enabled to do because of Gittip support.

On Wed, Jul 10, 2013 at 5:32 PM, Stephen Paul Weber <
[email protected]> wrote:

I don't really see the point of this feature. Links to social media
profiles you already have seems more productive.


Reply to this email directly or view it on GitHubhttps://github.com//issues/1075#issuecomment-20774985
.

@mvdkleijn
Copy link
Contributor

I think the "toot your own horn" idea as a way of providing simple updates to givers is nice.. I agree the name should be changed though. It feel unnecessarily self-promoting now... just updates is fine thanks.

@timothyfcook & @whit537 Please also see my issue #1323 where I suggest (amongst others) to have a pull in data from twitter based on a hash tag the receiver can set. (allowing for targeted tweets)

@chadwhitacre
Copy link
Contributor Author

"Tooting one's own horns" is mentioned in this review of Design to Thrive: Creating Social Networks and Online Communities that Last.

@untitaker
Copy link

How about making it a comments section for profiles?

@untitaker
Copy link

Or renaming it to "{username} is making the world better by..."

@cakey
Copy link
Contributor

cakey commented Sep 4, 2013

My idea for the horn:

  • Create connections between givers and receivers.
  • Stay anonymous
  • Reasons to use it over existing social platforms

I believe anonymous 'tip notes' are the way to do this. Each person who tips can leave an optional short message. This collection of messages is displayed prominently on the receivers profile. The collection creates a relationship, gives the receiver satisfaction and knowledge of what is being rewarded, and signals to the rest of the community the type of awesome work that the receiver is doing.

This serves as a solution to #1328 and improves #1323.

@chadwhitacre
Copy link
Contributor Author

#1466

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

10 participants