nstg-web (web app to auto-TG nations)

[[violet]]

nstg-web

nstg-web is a free and open source web application that allows you to easily send telegrams to a list of NationStates nations defined using a powerful query language called Telegram Recipient Language.

nstg-web features the following:

• ability to send telegrams to complex sets of nations defined using TRL
• a continuous mode that periodically updates the recipients list with new nations that match the provided TRL string, which is useful for recruitment purposes
• a dry-run mode that allows you to test TRL strings
• progress reporting
• rate-limiting
• ability to save configuration
• ability to automatically save past recipients to avoid sending a nation the same telegram twice

Usage

The latest version of nstg-web can be accessed here. Usage should be fairly self-explanatory; however, if you have any questions, you can ask them here and I'll answer them as soon as I can.

You can also view the source code on GitHub.

License

nstg-web is licensed under the Apache License 2.0.

[United Massachusetts]

YAY!

[Auralia]

Keep in mind that this is alpha-quality software and hasn't been fully tested.

It would be a very good idea to initially use the "dry run" feature to verify that you'll be sending telegrams to the correct nations.

[Frisbeeteria]

Regarding recruitment:

Recruitment telegram (One telegram every 180 seconds)
Non-recruitment telegram (One telegram every 30 seconds)

Does selecting the appropriate checkbox on your app also check the checkbox on the telegram? Please make it do so if it's not set up that way.

Also bear in mind that recruitment is for "a region or organization". It should be clear in your app that organizations need to use the Recruitment checkbox. And did you intentionally leave off Campaigns?

Edit: I see that this uses the Telegram ID field to set up the telegram. Shouldn't the rate limit automatically set itself based on the TG settings? If people try to send recruitment messages via the non-recruitment setting, it seems to me you'd be sending a lot of superfluous calls to the API.

[United Massachusetts]

Regarding recruitment:

Recruitment telegram (One telegram every 180 seconds)
Non-recruitment telegram (One telegram every 30 seconds)

Does selecting the appropriate checkbox on your app also check the checkbox on the telegram? Please make it do so if it's not set up that way.

Also bear in mind that recruitment is for "a region or organization". It should be clear in your app that organizations need to use the Recruitment checkbox.

And did you intentionally leave off Campaigns?

Campaigns are non-recruitment in NSAutoTelegram.

[Auralia]

Regarding recruitment:

Recruitment telegram (One telegram every 180 seconds)
Non-recruitment telegram (One telegram every 30 seconds)

Does selecting the appropriate checkbox on your app also check the checkbox on the telegram? Please make it do so if it's not set up that way.

[...]

Edit: I see that this uses the Telegram ID field to set up the telegram. Shouldn't the rate limit automatically set itself based on the TG settings? If people try to send recruitment messages via the non-recruitment setting, it seems to me you'd be sending a lot of superfluous calls to the API.

As far as I know, there's no way to determine whether a telegram is recruitment/campaign/none of the above using the API.

Also bear in mind that recruitment is for "a region or organization". It should be clear in your app that organizations need to use the Recruitment checkbox.

This should probably be added to the telegram API rules, which right now simply distinguish between "Recruitment TGs" and "Non-recruitment TGs" without defining the term.

And did you intentionally leave off Campaigns?

Campaigns don't have a special rate limit.

[Vulturret]

For the record, a line near the bottom of the original post says "nsth-web," as opposed to "nstg-web." But hey, that's an innocent mistake. I like the functionality and easy usage of the tool, in my opinion it's a lot better than other telegramming programs I've looked at. Overall, you did an excellent job on the app, and I absolutely adore the fact that it runs on a web browser as opposed to requiring a separate program to be used, which is immensely useful for numerous indivials in so many different situations. I applaud your work on the program! Happy holidays!

[Auralia]

For the record, a line near the bottom of the original post says "nsth-web," as opposed to "nstg-web."

Thanks for catching that!

[Caelorum Founder]

It appears not to want to comply with the rate limit. I have it recruiting, but it is telegrammint quicker than it is supposed to, then saying that it failed to send to someone.

Edit: After turning on verbose mode, that appears to be what is happening. Is it supposed to do that, or is it supposed to wait every 3 minutes?

Edit2: I don’t know what happened, I had the right box checked. Working now, but you might want to examine the code.

Edit3: Failing again.

[Auralia]

It appears not to want to comply with the rate limit. I have it recruiting, but it is telegrammint quicker than it is supposed to, then saying that it failed to send to someone.

Edit: After turning on verbose mode, that appears to be what is happening. Is it supposed to do that, or is it supposed to wait every 3 minutes?

Edit2: I don’t know what happened, I had the right box checked. Working now, but you might want to examine the code.

Edit3: Failing again.

Did you select the "recruitment" rate limit?

Can you provide any specific log messages?

[Anarhic Empire of Byzantine]

When I set API rate limit to recruitment telegram, igot HTTP Error code 429...

