mmalone's dashboard

mmalone replied on December 19, 2008 03:44 to the update "Pownce Read-only Archive" in Pownce:

@WolvenSpectre, yep! We've been talking to the Internet Archive, and hopefully we'll be able to work something out. Glad to hear others think its a good idea though!

mmalone replied on December 18, 2008 17:11 to the question "Export link is a 404/Ackbar error?" in Pownce:

Awesome. Wouldn't have expected you to figure that one out, it took me a few minutes to realize what the problem was and I know exactly what's going on :). Anyways, glad it worked!

mmalone posted an update in Pownce on December 17, 2008 00:52:

Pownce Read-only Archive

We've made a temporary read-only version of Pownce public notes available for archival purposes. We did this in response to user requests, and because we understand and believe in the importance of permalinks on the web.

So we're giving people the opportunity to create an archival copy of Pownce data. Read-only data will be available until at least January 1, 2009. Feel free to archive parts of the site, but if you're going to do anything large scale please let us know!

We'd also like to thank Ben Ward (http://getsatisfaction.com/pownce/top...) and Tantek Çelik (http://twitter.com/t/statuses/1032944132) for their thoughtful comments and help on this project.

mmalone replied on December 15, 2008 19:48 to the question "Export link is a 404/Ackbar error?" in Pownce:

Hey Matt, looks like you've run into a bug we recently discovered w/ secret keys. Try going to http://pownce.com/settings/secret_key/ and clicking "Change Key," then head back over to http://pownce.com/settings/export and it should work.

mmalone replied on December 10, 2008 17:13 to the question "Anyone received their export file yet?" in Pownce:

Six Apart has agreed to keep our S3 bucket up and running for at least a year. Public files have been moved over to a public S3 bucket (at http://media.pownce.com) and export files reference the copies stored in that public bucket. Private files will remain in Pownce's private S3 bucket, and your export contains private URLs generated to access those files for one year.

@djp, sorry for the delay with your export - I investigated a bit more and it looks like your inbox is extremely large and it was causing our export script to crash. I'll go ahead and generate the rest of the export files for you (you should receive another email) and will try to make some improvements to our export script in order to create an export of your inbox as well.

mmalone replied on December 10, 2008 03:52 to the problem "export ... sigh.... don't work." in Pownce:

DJ Paine: is your username 'djp'? If so, it looks like your export hasn't been processed yet (it's in the queue and will probably be done a little later tonight). I'm not sure why you got an email saying it had completed... sorry about that :/.

Heidi: you shouldn't share your export URL. The URLs contain a secret key so that import tools can access it without having to log in. Unfortunately, that means that others can view the page too if they know your secret key (the keys aren't guessable, so they're secure as long as you don't share them with anyone). If you share you secret key with someone and want to change it you can do so at http://pownce.com/settings/secret_key/

mmalone replied on December 09, 2008 23:13 to the question "Anyone received their export file yet?" in Pownce:

Ajit, once your export is generated you'll be able to download all the notes you've sent (with comments) and all the notes in your inbox (with comments) in "Pownce XML" format (the same format we use to return notes via the API, documented at http://pownce.pbwiki.com/API%20Docume...). You'll also be able to download all sent notes with comments as an MTIF file (non-public notes will be stored as draft posts). In addition, there are three ATOM feeds: public sent notes, sent notes (with the Six Apart's privacy extension), and comments. Finally, we're generating a static FOAF file with your relationship data.

Hope that helps!

mmalone replied on October 02, 2008 21:54 to the question "What's up with the YouTube display?" in Pownce:

Hey, this looks like a problem with YouTube. You should post it over at http://getsatisfaction.com/youtube

mmalone replied on September 24, 2008 23:38 to the problem "Location privacy not working with FireEagle" in Pownce:

@V All valid points. However, the Fire Eagle location feature works perfectly well for users who are comfortable sharing their location with the public (many are). Therefore, we made the decision to go ahead with the feature in it's current state (in part because we wanted to solicit feedback from the community and see what adoption would be like and how the feature would be used).

Like I said, the separation between privacy controls for permanent location and Fire Eagle location was an intentional design decision, and is not a bug. As such, adding additional privacy settings is a feature request, and will likely be implemented once we have resources available to implement it properly.

As an interim solution, Leah has added some language on the Fire Eagle account setup page that makes it clear to users that their Fire Eagle location information will be publicly available (this will go out with our next code push). We do appreciate your feedback, and take privacy matters very seriously. Again, I'm very sorry that the privacy policy w/ regards to Fire Eagle was not clear to you from the beginning.

mmalone replied on September 24, 2008 22:32 to the problem "Location privacy not working with FireEagle" in Pownce:

@V, I'm sorry you feel like we're disregarding privacy information. We're sensitive to privacy, and we try hard to make things clear to users. In this particular case, we view Fire Eagle (current/transient) location and Pownce (where I'm from/permanent) location as separate features, and therefore manage privacy for them differently.

