AtNightWeCode

This is the message you get when calling the same API endpoints as with 4.1. And in the vid they said that the older versions will be deprecated.

Your organization must be verified to use the model `gpt-5`. Please go to: https://platform.openai.com/settings/organization/general and click on Verify Organization. If you just verified, it can take up to 15 minutes for access to propagate.

And when you click that link the "service" they use is withpersona. So it is a complete shit show.

Yep, and I asked ChatGPT about it and it straight up lied and said it was mandatory in EU. I will never upload a selfie to OpenAI. That is like handing over the kids to one of those hangover teenagers watching the ball pit at the local mall.

So OpenAI added withpersona mandatory for API access. Thank you and goodbye.

I switched immediately because of pricing, input token heavy load, but it doesn't even work. For some reason they completely broke the already amateurish API.

They vibe coded the update.

"Your organization must be verified to use the model `gpt-5`. Please go to: https://platform.openai.com/settings/organization/general and click on Verify Organization. If you just verified, it can take up to 15 minutes for access to propagate."

And every way I click through this I end in an infinity loop on the site...

I would have agreed to this if it weren’t for the fact that, for various reasons, you occasionally need to copy and paste passwords manually from password managers. This phishing scenario is no worse.

When I asked ChatGPT about this topic it claimed that AI can make a software developer up to about 50% more productive on average. Sounds more reasonable to me. I often write custom tools to generate code. Sometimes when stars are aligned I get that 100x feeling. And sometimes I regret it so hard a couple of years later.

I think OP based this on an old case about what you can do with data from Facebook vs LinkedIn based on if you need to be logged in to get it. Not relevant when you talk about scraping in this case I think. P is clearly in the wrong here.

This is 100% incorrect.

I have not looked at those formats but take docx for example. That structure is complicated because the layout needs to be described and editable.

PDF is a format for preserving layouts across different platforms when viewing and printing. It is not intended for data processing and so on. I don't see why a structured document format can't exist that simplifies processing and increases accessibility while still preserving the layouts.

The problem for me is to predict what AI might get wrong. Claude can solve hard coding problems one day just to fail with basic stuff like thread safety the next. But overall I think it is clear that we reached the point where AI, if used correctly, saves a lot of development time.

It is a plague across the whole industry. The format in this case is highly influenced by how one corp designed their own products. Multiple document formats have this problem. But you can also find the exact same thing in PCI DSS and other standards. Like, one corp designed a tool to scan for a certain flaw and suddenly it is mandatory. Just ridiculous.

Ok, I see. Thanks.

Not sure about CF but a lot of corps report to https://www.abuseipdb.com. So it is not hard to get the IPs of attackers.

I never seen IPv6 used for origins in CF. Why do you need that?

Name one big US cloud provider or similar that is not ISO 27001 compliant.

I might be out of date but. I think the article is incorrect. It is the same corp that owns both the streaming rights and the ISPs. The court order allows those ISPs to block IP-addresses of sites that hosts illegal streaming. I find it hard to see how CF could have a case here.

Entire Amazon AS-numbers are sometimes blocked so CloudFront consumers have the same issue. The thing with CF is the scale. They are really big and that is why it gets noticed. When it comes to Akamai they don't have shady customers in general and the risk of a problem is less. They also have a better infrastructure.

Well, it is a point. But also remember the horrors of the monoliths he made. Like in Quake (123?) where you have hacks like if level name contains XYZ then do this magic. I think the conclusion might be wrong.

Google has always been hostile towards indiedevs but they have become complete garbage. They do things like removing apps because they have "banned" keywords in the naming. Apps that been around for +5 years. Or you have to comply to some new bs. Or they tried to force you to use Google pay and so on.

Google play has always been totally corrupt. But it is even worse today. The amount of trash spreading through their own programs is massive and then they are banning apps that does not even claim any permissions.

As always with Google, money talks. If you are a small corp you are pretty much screwed. If you are a big client Google will call you and tell you how they fixed your issues before you even knew about them. I really hate working with Google and hope they get split up and destroyed in the anti-trust case. (Yeah, I know the corp is named Alphabet)

Impossible. Speed option may do things like loop unrolling, function inlining and today even way more complicated things than that and therefor creates larger binaries.

Agree with this. But not what I concluded from OP. Architectural decisions from the start is where most optimizations should happen. I remember from school some kids that did this super optimized loop and the teacher said. Do you really have to do that same calculation on every iteration?

But, in the real world. Code bases are massive. And it is hard to predict when worlds collide. Most things does not matter until they do. So measuring is the way to go I believe.

Agree. A classic example is compilers that let you choose between optimizing for speed or binary size. But a smaller sized binary is sometimes faster.

Yeah, but the problem as I see it is not to renew the certs. Some systems becomes unstable or needs to reboot during installation of new certificates. I worked on systems where it takes hours to install and use new certificates.

Github Actions are simple things for tasks. I do btw also not like them.

But, there are so many red flags in this post. Clearly this corp does not know how to build, test and release professional software.

Thought it was strange that X got hit when they are using Cloudflare. Not much competence left at X I guess. What more have they done? No encryption between CF and origins?

The hackers can probably just launch a new attack from CF. Not like X is checking the headers if they failed with the basic setup.

Preteen girls using peeling skin cream is a thing where I live. It causes skin damage. Tiktok bs.

So to mostly prevent this.

Disable direct IP access. Use wildcard certificates. Don't use guessable subdomains like www or mail.

Assuming this is not direct traffic to your IP people will say it is because of TLS logs. Maybe it is in your case. But if you spin up a CF worker on a subdomain to it you will also get hit by traffic immediately. And those certificates are wildcards. I think CF leaks subdomains in some cases. Never seen this behavior when using CF just as a DNS server though.