No 'serious hindrance' involved.
818 karma · joined February 17, 2008
No 'serious hindrance' involved.
Luckily there's an escape hatch in this case: Cog Menu -> "Use Classic Look"
Of course sites that work within the PRC system of government censorship tend to stay unblocked. ;)
If you were hit with an actual patent claim, the first question you ask is what is the patent # and which specific claims are they referencing. Then go back to any referenced patents and see if the claims are unique to the new patent. Of the unique claims then you can make a case if your product infringes or not.
If the product is SaaS you have the ultimate power to resolve non-payment: stop service.
Just send a polite note to their accounts payable team or whomever is your main contact say "We really love you as a customer, but our invoice is overdue and forcing an automatic stop of service on XXX, XXXX (30 days from today). We really don't wish to loose your firm as a customer. Please contact us as soon as possible so we can avoid a service interruption" Make sure the subject says something like "30 days notice: Automatic Stop of Service on XXXX for non-payment" They should jump to action. If not, remind them again in 2 weeks, then if no action stop the service.
If your service is important to them, you'll be impressed at how quickly things get paid.
Curious if this is platform specific.
Can you switch to dev and let me know what results you get? If different than a new bug is warranted.
Any thoughts on Oauth2 and Facebook Graph support?
[edit: a famous bit of company-is-a-feature carnage for reference: STAC vs. Microsoft: http://en.wikipedia.org/wiki/Stac_Electronics ]
Which makes me wonder why Matt can't get this championed internally or for someone's 20% project?
re: soundcloud
Consider removing the reference to soundcloud. The best it can do is give give the lawyers an excuse to go after you for UI Copyright infringement.
re: value prop
The intro page does a good job motivating someone to use the product, but the homepage doesn't help sell the product at all. See if you can summarize the pain points on the homepage.
Also consider putting up a forum for musicians to collaborate/share/find each other (ala FLStudio Looptalk). The fastest way to get people to use a sharing product is to help them have people to collaborate with ;)
Good luck!
1) Fix graph.facebook.com to respect user permissions. graph.facebook.com/userid publicly leaks real names and UIDs even when users ask to be non-publicly searchable. This is creepy and makes users nervous that they don't have control over their privacy.
2) Give users back granular control to explicitly disallow sharing of any info they wish to keep private. This includes their friends graph, likes, wall access, etc. (empowering them to have the choice will reduce the sense of lack of control).
3) Let the application/site owners describe what they intend to use the information for. Ideally hold the app to the contract as well. example: "Need access to your wall in case you explicitly tell us to publish/share something on your behalf - we will never post to your wall without your approval".
Anecdotal story:
I showed someone Quora 2 nights ago as suggested they sign up. She said "Why do they need my Facebook? No way!". When asked "why?", she said, "I don't want that site spamming my wall - who are they?".
My takeaway: If Facebook wants to be the login for the web, it needs to give people comfort that they have control over how an app/site behaves on their behalf.
If you take a look at gmail in a debugger you'll see there are 4 iframes. The controller is the 'js_frame', the 'canvas' contains the graphic UI elements.
Leaving the canvas in its own iframe allows it to be reloaded separately without affecting application state.
Javascript still modifies the canvas iframe DOM. But that modification is cross-frame from the controller iframe.
I used a similar frame-based technique back in '97 when our enterprise startup needed a snappy native-looking zero-deploy UI.
If you just want the look and feel of Gmail, there are plenty of frameworks referenced in the comments (Cappucinno, YUI2, Sencha, etc) that can give you the basic layout. But if you want the mimic the speed/functionality, it'll require getting dirty with Javascript controller design in the browser.
On RWW Start the startups with exits are the headline grabbers. Delicious carries much more clickthrough appeal/legitimacy than AOL. Always lead with a grabber.
Congrats mate. If I was still investing I'd join y'all.
It's the unpredictability of the system (people holding doors, elevators going out of service, faulty mechanical switches, etc) that makes the algorithm design fun.
Feel free to ask me anything. I used to design elevator group dispatch systems as a side job in college.
That'll solve your prototype challenge too, since it's already done.
Email me if you want an intro (contact info in my profile).
Combine that with the positive 'word of mouth' I've encountered so far from non-technical types and it's possible we haven't seen the knee of the curve yet in adoption growth.
Blog wise: Bubble up some of the great activity going on behind the scenes. Design decisions, great implementation debates, calls for help on hard/easy problems, new releases, beta releases, testing calls, etc. The posts don't have to be more than a paragraph or two. Just enough so we can see where you guys are steering the ship and if there's something we can do to help.
I'm sure there are more than a handful of potential up and coming language implementers that Rubinius could help inspire and recruit. All it takes is an easy to find/read active conversation to get them engaged.
Also, I'm sure you're thinking about a 'the long road to 1.0' post. That would be great first post to talk about all the decisions and direction changes that lead up to the current design.
Now that 1.0 is out, how about adding a blog and a mailing list?
I'd love to see Rubinius pick up a large following. IRC-only makes it a challenge to build a thriving community.
One question is why dogster.com, who was clearly the leader, shifted direction towards being more of a portal and less of a dating site.
Today it seems you're a consultant/service-provider.
Although not original, your breakfasts may be good. Just please for the sake of our patience, call out your conflict of interest when posting here. There are many charming ways to do it. Denial or dismissal isn't one of them.
If someone calls you on a conflict of interest and there's even a remote chance there might be a conflict, just say something like: "Forgive my oversight. ...". Then graciously move on.
You run a consulting firm that feeds on startups.
Your breakfasts are a marketing/leadgen program. That's fine if you call it out, but you're deluding yourself if you try to claim it's a community service. It may benefit the community as a side effect, but that's not why you do them.
ProTip: When you have a conflict of interest, call it out upfront. Anything less dilutes your legitimacy.