I use
new[25];

[Caelorum Founder]

It appears not to want to comply with the rate limit. I have it recruiting, but it is telegrammint quicker than it is supposed to, then saying that it failed to send to someone.

Edit: After turning on verbose mode, that appears to be what is happening. Is it supposed to do that, or is it supposed to wait every 3 minutes?

Edit2: I don’t know what happened, I had the right box checked. Working now, but you might want to examine the code.

Edit3: Failing again.

Did you select the "recruitment" rate limit?

Can you provide any specific log messages?

Yes, I did set the recruitment rate, and I got the same thing as Byzantine

[Auralia]

I think this bug should now be fixed.

[Caelorum Founder]

I think this bug should now be fixed.

It works, at least right now. Thanks so much!

[Imperium Anglorum]

As far as I know, there's no way to determine whether a telegram is recruitment/campaign/none of the above using the API.

I proposed a shard to do this in the main API thread. I don't think it was ever acted upon. (Instead of sendTG, I wanted something like a TGinfo shard or something like that.)

---

Also, why did you design your telegrams language not to use the standard telegrams recipient format?

[Auralia]

As far as I know, there's no way to determine whether a telegram is recruitment/campaign/none of the above using the API.

I proposed a shard to do this in the main API thread. I don't think it was ever acted upon. (Instead of sendTG, I wanted something like a TGinfo shard or something like that.)

Yes, I'd definitely use that if it existed.

Also, why did you design your telegrams language not to use the standard telegrams recipient format?

The standard format -- which I believe was originally derived from the format I used for NationStates AutoTelegram -- doesn't allow you to specify multiple arguments for a single category type, nor does it allow you to create your own groups. I decided to use an alternate syntax to support these features.

The standard format also made some confusing decisions -- "+" does not conventionally mean "filter by inclusion", it means "add".

[Little St Nick]

Nice Christmas gift. Thank you for sharing. I hope Santa was good to you!

[Vuori Kunin-Grrs]

This is an amazing development of your previous NationStates Autotelegrammer - a Christmas gift for us NS recruiters. Thank you.

In using your recruiter, I've gotten the following, where afterwards, the program simply stops. What is the problem?

error: Failed to send telegram to romeera.
error: [Error: XHR error]

[Auralia]

This is an amazing development of your previous NationStates Autotelegrammer - a Christmas gift for us NS recruiters. Thank you.

In using your recruiter, I've gotten the following, where afterwards, the program simply stops. What is the problem?

error: Failed to send telegram to romeera.
error: [Error: XHR error]

What browser are you using? Do you have verbose logging enabled? Can you give me any other information?

[Vuori Kunin-Grrs]

This is an amazing development of your previous NationStates Autotelegrammer - a Christmas gift for us NS recruiters. Thank you.

In using your recruiter, I've gotten the following, where afterwards, the program simply stops. What is the problem?

error: Failed to send telegram to romeera.
error: [Error: XHR error]

What browser are you using? Do you have verbose logging enabled? Can you give me any other information?

Apologizes for the long delayed reply, but it appears to only appear when my Wifi cuts off, often for no more than 5 minutes.

Could you add some sort of feature that gives permission for the API client to continually retry sending if Wifi temporarily cuts off for a custom amount of time?

[Teloanaple]

Auralia i am getting the error saying I am exceeding my rate limit. Similar to the problem a bit up the page but this time it still continues. Also I wanted to send 25 telegrams but end up only sending one or a error.

[Auralia]

Could you add some sort of feature that gives permission for the API client to continually retry sending if Wifi temporarily cuts off for a custom amount of time?

I'll look into the possibility of implementing retry support.

Auralia i am getting the error saying I am exceeding my rate limit. Similar to the problem a bit up the page but this time it still continues. Also I wanted to send 25 telegrams but end up only sending one or a error.

Are you doing something else with the API at the same time?

[Angevin Founder]

I wasn't sure if this was the correct place to put this.

After following the steps for this client it keeps saying that the telegrams are failing to send. It will bring up a list of nations that its going to TG and then slowly fails them one by one. Help?

[Kaystein]

I just got a surprising telegram sent to my inbox: https://pasteboard.co/IyNlPvp.png

Apparently, it's from somebody replying to the automated API recruitment telegrams I'm sending out using this client.

Just for reference, this is my current configuration (minus my secret key, tgid, client key): https://pasteboard.co/IyNnbW9.png

Now, I assumed that since "recruitment telegram" is toggled, that would mean that the API system would send telegrams marked as "recruitment" so it gets filtered correctly.

So help me out here; if somebody that blocked recruitment telegrams is getting one of the automated API telegrams being sent through using nstg-web, what's the glitch? Is it something on my end or is it something wrong with the client, or something wrong with NationStates API?

[Marxist Germany]

No, your template must be marked as Recruitment before you click send to tag:API, you mustve forgotten that step.