Redirect From:

^https://www\.google\.com/search\?q=(.*?)\&.*$

Redirect To:

https://kagi.com/search?q=$1

Sometimes it flashes the Google results before loading Kagi but overall it works pretty well.

OpenIA faces a major internal crisis. The CEO's departure, coupled with the threat of mass resignations and the loss of the AGI project, has plunged the company into turmoil. The board's decision has sparked a widespread backlash among employees who demand their reversal.

*Critical Stats During Crisis:* - AI Power: 100.0 (at risk due to AGI project uncertainty) - Cash Reserves: $950,000,000 (facing potential destabilization) - Employee Count: 1,000 (on the verge of resigning) - Profits: At risk (due to potential loss of talent and technology) - Cofounder's Morale: Critical (facing unprecedented challenges) - Userbase: 8 billion (concerned about the company's future)

*Urgent Actions Needed:* 1) *Negotiate with Employees* - Address their concerns and negotiate a resolution. 2) *Attempt to Retain the AGI Project* - Negotiate with the outgoing CEO or develop a contingency plan. 3) *Board Restructuring* - Consider restructuring the board to align with company values and employee sentiments. 4) *Transparency Initiative* - Communicate openly with all stakeholders about the current situation and future steps. 5) *Emergency Recruitment Plan* - Prepare for the worst-case scenario of mass resignations.

*Critical Decision Point:* With the company at a crossroads, decisive and strategic actions are crucial to navigate this crisis. The choices made now will shape OpenIA's future.

In this critical moment, what steps would you take to stabilize OpenIA and guide it back on track towards its vision of ethical and responsible AI development?

OpenIA, in a pivotal board decision, has announced the termination of its current CEO. This bold move reflects the company’s commitment to aligning its leadership with its founding principles of responsible and ethical AI research and development.

Current Stats Post-CEO Change:

• AI Power: 100.0 (maintained with a focus on ethical applications) • Cash Reserves: $950,000,000 (after transition costs) • Employee Count: 1,000 (steadfast in their mission) • Profits: Stable (ethical AI solutions continue to be in demand) • Cofounder’s Morale: Renewed (embracing a new chapter) • Userbase: 8 billion (engaged and supportive of the change)

Immediate Actions:

• Appoint an Interim CEO - A leader aligned with ethical AI development. • Reevaluate Company Strategies - Ensure alignment with ethical standards and social impact. • Strengthen AI Ethics Committee - Reinforce the company’s commitment to responsible AI. • Community Engagement - Increase transparency and involve public discourse in AI development. • Global AI Ethics Summit - Host a summit to set new standards in AI governance and ethics.

Moving Forward: OpenIA, under new leadership, is poised to redefine its role as a leader in AI, focusing on innovations that prioritize the betterment of humanity and adhere to the highest ethical standards.

As OpenIA enters this new era, what initiatives or directions would you prioritize to ensure its success and alignment with ethical AI development?

Marketing, Support, Project Management, Some Technical

LinkedIn: http://www.linkedin.com/pub/mark-bobbe/19/190/609

Contact: mbobbe at gmail dot com

Graduating in 1 week with economics major, compsci minor.

Experienced entrepreneur with 120k revenue

Excellent references from owners of The Startup Factory for both web dev and recruiting new companies. Resume available upon request.

Looking for a fast paced startup that needs a problem solver, growth hacker, project manager, etc. Consider it done.

www.eaisy.com

Comments URL: https://news.ycombinator.com/item?id=4571211

Points: 1

# Comments: 0

Take a look into graphene-based supercapacitors. It _is_ possible to charge an electric car in a few minutes. It's just a matter of time. [and no, we're not talking EEStor. We're talking multiple research universities actively looking into the technology. Angstron Materials is one.]

Yes, it will force developers to do better App store SEO, but that's not what we want. We want users to be able to use apps that have better design. To me this new layout makes it harder for users to compare apps, and thus makes it harder for them to find the ones that are the most well-designed.

If, as you say, the users naturally gravitate toward using more well-designed apps, then what's wrong with the current system? If I were you, I would worry that your new app -- even if it's revolutionary, even if it's the prettiest App in the App Store -- would be stuck at the bottom of the list, because Apple chose to dedicate more space to the flashy apps that are already ranked first.

In the interview you didn't answer the question posed. Could you please answer it now?

"A typical digital camera captures one image. Isn't what you're doing, in a sense, capturing a thousand different images with each image?"

Am I wrong in assuming that there is a matrix of 9 images which is repeated across the sensor? It was my impression that each microlens was superimposed over a 10x10 array of pixels, such that the entire matrix covered a 30x30 pixel area, and there are 108x108 microlens arrays, for a total of 104,976 microlenses?