We have discussed more robust privacy controls for your Fire Eagle location, but it's not quite as simple as it seems. First, the straightforward lookup of privacy information on a per-note basis may be trivial to implement, but scaling it on Pownce's infrastructure to handle many thousands of notes per second is not quite so trivial. A proper implementation will require a bit more planning, and unfortunately we haven't gotten to the point where we can devote resources to this task just yet.

It would also be nice if users could specify location granularity for friends/fans/public. Again, this is something that would require some careful thought before implementing.

Keep in mind that the Fire Eagle location feature is still relatively new. We're carefully considering suggestions and feedback from the community, and you will likely see some tweaks in the future.

mmalone replied on August 27, 2008 23:28 to the problem "Pownce FAQ pop-ups not showing" in Pownce:

Oops, we just switched from prototype to jQuery and it looks like I missed some stuff on that page. I'll take care of it and check it in with the next push. Thanks for the heads up!

mmalone replied on August 20, 2008 05:09 to the problem "Is anyone else getting an email every 3 minutes?" in Pownce:

Not sure why you got more than one... that's weird. Sorry man!

Like Daniel said, if anyone else is having this problem please let us know so we can take care of it!

mmalone replied on August 19, 2008 05:08 to the problem "Pownce couldn't connect me to Fire Eagle" in Pownce:

Fire Eagle apparently had a little hiccup and is rate limiting us right now. I just talked to someone from their team and he's going to try to remove the rate limit as soon as he can, but everyone's home right now so it might not be until tomorrow morning.

mmalone replied on August 14, 2008 00:01 to the problem "fireeagle support appears broken" in Pownce:

Hey, it sounds like you may have run into a caching issue what we're currently working on resolving. Pownce is caching your current location for approximately 15 minutes. So after you update Fire Eagle it could take up to 15 minutes for your location to update on Pownce.

We're working on a fix that will update your current location on Pownce if you update your Fire Eagle location via Pownce. In order to make this work, some changes need to be made to the Fire Eagle API. We're working with the Fire Eagle team to get this resolved, and hope to roll out a fix soon.

mmalone replied on August 13, 2008 23:36 to the problem "Location privacy not working with FireEagle" in Pownce:

Unfortunately the only options for Fire Eagle integration at the moment are "on" or "off". You can set the granularity of the location information Pownce has access to via Fire Eagle, and the new settings should take affect the next time Pownce fetches your location. This can take up to 15 minutes, which is probably why you continued to see your exact location displayed after changing your Fire Eagle settings.

We are discussing additional privacy options that we may implement in the future. It's a complicated problem to solve properly. Since your Fire Eagle location doesn't just show up on your profile, we'd need to conditionally attach your location to notes.

So, Definitely keep an eye out for additional privacy settings in the future. In the mean time I'd recommend re-linking your Fire Eagle account and setting the granularity to city only. If Pownce doesn't update to display your city level location within 15 minutes please report back and I'll take another look.

Thanks!

mmalone replied on August 03, 2008 18:24 to the question "I have a friend request that doesn't exist." in Pownce:

Looks like you found a new bug! I've fixed this for your account, and I'm filing a ticket to implement a more general solution. Thanks for the feedback, and please respond if the problem continues.

mmalone replied on July 29, 2008 18:11 to the question "Can't authorize Pownce app for iPhone." in Pownce:

A recent code push broke the mobile site. I just rolled out a fix, so it should work now! Sorry about that.

mmalone replied on July 15, 2008 17:25 to the problem "Why does Pownce keep killing kittens with the password anti-pattern?" in Pownce:

We're working on switching over to data APIs that don't force us to handle user secrets. It's on our short list of things to do in the near future. Hopefully it will get done in the next couple of weeks.

mmalone replied on July 11, 2008 06:41 to the idea "OpenID Support" in Pownce:

Stephen, it does make sense. OpenID is used to authenticate on site A using credentials stored on site B. OAuth lets you authorize access to site A using credentials stored on site B. The two standards have many overlapping use cases.

In any case, implementing OpenID is non-trivial as it require significant changes to our auth system, login flow, and usernames. As Ariel said, we are involved in both the OAuth and OpenID communities and we're actively participating in discussions re: a proposed merger of the standards. Until some consensus/stability is reached on the scope/overlap of the two standards we won't be implementing OpenID. If things change in the future we may re-assess the situation.

mmalone replied on April 17, 2008 06:12 to the problem "Error 500" in Pownce:

Hey everyone. We're really sorry for the delay getting this fixed, it was a tough one to track down. We just released some new code that should fix this issue.

If you're still having problems please let us know by posting a response along with your Pownce username here.