joshcartme

What about using cloudflare or whoever to forward emails to your gmail, and then user cloudflare or whoever's smtp to send emails from that address?

Jacob's blog links to https://foundermail.mx/, I'm guessing you were looking at foundermail.app. I have no idea if they're related, but the former does not burn your eyes, the latter is very bright

It gets worse! If Google decides the people in your test don't engage enough and/or you didn't respond to their feedback, they may not give you production access. I've got a game that's available on iOS, I released there first and did lots of testing to deal with the low-hanging bugs. After doing the 14 day test Google emailed me:

Possible reasons why your production access could not be granted include:

    - Testers were not engaged with your app during your closed test
    - You didn't follow testing best practices, which may include gathering and acting on user feedback through updates to your app

I've always wanted to make a video game, and over the past few months have been building one, Fairway Rogue. It's a procedurally generated, deck-building, mini-golf roguelite. It's been a lot of fun, and I've learned a lot.

I remember someone saying that when you build a game, you end up building tools to help you build the game. I never really got that, but now I do. I've spent quite a bit of time working on tools to help me balance the various game mechanics.

One weird learning, it was much easier to get it on the iOS app store, than the Google Play store. Google wants you to have a closed playtest with at least 12 players, for 14 days. I did that and they said the testers weren't engaged enough.

If you want to check it out on iOS https://apps.apple.com/us/app/fairway-rogue/id6783598189, I'm still trying to get it on Android

Yeah, I was surprised. I had Claude make a skill to extract the explore agent from Claude Code, but set the model back to haiku. Here it is if it's helpful:

https://gist.github.com/joshcartme/dd71df7b4c51c356760b28d7f...

They changed it with the release on July 1 Explore now inherits the model, it isn't always haiku.

https://code.claude.com/docs/en/changelog#2-1-198

> The built-in Explore agent now inherits the main session’s model (capped at opus) instead of running on haiku

They did recently change it so the default explorer agent inherits the session agent (capped at Opus). Before Explore was always haiku. I had Claude write a skill that extracts the built in Explorer agent skill, and then writes an identical Explore agent that uses Haiku

You could probably open the developer tools, find the console elements and extract the data from there to get around copy/paste limitations. I’m not familiar with the AWS console but let’s say it’s an input, select it in the dev tools and then in the dev tools console do $0.value

I think ground up commonly indicates that an outlet is controlled by a switch on the wall. It's not code, but I think it's a convention

Yeah I'm curious to see how this turns out, because I think part of the appeal of AV1 was how it's unencumbered by them

I have an iphone, previously had an android. I had trouble with RCS chats and then did the "Don't have your previous device" part here, https://messages.google.com/disable-chat. And since then things have been pretty good for me.

If you look at bench or conformance here, https://github.com/ivankra/javascript-zoo?tab=readme-ov-file..., you can get an idea of how it compares in some ways

Thanks! I searched a little and didn't find this but clearly could have searched better

Apparently it's only about as powerful as a RTX 5070, but it's got 128GB of memory. Curious to see if it has a niche vs using something like a framework desktop with 128GB of RAM.

edit: It does have an ARM processor and runs some variant of Ubuntu.

I had the exact same thought. I guess now you could put something in a queue if you have to do non-trivial processing before replying, but that’s not what they wrote

I restarted FF and am now seeing something similar. Hard refreshing alternates between 2 and 3, and soft refreshes quickly get back to 3 most of the time

It reproduces for me in FF 142 on Windows. When I first went to https://cloudflare-quic.com/ it said HTTP/3, but after a few hard refreshes it says HTTP/2 and hasn't gone back to 3

At least these days I think Plot, https://observablehq.com/plot/getting-started, which uses D3 under the hood and is from the makers of D3, is probably the closest thing to an official charting tool built on top of D3.

Thanks for clarifying!

I think I'm getting it now: OS models are getting closer, but only via distillation. Not by training a new frontier model which is out of reach for economic reasons.

Maybe I'm totally misreading this, but it seems like the post contradicts itself. At the beginning of the third paragraph:

> Impressively, open source models have been able to quickly catch up to big labs.

And then the beginning of the fourth:

> Open-source has been lagging behind proprietary models for years, but lately this gap has been widening.

Followed by a picture that is more or less inscrutable.

Wow, that really is amazing!

I couldn't help but notice that you can still see the shadows of the rips in the fixed version. I wonder how hard it would be to get those fixed as well.

It looks like you comment may have been cut off, it sounds good. I'd say go for it, see if you can develop a community around!

I'm the author of those blog posts and I just now saw that this had made it's way onto HN, glad I could generate some discussion and good publicity for Mezzanine. Thanks for sharing it!

The referenced posts are mine, I enjoy photography and figured it was a good place to mix my hobby and profession. It's nothing specific to Mezzanine, just the particular design of my site which is coincidentally powered by Mezzanine.

Do you find it aggravating, appealing or are you ambivalent?

I'd say just go for it, maybe make a basic tutorial that would explain to people how to use it then open source it.

With Mezzanine I think the community that has developed around it's google group has been key.

What's your CMS written in?

I totally agree, beyond needing to understand the basics of the Django template language nothing else is required to create a Mezzanine theme.

In the blog posts this discussion is about, I did go into some detail about creating custom content types but none of that is necessary to theme vanilla Mezzanine.

edit: grammar

What part of it looks hard?

Depending on your programming knowledge integrating a payment gateway shouldn't be too hard. Take a look at some of the ones that have already been done: https://bitbucket.org/stephenmcd/cartridge/src/5be5cd01496b/...

If you look at the Authorize.net one for example, most of the lines of code are setting up the POST data. The actual posting is only about 6 lines or so.

So far the time I have spent working with Mezzanine has been great. The code is very well written and understandable making it easy to dive in and make fixes and/or changes to suit your needs. Using Mezzanine's page_processors it is also very easy to add custom logic to any page you have created without having to modify the core codebase. The community around it is also great and very responsive, helpful and open to make changes to suit the needs of users.

Mezzanine provides all the basic features you would need in a CMS and then makes it very easy to add anything custom or unusual you might want. In this way you don't get overwhelmed by stuff you don't need.

Here's an interesting blog from the Django developers about their plans for python 3: https://www.djangoproject.com/weblog/2012/mar/13/py3k/ The short of it is that they are planning to move for sure and with each release of Django they drop support for one of the 2.x releases of python. Django 1.5 (the next major version) will experimentally support python 3.

Mezzanine provides a platform that allows you to do a lot more than just CMS stuff, so some projects aren't completely CMS-based. The mezzanine-project command just creates a django project that has some settings already configured (installed_apps, middleware, urls, etc...) so you definitely could integrate Mezzanine into an existing project. In reality Mezzanine is a Django reusable app.