Comment by AlotOfReading 1 year ago That's one of the the technical limitations behind gating it to unlimited accounts for now. 3 comments AlotOfReading Reply bloomingkales 1 year ago They could embed the subscription level into the blind signature. dgacmu 1 year ago But they still couldn't do accounting / query limiting for users on a limited queries per month plan. So you could do "yes you have assistant" or "no you don't" but their $5/month taster plan has a query limit. bloomingkales 1 year ago Yeah, I guess the only way would be to keep reissuing an updated embedded signature with updated query count.I don’t know the cost or liability of that at scale.
bloomingkales 1 year ago They could embed the subscription level into the blind signature. dgacmu 1 year ago But they still couldn't do accounting / query limiting for users on a limited queries per month plan. So you could do "yes you have assistant" or "no you don't" but their $5/month taster plan has a query limit. bloomingkales 1 year ago Yeah, I guess the only way would be to keep reissuing an updated embedded signature with updated query count.I don’t know the cost or liability of that at scale.
dgacmu 1 year ago But they still couldn't do accounting / query limiting for users on a limited queries per month plan. So you could do "yes you have assistant" or "no you don't" but their $5/month taster plan has a query limit. bloomingkales 1 year ago Yeah, I guess the only way would be to keep reissuing an updated embedded signature with updated query count.I don’t know the cost or liability of that at scale.
bloomingkales 1 year ago Yeah, I guess the only way would be to keep reissuing an updated embedded signature with updated query count.I don’t know the cost or liability of that at scale.
They could embed the subscription level into the blind signature.
But they still couldn't do accounting / query limiting for users on a limited queries per month plan. So you could do "yes you have assistant" or "no you don't" but their $5/month taster plan has a query limit.
Yeah, I guess the only way would be to keep reissuing an updated embedded signature with updated query count.
I don’t know the cost or liability of that at scale.