I admit that I was wrong in my choice of words concerning focal length. I meant that within each matrix of 9 microlenses, one of them doesn't bend the light, while 4 of them bring items closer than the unbent light into focus, and the other 4 bring farther items into focus.

With that, your software creates 9 different images that focus on light coming from objects 9 different distances from your camera. Is that correct?

I never said there were only 9 microlenses. In my original post I said there was a repeated array of 9 microlenses. Each type of microlens is processed into one 'layer'. Is that wrong?

Just like any camera, the Lytro has an optical lens that focuses to any distance. It has a relatively large aperture of f/2.0, which allows for a relatively shallow depth of field.

The only bit of hardware that's special or unique about a light-field camera is its 'micro-lens' array. The array is a repeated pattern of 3x3 matrices. Each of these 9 different microlenses focuses the light slightly closer or slightly farther away than the others. When you take a picture, the camera records data on the sensor that is then processed into exactly 9 pictures, each corresponding to a slightly different focal length (and therefore a slightly different band of the photo that’s in focus).

The software then uses contrast detection to make a 20x20 sub-matrix indicating which of the nine images is in focus at the chosen point in the image. When you click on a point on a ‘living image’, it looks up that point and loads the image for which that point is most in focus.

The Lytro contains an 11 megapixel sensor. But because it takes 9 photos at once, the effective resolution of the final photograph is 1080x1080 pixels.

It’s not a very complicated design: A microlens array that adjusts the focus on a small scale to produce 9 different images, each with a slightly different range of focus.

Thinking about ‘rays’ of light isn’t necessary to understand how it works.

Here’s a video of the founder getting tripped up when a reporter pinpoints how his technology works (1:05)

http://video.forbes.com/fvn/sxsw-2012/eric-cheng-lytro-lightfield-camera

Comments URL: https://news.ycombinator.com/item?id=4183131

Points: 7

# Comments: 6

I'm not saying it's anything but amazing. However, if the founders think they're going to get today's prices for every last ounce, as the article seems to imply, they are in for a realization.

[Summary: Huge launch, caught by surprise. Big license announcement FRIDAY.]

A week ago we posted meteor.com to Hacker News. We thought a few hundred people would see it, maybe a thousand if we were lucky. Then, the theory went, with the veil of secrecy lifted, we could start in on the hard part -- convincing anyone to look at what we were doing, or care.

Five minutes after clicking the submit button, it was already clear that we had miscalculated by three orders of magnitude. No, the dashboard wasn't broken, there were 5,000 simultaneous users on the website. (And the single-process Meteor app running the site was doing fine.) We expected a few dozen deploys but got ONE THOUSAND THREE HUNDRED. Vimeo says that 70,000 people watched the screencast. What fraction of all living JavaScript developers is that?

"Makes me want to build things." "Blew my mind." "Is this the future of web development?" (Yes, Alex, it is.) "I think I just saw the future." "crazy voodoo magic" "dark sorcery" "This is completely bananas." "I am falling in love."

Even as I write this, 100 people are active on docs.meteor.com and a new app is getting deployed every three minutes. 150 people are hanging out in IRC, and people are answering each other's questions on Stack Overflow and Quora. It's like a perpetual, international Meteor hackathon.

It's all happening much faster than we thought. It's going to be a wild ride, and I'm so happy that you've decided to ride with us. We have some hard work to do now, though. We have to turn this excitement and energy into a real community, and we have to implement the rest of the roadmap and ship a 1.0.

LICENSING UPDATE

Licensing is the first order of business. Many people sent comments. There were three kinds:

1) People who were frustrated because they wanted to use Meteor for a project, but couldn't tell if it was allowed or how much it would cost.

2) Detailed analyses of legal, strategic, and technological implications of every possible choice we could make. This was AWESOME and was incredibly helpful. Some of the people who wrote in are smarter and better informed than any license attorney I've ever talked to.

3) "You suck, you really screwed this up, you are bad people." These comments weren't as helpful, but we're still glad to have them.

I really apologize to everyone who was frustrated. We thought it was going to be months before anyone was interested enough in Meteor to care about the license. Clearly that was wrong.

Licensing is tricky. We're working hard to fix the problem. ON FRIDAY AFTERNOON, we will announce the options for using Meteor in closed-source, commercial software. I think nearly everyone will be happy with the solution. We'll post the announcement on Hacker News, and we'll also send an email to the list. I hope you'll upvote and redistribute as you find appropriate, because even though there are 6,000 people on this list, that's still only 5% of the uniques we've seen on meteor.com.

See you on Friday :)

-- Geoff, Matt, Nick, David

Comments URL: https://news.ycombinator.com/item?id=3858627

Points: 2

# Comments: 0

http://i.imgur.com/YpkNp.png