The article says "We plan to release substantially larger improvements to our models in the coming weeks."
Sonnet 4 has definitely been the best model for our product's use case, but I'd be interested in trying Haiku 4 (or 4.1?) just due to the cost savings.
I'm surprised Anthropic hasn't mentioned anything about Haiku 4 yet since they released the other models.
After my Pebble I tried an e-ink "Watchy" from SQFMI (https://watchy.sqfmi.com/) thinking that the battery life would be great but the battery only lasted a few days.
I've been wearing a Bangle 2 (https://www.espruino.com/Bangle.js2) which feels closest to recreating my Pebble. It has super long battery life and feels a lot like my Pebble did, but doesn't have the polish of the pebble UI and animations.
"Worldwide, most radiosonde observations are taken daily at 00Z and 12Z (6 a.m. and 6 p.m. EST)" - NOAA.gov
I know we get more weather data from other sources, but it seems insane that these 2 launch times per day (per balloon location) are what make up most of our current weather forecasting data.
You mentioned solar. Do you have the capability (or plans) to run these over night as well?
I'm amused at how upset people seem to be about being asked to sign up and pay for this service. I don't remember seeing comments like this on other launch threads on HN.
Sign up for free, try it for...not free. Go fuck yourself!
I’m glad you have the pricing clear in the front page so I won’t use it, unlike another similar service I tried that after wasting my time generating logos with prompts and details only to ask me to pay to download it..
My prediction. You won't survive a month with this kind of behaviour. ... Milking money out of people is outdated and obsolete approach.
After all the work I had sketching a penis I got hit with the paywall without even seeing a single result
So, I just logged in and there is no free plan at all to try your service as well as no way to delete my profile.
I went through the trouble of signing up, drew my sketch and prompt, clicked "generate" and it just sends me to a pricing page with minimum spend $20/month
Come on, just let us try the damn thing one or two times - nobody's actually going to be satisfied with the first logo they generate, so it's not like you lose the sale.
I think you need to give us the ability to test the creation of the logos before signing up. Maybe ask for payment later on when the user wants to download the logo?
I didn’t even get to see it work before being hit with a pay link.
I don’t really want to sign up before playing with it, maybe you can find another way to achieve your goal?
Whoa yeah this looks like it would be easier than doing it all by hand. $466 at Mouser. Interesting!
Looking around on Google, I don’t see anyone that has tried using this for interferometry yet but the KrakenSDR team explicitly mentions that it can be used for interferometry.
Is there a better frequency available to amateur hardware that would give tolerance within more reasonable limits?
Without a shared external clock reference, i.e. over longer distances, how expensive does the hardware get if you want to be able to accurately measure the time/phase wandering to correct in software?
Just curious if it’s a limit of the low cost RTL-SDR or if it’s a harder problem than that (or both?).
This is really cool. Could you build a few of these and make an interferometer?
I remember reading that interferometers are usually all connected by physical cables with physical loops to make sure the incoming data is combined at exactly the right time. But are we at a point now where that can somehow be done intelligently in software? Or are these little RTL-SDR's not accurate enough to even begin trying that?
We use images from istock.com (Getty Images) for the paid plans and unsplash.com for the free plan.
We ask gpt-4 for a good keyword that we can search on the istock.com API based on the business description in order to get images that fit the website out of the box.
Yeah! We made our own landing site using our own tool. That was pretty fun to do.
Asking the AI to edit things on the page is really fun. It's crazy what changes it can make with such little context.
For example the form where you input your business name and description. We just gave the AI a prompt of "turn this section into a form that posts to https://... with a business name and description" and it gave us exactly that, first try.
Hi! I’m Todd, the solopreneur founder of Prerender.io and I created that $1,000,000/year AWS bill. I sold Prerender.io to Saas.group in 2020 and the new team has done an incredible job growing and changing Prerender since I left.
$1M per year bill is a lot, but the Prerender back end is extremely write-heavy. It’s constantly loading URLs in Chrome in order to update the cached HTML so that the HTML is ready for sub-second serving to Google and other crawlers.
Being a solo founder with a profitable product that was growing organically every month, I really didn’t have the time to personally embark on a big server migration with a bunch of unknown risks (since I had never run any bare metal servers before). So the architecture was set early on and AWS allowed me the flexibility to continue to scale while I focused on the rest of business.
Just for a little more context on what was part of that $1M bill, I was running 1,000+ ec2 spot instances running Chrome browsers (phantomjs in the early days). I forget which instance type but I generally tried to scale horizontally with more smaller instance sizes for a few different reasons. Those servers, the rest of the infrastructure around rendering and saving all the HTML, and some data costs ended up being a little more than 50% the bill. Running websites through Chrome at scale is not cheap!
I had something like 20 Postgres databases on RDS used for different shards containing URL metadata, like last recache date. It was so write heavy that I had to really shard the databases. For a while I had one single shard and I eventually ran into the postgres transaction ID wraparound failure. That was not fun so I definitely over provisioned RDS shards in the future to prevent that from happening again. I think RDS costs were like 10%.
All of the HTML was stored in s3 and the number of GET requests wasn’t too crazy but being so write heavy on PUT requests for recaching HTML, with a decent sized chunk of data, the servers to serve customer requests, and data-our from our public endpoint, that was probably 30%.
There were a few other things like SQS for populating recache queues, elasticache, etc.
I never bought reserved instances and I figured the new team would go down that route but they blew me away with what they were able to do with bare metal servers. So kudos to the current Prerender team for doing such great work! Maybe that helps provide a little more context for the great comments I’m seeing here.
It looks like the hacker was able to log into the website's hosting provider account. The hacker then changed the DNS to point to a different server that had an exact copy of the blackwallet.co website but with a small injection of some javascript to siphon off the master keys that people were entering.
We'll keep working on improving Prerender.io and we'll continue serving our customers exactly as we are now. So no pivot for Prerender.io.
Prerender.com is sort of a pivot, but more like just opening up our infrastructure to other crawlers that would like to execute javascript too. So we're expanding our offerings :)
Yep, we have LOTS of servers :) We pretty heavily cache pages too.
Headless Chrome is great and we're super thankful that the Chromium team put the work in! PhantomJS is good... it just doesn't have all of the latest features, like ES6. So it was really helpful that headless Chrome came along right as people started using more ES6.
Yeah, Chrome did break the opening of view-source URLs a while back for our https://prerender.io/ buttons on the bottom of the homepage.
It looks like they are currently using Chrome 41 (https://developers.google.com/search/docs/guides/rendering) when rendering pages. I agree that with all of the work on headless Chrome, they should move towards using headless Chrome in the future.
Todd from Prerender.io here. We always knew this day would come eventually :) We are currently serving around 60 million prerendered pages to crawlers every day, with Google being about half of those requests. We are recaching around 1 billion pages every month in PhantomJS/Headless Chrome. Google is the only crawler executing a meaningful amount of JavaScript so Bing, Baidu, Yandex, Facebook, Twitter, and other SEO crawlers still need prerendering.
For anyone that will need to update their own crawlers to match Google’s new javascript crawling, we’ve opened up our Prerendering engine that uses Headless Chrome at https://prerender.com. You can capture HTML, Screenshots, PDFs, or even HAR files from any web page with just an http request to our service. So it’s super easy to add javascript crawling to any crawler with Prerender.com (and it’s open source https://github.com/prerender/prerender).
For our Prerender.io customers, this announcement just means that Google will stop crawling ?_escaped_fragment_= URLs so they won’t request prerendered pages anymore. Instead, Google will just execute the javascript directly and index the result.
We’ve always recommended that our customers use the escaped fragment protocol, so it will be a smooth transition as Google slowly stops crawling the ?_escaped_fragment_= URLs. No changes need to be made if you are currently using Prerender.io. Keep an eye on our twitter (@prerender) and we’ll give updates on Google’s transition.
The one thing to look for when Google starts executing your javascript is keep an eye on your Google Webmaster Tools for your number of pages crawled by Google. In the past, we’ve seen that Google crawls much slower when executing the javascript themselves. Hopefully javascript websites don’t take a hit in number of pages crawled daily since that can affect large sites having all of their pages up to date in Google's index.
If Google Webmaster Tools is unable to render your website correctly, then that's a good indicator that Googlebot won't be able to render the pages correctly either. If you remove the fragment meta tag, then Google will need to render your javascript to see the page. Let us know how that goes if you try it! [email protected]
Todd from Prerender.io here. We've seen the same thing with people switching to AngularJS assuming it will work and then coming to us after they had the same issue.
[1] This image is from 2014, when Google previously announced they were crawling JavaScript websites, showing our customer's switch to an AngularJS app in September. Google basically stopped crawling their website when Google was required to execute the JavaScript. Once that customer implemented Prerender.io in October, everything went back to normal.
Another customer recently (June 2015) did a test for their housing website. They tested the use of Prerender.io on a portion of their site against Google rendering the JS of another portion of their site. Here are the results they sent to me:
Suburb A was prerendered and Google asked for 4,827 page impressions over 9 days
Suburb B was not prerendered and Google asked for 188 page impressions over 9 days
We've actually talked to Google some about this issue to see if they could improve their crawl speed for JavaScript websites since we believe it's a good thing for Google to be able to crawl JavaScript websites correctly, but it looks like any website with a large number of pages still needs to be sceptical about getting all of their pages into Google's index correctly.
Last time someone posted prerender.io on HN, I totally wasn’t ready. We only had the open source component. Launch early, right? Now, we’re a full blown SaaS solution for rendering HTML to crawlers from SPAs or AJAX heavy websites.
Our open source prerender server has improved a lot. We fully support _escaped_fragment_ and only check user agents for the crawlers that don’t support it. The server starts a pool of phantomjs processes, has a robust plugin architecture, can be installed via npm, and easily customized like expressjs.
Sonnet 4 has definitely been the best model for our product's use case, but I'd be interested in trying Haiku 4 (or 4.1?) just due to the cost savings.
I'm surprised Anthropic hasn't mentioned anything about Haiku 4 yet since they released the other models.