thank yoooou

64e403cf1f4724e7a626a45ab6afab39

Just saw the new batch, any chance I can join in?

Done

I'm very interested in PubSub to replace my use of Ably. However, I noticed there is a limit of 1000 subscribers per topic. Are there any plans to update that to something really big? I need to send a notification to every user currently on a webpage and 1000 subscribers is too low for that. For my use case, each website is a topic (e.g. all users on cloudflare.com)

I personally wouldnt recommend using pubsub on a large scale production site until it is GA. And I'm not sure the limits are changing soon it seems that pubsub has kind of been on the back burner and other products are taking priority to be worked on (but I could be mistaken here just seemingly hasnt been many updates)

I'd definitely wait until GA before switching over. I think I must have missed the existence of pubsub, as I just realized it existed.

what would be a good alternative pub/sub provider we could use until cf pub/sub is in GA? We are looking for a "compatible" solution that would be easy to switch to cloudflare once its stable.

Thanks very much for adding me to the beta. Am following the docs at https://developers.cloudflare.com/pub-sub/get-started/guide, but unfortunately I'm getting "Authentication Error 10000" when trying to create a namespace (via

wrangler pubsub namespace create foo

with wrangler v2.20.0). This is after creating a new API key with "Pub/Sub:Edit" and exporting it via

export CLOUDFLARE_API_TOKEN="mynewtokenpastedhere"

. Is there anything internal that could be causing this issue or can you think of any potential gotchas/footguns I might have run into?

Hmm, that should work. The Pub/Sub token permissions I am using:

Yeah, I just checked to make sure:

Sudden thought: might there be anything I'm missing in terms of conflicts with old tokens in Wrangler?

Not a wrangler export. I just checked and the following options work for me: 1) Set

CLOUDFLARE_API_TOKEN

or 2) Set

CLOUDFLARE_EMAIL

+

CLOUDFLARE_API_KEY

*expert

Looks like pubsub is MQTT compatible, so you could use anything also MQTT compatible and just use MQTT libraries. But switching from one pubsub library to another probably won't be too bad - just switching out some boilerplate for publishing and subscribing.

Turns out I had some environment issues but have now managed to get things sorted. Thanks for your help 🙂

Good stuff

ddffbe0a270fdb9058888d8129d7cb48

Is there (or is there likely to be in the future) an approved way to generate client tokens on demand via a worker rather than using wrangler?

You can already do this right now via the API

I did try looking into the Cloudflare REST API docs but couldn't find anything... Do you have a link to more info?

Or do you mean making a GET request to an

/issue

endpoint in the same way you might revoke credentials via

/revoke

?

The API requests used to be in the docs iirc. I can't seem to find them right now though 😅

Thanks for the top tip! By diving through the git history on the docs I created a successful curl request with...

bash
curl -s -H "X-Auth-Email: $CF_API_EMAIL" -H "X-Auth-Key: $CF_API_KEY" -H "Content-Type: application/json" "https://api.cloudflare.com/client/v4/accounts/$CF_ACCOUNT_ID/pubsub/namespaces/YOUR_NAMESPACE_NAME/brokers/YOUR_BROKER_NAME/credentials?number=2&type=TOKEN&topicAcl=#"

Strangely, it only seems to work with the legacy global API key and email combo; using a correctly scoped API token (replacing the email and key headers with

-H "Authorization: Bearer $CF_API_TOKEN"

) gives me

{"success":false,"errors":[{"code":10000,"message":"Authentication error"}]}

3047c08c562cc038bb307cca95ca2921 Thanks in advance!

96f8637892042b2b1c3cd1569ba7f2d9 Thanks! Really looking forward to trying it out.

🙏 980f4c932a76c709b431713c566959cf

e98dca55a016b4a79f8bb19f1c22c2a4

🙏

Will create the thread to reduce the amount of messages in the main channel 🙂