- Google cloud is setup for big organizations. Not for individuals. All cloud providers are pretty much confusing in a similar way.
- India has specific rules re cybersecurity and financial regulations that Google has to comply. (mandatory id verification and kyc compliance). Others have asked for an id check too.
From what confused me, if OP wanted to use a model, the easier way would have been to pay cursor/windsurf etc. and select that model. Usually that is how people try out a new model. Trying out a specific way means going through the norms every country imposes, and bloat in case of legacy products.
AWS and Azure have come up with their own models. If their future versions hit close to sota and people want to use it, many would end up in a similar loop (and woudl be easier to just use it from the aggregators).
you already sent the prompt to gemini api - and they likely recorded it. So in a way they can access it anyway. Posting here or not would not matter in that aspect.
Google is about to find out the next step of this chain - give access to everyone, don't gatekeep / do checks, and yet take responsibility for anything that goes wrong.
"You should open up the tool, put no restrictions, and yet ensure that it is safe and secure" is an impossible task for anyone.
because they put restrictions. now they cannot. because all the restrictions meant saying no to some legit things as well - inevitably. but then they got sued, laws got passed, to not be monopolistic, and still secure the users. this is the aspect of tech saying no when the thing being asked is impossible but people assume because they dont want to do it for whatever reason.
The thing is that if you are giving professional advice in US - legal, financial, medical - the other party can sue you for wrong or misleading advice. In that scenario, this leaves Openai exposed to a lawsuit, and this change seemingly eliminates that.
They can block the site on a mac if they dont want you to purchase via a mac. They can block any browser agent they want if they dont like the traffic. They can also close your account if they have some reasons. They dont need a reason either. You agree to a terms of service when you make an account, and that usually means giving them broad leeway.
I think its more to do with obfuscation than simple agent buying stuff. Perplexity disguises its agents as chrome browser, and that messes up things at Amazon's end. Not saying its good or bad, but think of ad relevance, then recommendations effectiveness, placements etc. because by default an agent is going to click more and more randomly than a user.
Then, when the agent buys stuff, my guess is that returns are a higher %age (because naturally agents have no preference model so end users might not like what they purchased eventually and returned). I don't know if enough people returned for it to matter, but as a user, if an agent is making a purchase and i know its super easy to return, i won't check everything agent did, just buy and then return if I dont like it.
I don't think it's always a price comparison or margin thing at this point. Given their margins and volume, the agent purchases woudl need to be an order of magnitude more to matter on that front.
create a instruction.md file with yaml like structure on top. put all the instructions you are giving repeatedly there. (eg: "a dev server is always running, just test your thing", "use uv", "never install anything outside of a venv") When you start a session, always emphasize this file as a holy bible to follow. Improves performance, and every few messages keep reminding. that yaml summary on top (see skills.md file for reference) is what these models are RLd on, so works better.
I agree it's a workaround. Ideally the model should follow instructions directly, or check before running another server to see if it's starting. Though training cannot cover every usecase and different devs work differently, so i guess its acceptable as long as its on track and can do the work.
The headline is provocative. The issue is simple: Meta has a recommended feed and another feed which is reverse chronological. The option is hidden and not default, and all the NL judge is asking is for that option to be preserved and not be reset everytime user opens the app/website. Instagram never had this option, this does not say whether they have to implement it too.
I would be curious if the order stands as for curation as well. Someone could have 1000s of friends, and you cant show posts from everyone in a reverse chronological order for a good ux.
- Google cloud is setup for big organizations. Not for individuals. All cloud providers are pretty much confusing in a similar way. - India has specific rules re cybersecurity and financial regulations that Google has to comply. (mandatory id verification and kyc compliance). Others have asked for an id check too.
From what confused me, if OP wanted to use a model, the easier way would have been to pay cursor/windsurf etc. and select that model. Usually that is how people try out a new model. Trying out a specific way means going through the norms every country imposes, and bloat in case of legacy products.
AWS and Azure have come up with their own models. If their future versions hit close to sota and people want to use it, many would end up in a similar loop (and woudl be easier to just use it from the aggregators).
reply