seekbeak

The interior of this place looks like something from The Last of Us. We had a client make a 360º tour of it ages ago, and they let us use it on our examples page. It's the last example here: https://seekbeak.com/examples/

You can use the drop down to jump around to different places, or do the tour and use the various navigation hotspots. They're usually located by looking down-ish on each image.

Sure thing: #1084672

The exact wording was: "If you are interested in increasing these limits, we do offer a higher threshold to customers who commit to a minimum of 20TB of our B2 Reserve Capacity-Based Storage service through one of our reseller partners."

Funny you mention that, I am creating a test bucket with R2 at this very moment.

Just emailed support and they've said this is already implemented, and you can only increase your limits if you commit to 20TB of storage.

Our production web app can easily makes more than 20 requests for images per second on the initial page load for a single user. B2s new 20 requests per second cap means that it will just take one person viewing to cause anyone else also trying to view the app at that second to get an empty white screen. Cloudflare cache will only mitigate this so much.

Anyone got non Amazon suggestions to migrate to ASAP?

Crazy. I’d always thought it was because of Nyquist and the 20k ish human hearing limit.

Replying to my own comment as I just talked to their support about this: "The maintenance window does affect all our data simultaneously. As we push the updates through one data center to another." Welp, so much for that.

Same here. We're midway through a migration, and this has us re-thinking the whole move. I wonder if we had a duplicate copy of our data in the EU data center if we could do a fallback during US downtime, or if the entire 'cloud' goes down.

I love how they are just "turning it off and on again".

Can't the majority of that manual binding be done by good 'ol fat arrows?

I need to get into server rendering more. I find myself doing double validation these days and server rendering could solve some of that. I validate client side, then again server side to make sure people aren't throwing garbage at my API.

None of them? Are you just doing everything vanilla js/html/css with no build tools, or just using bash/npm scripts?

It's such a no brainer after you use it for a while, and the time savings after the fact far make up for the initial learning curve.

Just do a small project to muck around with first. Maybe something small that nobody has thought of, like a to-do list?

Please work. Please work. Please work. This couldn't come at a better time. I've got "convert site to TS" looming on my to-do list for a large web app. Anything that saves me some interface props/state typing tedium would be great.

I had my eye on http://fuse-box.org/ for a while, and tried a few sample projects with it. It has a lot of the same promises as Parcel appears to have. Multicore is exciting for me, which Fusebox doesn't have. So... many... choices...

This is really, really cool.

However, I can't help but think about the day where I am walking down the street, bombarded by advertisements doing this in my AR glasses/contacts/implant.

From the title, I was hoping it was some sort of cool step sequencer that would somehow help with rhythm training.

How wrong I was.

I made the initial version of https://seekbeak.com after about 3 or 4 months. It's been updates and additions for the past year now.

I'll echo the rest of the folks in here: Launch early, and add features as you go. I'd rather launch at 85% than never launch at 100%

Also, there is a fine line between an initial launch which is missing a few fancy features, and an embarrassing clusterfuck. So make sure that the site/app is totally functional, and as bug free as you can be. Then you can get to work on adding all the bells and whistles which are buzzing around your head!