Live data from Hacker News

Punchfork shutdown inspires Open Recipes

blog.fictivekin.com

41–50 of 60 posts

Re: Punchfork shutdown inspires Open Recipes

#41
I long ago stopped replying to posts and comments that anger me for their negativity and bullshit, but none has made me as furious as this one.

Disclaimer: After reaching out to him cold, Jeff Miller was an informal advisor to me for over a year providing valuable insights and advice, not to mention moral support, as we built our company. He did this for no reason other than his dedication to helping a fellow entrepreneur. Over dozens of email exchanges and in-person get togethers, he proved hands down, to be one of the most helpful, friendly, altruistic people I've met in the valley. After a year building up this friendship and trust, he invested in our company, and he is consistently one of the first people I reach out to when I have real founder issues to discuss.

The OP has literally ZERO idea what reasons Jeff has for his decisions about the data on his site, not the least of which could be legal restrictions of the acquisition. They provided, what looks like, ZERO background on why they wanted to talk to someone who was incredibly busy transitioning a startup into the hands of a new parent company. Jeff was as polite as he needed to be when he responded to a completely context-less request for a call with, "I'm sorry I can't right now." The OP does not know, beyond building a startup worth acquiring, and transitioning it, what else someone might have on their plate that would prevent them from having time to chat with someone who failed to provide any reason for their request. Then, when Jeff asked point blank whether the OP was scraping data from his site, they responded with an ambiguous, "not trying to do anything uncool. Still super eager to talk more. Happy to do so anytime."

The OP apparently does not have to try to do something uncool. This entire situation is unbelievably uncool, from the beginning of the communication, to their actions in between, to this post. The only thing more shocking than the sense of entitlement displayed here, is that they, or anybody here, thinks this post documents anything other than a pure display of arrogance and entitlement by the OP. They approached this whole situation with such a stark lack of professionalism that it would be laughable if they hadn't also decided to smear one of the nicest people I know in the process.

This post reflects an attitude that is a shining example of so many things wrong in the startup community, from the sense of entitlement, to the lack of common courtesy, to the manipulation of a situation for personal gain at the expense of others. It is so unreal how easily people seek to tear down others, and worse, how quickly smart people jump on the bullshit bandwagon.

This post is a joke. Nobody owes you anything because they built a site you enjoyed. If anybody owes anybody anything, the OP owes Jeff Miller an apology for this time wasting bullshit.

Re: Punchfork shutdown inspires Open Recipes

#42
Interesting that this is written by one half of the Analog Folk/Fictive Kin co-op.

These guys are responsible for Mapalong, a (formally great) mapping service that they abandoned early last year and for which they ignore any requests for exported data (I've been asking for a .KML file for a year to move my points somewhere else).

Re: Punchfork shutdown inspires Open Recipes

#43
post #7

Startups that are based on user-contributed content are based on fraud in the sense that they imply to their users that the contributed data will always be available. But it's a lie, the user's data is only being used to explore a potential market. If the market idea proves successful the company will be sold and shutdown. If the idea is unsuccessful it will also be shutdown. Startups should be required to tell users…

While I don't think forcing private companies to reveal this information is right, a legal requirement to support data exports (including for up to 30 days after the announcement of a closure) seems in society's interest.

Re: Punchfork shutdown inspires Open Recipes

#45
post #3

I could see posthaven turning into an API that any site could integrate with so that users knew their data was safe. Depending on the site and type of user data, this type of exportability/backupability could be a real differentiating feature.

Idea: a browser extension that automatically scrapes and archives your data as you browse a site. Power-users can submit scrapers for new/modified sites. Normally scrapers can be detected and blocked, but if it's passively running in the background on a user's machine, opportunistically grabbing data the user is already viewing, it should be impossible to detect.

Related: Consider http://Pinboard.in with the yearly plan offering Personal Archiving. Anything pinned (bookmarked) gets archived and you can view it from your personal archive.

Re: Punchfork shutdown inspires Open Recipes

#46

I long ago stopped replying to posts and comments that anger me for their negativity and bullshit, but none has made me as furious as this one. Disclaimer: After reaching out to him cold, Jeff Miller was an informal advisor to me for over a year providing valuable insights and advice, not to mention moral support, as we built our company. He did this for no reason other than his dedication to helping a fellow entrepr…

This post reflects an attitude that is a shining example of so many things wrong in the startup community, from the sense of entitlement...

Well, yes, when you invest in your data, you feel entitled to it. I would argue you are entitled to it.

Which is why Advection, as a streaming VOD provider, has maintained -- at our own expense -- license servers for users who bought movies from content owners that went out of business up to a decade ago. We believe in digital ownership, and believe that non-evaporative content principles are good for the whole ecosystem.

I applaud any archiving efforts that help end users have a greater sense of trust in future digital products.

Re: Punchfork shutdown inspires Open Recipes

#47
post #3

I could see posthaven turning into an API that any site could integrate with so that users knew their data was safe. Depending on the site and type of user data, this type of exportability/backupability could be a real differentiating feature.

Idea: a browser extension that automatically scrapes and archives your data as you browse a site. Power-users can submit scrapers for new/modified sites. Normally scrapers can be detected and blocked, but if it's passively running in the background on a user's machine, opportunistically grabbing data the user is already viewing, it should be impossible to detect.

I dig it. Store this data in the cloud and call it ViewHaven. An automatic and complete record of everything you've seen on the web.

Re: Punchfork shutdown inspires Open Recipes

#48
post #42

Interesting that this is written by one half of the Analog Folk/Fictive Kin co-op. These guys are responsible for Mapalong, a (formally great) mapping service that they abandoned early last year and for which they ignore any requests for exported data (I've been asking for a .KML file for a year to move my points somewhere else).

Mapalong is still in private beta, but it's otherwise alive and well. It's a huge bummer that you think otherwise. I'm sure you're not alone.

We have had to pause development, but not only is your data still there, you can still use it. New users can't join, but that's about it.

As soon as we're able, we want to finish it and launch it. As part of this, we'll make sure people can get their data out in useful formats. (Perhaps a GeoRSS feed per URL? A KML file per user?)

I genuinely respect you for holding us to a high standard, but I think it's a little unfair to criticize us for an unfinished app.

Re: Punchfork shutdown inspires Open Recipes

#49
post #42

Interesting that this is written by one half of the Analog Folk/Fictive Kin co-op. These guys are responsible for Mapalong, a (formally great) mapping service that they abandoned early last year and for which they ignore any requests for exported data (I've been asking for a .KML file for a year to move my points somewhere else).

Mapalong is still in private beta, but it's otherwise alive and well. It's a huge bummer that you think otherwise. I'm sure you're not alone. We have had to pause development, but not only is your data still there, you can still use it. New users can't join, but that's about it. As soon as we're able, we want to finish it and launch it. As part of this, we'll make sure people can get their data out in useful formats.…

I'm sorry if you feel it's unfair, but it's hard not to jump to such conclusions when the Twitter account is dead and nothing (visibly) changes.

It would certainly make people feel better if, with slowly progressing software, it was made easier for these testers to feel like they could properly test such software with the full knowledge that they can get their investment out in the form of a reasonable export function - they are after all providing a service to you by testing the software and providing feedback.

Re: Punchfork shutdown inspires Open Recipes

#50
post #49

Earlier quoted context omitted.

Mapalong is still in private beta, but it's otherwise alive and well. It's a huge bummer that you think otherwise. I'm sure you're not alone. We have had to pause development, but not only is your data still there, you can still use it. New users can't join, but that's about it. As soon as we're able, we want to finish it and launch it. As part of this, we'll make sure people can get their data out in useful formats.…

I'm sorry if you feel it's unfair, but it's hard not to jump to such conclusions when the Twitter account is dead and nothing (visibly) changes. It would certainly make people feel better if, with slowly progressing software, it was made easier for these testers to feel like they could properly test such software with the full knowledge that they can get their investment out in the form of a reasonable export functio…

It's cool. Like I said, I'm sure you're not alone.

Also, you make a very good point. We never expected to have to pause, but we should have put more focus on making sure people never felt their data was trapped, even in the very beginning.

In fact, you've managed to convince me that proper data export should be the very next feature we add.

Post reply on HN