“Coding wasn't the hard part.” I would hope not since astra did that.

Above saltiness aside, are you worried Microsoft will see this?

Ha, fair. I should have said "Coding wasn't the hard part because Astra did all of it."

The hard parts for me were describing bugs that weren't visual and the more subjective stuff, e.g. where memories should go, pacing, what felt confusing, whether something was actually fun, etc. I couldn't have built this without AI.

Regarding Microsoft: a little. It's noncommercial, and I have a credits/disclaimer screen that makes it clear it's an unofficial fan project and that the Halo assets belong to their respective owners. But obviously that doesn't mean I own or have a license to the Guardian assets. If Microsoft/Halo Studios asked me to take it down or change something, I would.

Apple has some “trust” for vetting things, and with the wave of slop-apps it fine with a slight delay so the App Store doesn’t become riddled with slop like the android store.

Review speed and slopness are related but not exclusive to each other.

Definitely not exclusive, though I believe they are related enough to not tank one for the other. If a review is 2 seconds and done, then the circle for figuring out the mvp slop app is pretty slim.

You can imagine with the AI models we have now, many of the stuff reviewers do could be automated to a large extent. They can also determine through binary diffing that functionality changes may be limited etc. Many things can be done to eliminate majority of the queue for example.

Some stuff the reviewers do could easily be automated. I’m off the mindset everything the reviewers do shouldn’t be automated however, as llms do hallucinate and are still susceptible to ghost prompts.

At the infinite app review scale (some apps malicious, illegal, rip-offs), extra time is inevitable.

Don’t worry, that’s almost every other page on the feed

Don’t worry, just give them a year and infinite tokens and they can make windows me.

Just have to view their “trust me bro” rating.

HR loves this one trick…

CTO and CEO as a service, I can’t wait to import that into my agents and now see some people sweating.

Unfortunately that seems like bad history. I’ve only had good experience with wsdls, internally and externally, but they were generated with the services and readily available.

I have the same experience as you. I have probably worked with a few dozen SOAP services in my time, so perhaps I have been "lucky", but WSDLs have not been an issue for me.

WSDL is in some ways more user-friendly than openapi schemas. They have a rich set of types that mostly just work as expected. When I try to generate models from an OpenAPI JSON file, I often find myself either overriding the models or making scripts/plugins to rewrite the json to fix types. An example of this is using proper decimals instead of doubles, which is crucial in my line of work.

Ontop of this, including a photo edit history in a photo including the original photo would increase the size of a photo to be completely unusable or unshareable.

I understood the GP so that only some unique ID or hash of the original image would be included, not the image itself. Basically like the commit chain of Git but without the actual content blobs.

You could use this data to prove that image B is an edit of image A if you already have both A and B.

I still think this is a bad idea, because this all requires the images to have some sort of ID - and that seems like a prime target for tracking.

You can publish a fully stripped image (as people do now for exif), and retain the original

Unfortunately theres no thanks to the suppliers of training data. US courts made sure there’s no recompense for them, and likely never will be.

Seems similar to eminent domain, but without limitations.

100%