Hacker Newsnew | past | comments | ask | show | jobs | submit | doc_ick's commentslogin

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.

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%

Well you don’t repeat yourself if the llm repeats it for you at the cost of millions of tokens.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: