Abraham Williams's dashboard

poseurtech asked a question in Twitter on March 31, 2009 09:57:

When is Twitter going to start releasing inactive accounts?

People used to be able to email username@twitter.com to get an inactive account released. This no longer is supported though. Instead an email is sent specifiying:

[...] you'll have to wait until all inactive user names are released.

I would like to have a username that was registered in 2007 and has no updates.
Is there a timeframe we can expect or is this a lost cause?

poseurtech started following the question "Deleting unused accounts" in Twitter.

poseurtech started following the question "How do I take over an inactive Twitter account?" in Twitter.

poseurtech started following the question "Can an inactive Twitter page/username be removed by request? Or even a request be sent to the current inactive owner?" in Twitter.

poseurtech started following the idea "Automatic OAuth redirect once an application is authorized" in Twitter.

poseurtech started following the problem "Inactive Username" in Twitter.

poseurtech replied on March 10, 2009 14:09 to the idea "Unique project email address for filters" in Pivotal Labs:

NP :). I don't think I was clear either.

From Gmail's perspective there is negligible change in usability of using project name/id in the from name as apposed to having it in the email subject. Where as unique reply-to addresses drop clicks for creating filters.

I pretty much exclusively use Gmail so I don't know it there is a usability increase for other clients.

A comment on the idea "Unique project email address for filters" in Pivotal Labs:

I'm not really familiar with getting email address verified but I assume there are methods of pragmatically adding new ones. Is there a technical or financial reason there can't be a verified email address for each project? – poseurtech, on March 10, 2009 11:47

poseurtech replied on March 10, 2009 11:45 to the idea "Unique project email address for filters" in Pivotal Labs:

From Gmail's standpoint I don't think the name is any easier then the subject.

poseurtech replied on March 10, 2009 03:24 to the idea "Unique project email address for filters" in Pivotal Labs:

Ok. Well a work around is to filter off of both the email address and project name in the subject. There would be issues if you are in 2 projects with the same name though.

A comment on the question "Socialthing! does not need the ability to delete Flickr photos." in Socialthing:

It is possible and quite easy to have write only permission.

From Flickr's specs:

5. Authentication permissions

An application should never request more permissions than it needs to operate. The permissions field is a string, representing the permission level. Each level implies the level below it. Possible permissions are:

* read - permission to read private information
* write - permission to add, edit and delete photo metadata (includes 'read')
* delete - permission to delete photos (includes 'write' and 'read')

For example, the permission w allows an application to read and write on behalf of the user.

http://www.flickr.com/services/api/au... – poseurtech, on March 08, 2009 07:25

poseurtech reported a problem in Pivotal Labs on March 08, 2009 07:19:

Individual stories from public projects are not public.

Example:

Public project: http://www.pivotaltracker.com/project...

Single story in project: http://www.pivotaltracker.com/story/s...

The individual story link gets redirected to the global homepage.

poseurtech shared an idea in Pivotal Labs on March 07, 2009 20:50:

Unique project email address for filters

It would be awesome if emails from projects had unique addresses. Currently emails come from "tracker-noreply@pivotallabs.com" It would be nice if it was "story126-10203@pivotallabs.com" (projectName-projectID). This makes gmail filters a lot more useful.

poseurtech started following the idea "Gravatar Support?" in Twitter.

poseurtech started following the question "im" in Twitter.

poseurtech replied on February 21, 2009 00:39 to the question "Why is Brightkite asking for delete permissions on flickr?" in Brightkite:

Awesome. Thanks!

poseurtech marked one of Lesley's replies in Brightkite as useful. Lesley replied to the question "Why is Brightkite asking for delete permissions on flickr?".

poseurtech started following the question "Will there be an android application, and when?" in Brightkite.

poseurtech started following the question "OpenMicroBlogging spec" in Twitter.

poseurtech asked a question in Brightkite on February 20, 2009 07:38:

Why is Brightkite asking for delete permissions on flickr?

There is no reason BK should be asking for delete permissions on Flickr. Flickr has excellent levels of read, read/write, and read/write/delete.

From Flickr's specs:

5. Authentication permissions

An application should never request more permissions than it needs to operate. The permissions field is a string, representing the permission level. Each level implies the level below it. Possible permissions are:

* read - permission to read private information
* write - permission to add, edit and delete photo metadata (includes 'read')
* delete - permission to delete photos (includes 'write' and 'read')

For example, the permission w allows an application to read and write on behalf of the user.

http://www.flickr.com/services/api/au...