Agadar's Telegrammer (updated August 16th, '20)

[Agadar]

[ Agadar's Telegrammer ]

This desktop application allows you to automate sending telegrams to other nations, making it useful for recruiting, World Assembly campaigning, region-wide telegramming, and so forth. It only requires Java to be installed on your machine in order to run.

Before you use this program, make sure you're familiar with the Telegrams API. You should know how to obtain a Client Key, and how to create a telegram template. Once you've obtained a Client Key, a Telegram Id, and a Secret Key, you're ready to start using this program.

If you're looking for a guide on how to obtain the keys and a Telegram Id, check out Ever-Wandering Souls' Simple Guide to Sending Telegrams via API!

This program uses the NationStates Telegrammer Core library to communicate with the NationStates API.

[ Screenshot ]



[ Links ]

Releases
Source code
More applications

[Agadar]

Version 1.1.0 has just been released. Details can be found in the changelog on the releases page.

[Ever-Wandering Souls]

Greetings! Would you like your client to be included in my API Telegram Guide? I would be happy to add it to my list (and it might also get me to do some other maintenance, like updates for RO, recruitment permissions, and which clients are currently functioning xD).

[Agadar]

Greetings! Would you like your client to be included in my API Telegram Guide? I would be happy to add it to my list (and it might also get me to do some other maintenance, like updates for RO, recruitment permissions, and which clients are currently functioning xD).

I'd love it if it were included. That's a great guide. I'll make sure to link to it from this thread as well.

[Agadar]

Version 1.2.0 has been released. Check the details in the changelog on the releases page.

[Luxdonia]

Very interesting application! I'll make to check it out!

[Ever-Wandering Souls]

Greetings! Would you like your client to be included in my API Telegram Guide? I would be happy to add it to my list (and it might also get me to do some other maintenance, like updates for RO, recruitment permissions, and which clients are currently functioning xD).

I'd love it if it were included. That's a great guide. I'll make sure to link to it from this thread as well.

Added!

[Imperium Anglorum]

Is the client key in the screenshot above real?

[Agadar]

Is the client key in the screenshot above real?

Nope, it's gibberish.

[Ever-Wandering Souls]

Hey, just wanted to let you know that I occasionally hit the TG rate limit with your tool.

[Agadar]

Hey, just wanted to let you know that I occasionally hit the TG rate limit with your tool.

Aye, I'm still experimenting with finding that sweet spot that delays as little as possible while not hitting the limit. Currently at the exact rate limit plus one second. Going to test adding another half second.

[Imperium Anglorum]

Hey, just wanted to let you know that I occasionally hit the TG rate limit with your tool.

Aye, I'm still experimenting with finding that sweet spot that delays as little as possible while not hitting the limit. Currently at the exact rate limit plus one second. Going to test adding another half second.

Huh. My program uses a rate limit of 30.05 and 180.05 seconds. That the program touches the rate limit is peculiar to say the least.

[The Blaatschapen]

Aye, I'm still experimenting with finding that sweet spot that delays as little as possible while not hitting the limit. Currently at the exact rate limit plus one second. Going to test adding another half second.

Huh. My program uses a rate limit of 30.05 and 180.05 seconds. That the program touches the rate limit is peculiar to say the least.

Lag on the network maybe? While it sends out the requests just within the limits, they might have been received by the server just outside of it?

[Agadar]

Curious indeed. I'll make sure to re-evaluate my client's rate limiter.

[Agadar]

Solved the issue. It was a minor lapse of logic in my rate limiter. The next version of my Telegrammer should have fixed the occasional rate limit violation.

[The World of Remnant]

A suggestion of sorts -

when running a long campaign, such as a tag:all, on a machine that occasionally needs to be restarted, setting the TG to run again involves an ever-increasing amount of time spent just chugging through api calls to determine that thousands and thousands of nations have already been hit. Additionally, thinking ahead, in the case of any restarts after the 28 day mark (since a tag:all, estimating by the ratio of nations blocking tg's to those not blocking based on running my current campaign for a few weeks, will take over 200 days), nations will no longer return "previous too recent" when called, and telegrammer could effectively end up telegramming the same tens of thousands of nations every 28 days if the user has to restart at all.

Now, admittedly, the usage case for running a tag:all via API is a pretty small one, but nonetheless, for this niche these are major issues if you're running telegrammer on anything but a dedicated server - i.e. anything that might need to restart now and then, or be forced to by a loss of power or something.

Fixing this, I see two similar solutions of sorts -

For the issue of looping recruitment if restarted after 28 days, you could keep a file of nations already hit by a telegram, and allow an option to not send a given telegram to a nation more than once (checking against your own list).

For the issue of api calls, you could keep a similar list of nations attempted to be targeted and failed. Obviously, this is something that could be changed at any time, but I at least would much rather risk missing one or two people who've changed their settings since I last tried than spend days api calling them all to check.

This could also be a single list, of every nation a campaign has targeted hit or miss, which while less selective, is perhaps simpler?

---

Additional side note, I've been a bit confused by some of the time stamps I'm seeing.

[11:00:01] skipping recipient 'orthamotch': recipient is blocking recruitment telegrams
[11:00:01] skipping recipient 'wationiellecsstan': recipient is blocking recruitment telegrams
[11:00:02] skipping recipient 'cunfound': recipient is blocking recruitment telegrams
[11:00:02] skipping recipient 'bmama': recipient is blocking recruitment telegrams
[11:00:02] skipping recipient 'this_england': recipient is blocking recruitment telegrams
[11:00:05] skipping recipient 'dingleton': recipient is blocking recruitment telegrams
[11:00:05] skipping recipient 'hercules_labors': recipient is blocking recruitment telegrams
[11:00:05] skipping recipient 'new_republic_of_york': recipient is blocking recruitment telegrams
[11:00:06] skipping recipient 'raiona': recipient is blocking recruitment telegrams
[11:03:02] queued telegram for 'kontbagass'
[11:03:02] skipping recipient 'araguari': recipient is blocking recruitment telegrams
[11:03:02] skipping recipient 'hcaer': recipient is blocking recruitment telegrams
[11:03:02] skipping recipient 'dyer_mycoria': recipient is blocking recruitment telegrams
[11:03:03] skipping recipient 'the_northern_white_isles': recipient is blocking recruitment telegrams
[11:03:03] skipping recipient 'rezial': recipient is blocking recruitment telegrams
[11:03:06] skipping recipient 'powerstrike': recipient is blocking recruitment telegrams
[11:06:03] queued telegram for 'galmmoria'
[11:06:03] skipping recipient 'spires_island': recipient is blocking recruitment telegrams
[11:06:03] skipping recipient 'mechamuffinland': recipient is blocking recruitment telegrams
[11:06:03] skipping recipient 'joaolandia': recipient is blocking recruitment telegrams
[11:06:03] skipping recipient 'west_fiana': recipient is blocking recruitment telegrams
[11:06:03] skipping recipient 'six_thrones': recipient is blocking recruitment telegrams
[11:06:07] skipping recipient 'pallanthium': recipient is blocking recruitment telegrams
[11:06:07] skipping recipient 'martys_country': recipient is blocking recruitment telegrams
[11:06:07] skipping recipient 'project_valor': recipient is blocking recruitment telegrams
[11:06:07] skipping recipient 'softened_pyrokinetics': recipient is blocking recruitment telegrams
[11:06:08] skipping recipient 'west_emeraldland': recipient is blocking recruitment telegrams
[11:06:08] skipping recipient 'dumue': recipient is blocking recruitment telegrams
[11:06:11] skipping recipient 'pepelonia': recipient is blocking recruitment telegrams
[11:06:11] skipping recipient 'vitle_swizzla': recipient is blocking recruitment telegrams
[11:06:11] skipping recipient 'fedner': recipient is blocking recruitment telegrams
[11:06:11] skipping recipient 'hephathenix': recipient is blocking recruitment telegrams
[11:06:11] skipping recipient 'stoacia': recipient is blocking recruitment telegrams
[11:06:12] skipping recipient 'piloria': recipient is blocking recruitment telegrams
[11:06:15] skipping recipient 'altmoras_i': recipient is blocking recruitment telegrams
[11:06:15] skipping recipient 'pacmanistania': recipient is blocking recruitment telegrams
[11:06:15] skipping recipient 'chapmanian_kingdom': recipient is blocking recruitment telegrams
[11:06:15] skipping recipient 'camnasia': recipient is blocking recruitment telegrams
[11:06:16] skipping recipient 'equnalagria': recipient is blocking recruitment telegrams
[11:06:16] skipping recipient 'kevin_mitnick_alliance': recipient is blocking recruitment telegrams
[11:06:19] skipping recipient 'kubbitt': recipient is blocking recruitment telegrams
[11:06:19] skipping recipient 'the_russian_empire_1917': recipient is blocking recruitment telegrams
[11:06:19] skipping recipient 'devantania': recipient is blocking recruitment telegrams
[11:06:19] skipping recipient 'belarusian_socialist_republics': recipient is blocking recruitment telegrams
[11:06:19] skipping recipient 'altmoras_v': recipient is blocking recruitment telegrams
[11:06:20] skipping recipient 'patamina': recipient is blocking recruitment telegrams
[11:06:23] skipping recipient 'timao': recipient is blocking recruitment telegrams
[11:06:23] skipping recipient 'nukls-andwicz': recipient is blocking recruitment telegrams
[11:06:23] skipping recipient 'hongcouver': recipient is blocking recruitment telegrams
[11:06:23] skipping recipient 'altmoras_x': recipient is blocking recruitment telegrams
[11:06:24] skipping recipient 'nadnock': recipient is blocking recruitment telegrams
[11:06:24] skipping recipient 'shazen': recipient is blocking recruitment telegrams
[11:06:27] skipping recipient 'panamericana': recipient is blocking recruitment telegrams
[11:06:27] skipping recipient 'goosainia': recipient is blocking recruitment telegrams
[11:06:27] skipping recipient 'star_light_glimmer': recipient is blocking recruitment telegrams
[11:06:27] skipping recipient 'joedain': recipient is blocking recruitment telegrams
[11:06:28] skipping recipient 'polish_republic_of_federal_states': recipient is blocking recruitment telegrams
[11:06:28] skipping recipient 'edatsinovap': recipient is blocking recruitment telegrams
[11:06:31] skipping recipient 'injigo': recipient is blocking recruitment telegrams
[11:06:31] skipping recipient 'fascist_protector': recipient is blocking recruitment telegrams
[11:06:31] skipping recipient 'mountain_man_of_appalachia': recipient is blocking recruitment telegrams
[11:06:31] skipping recipient 'the_condemed': recipient is blocking recruitment telegrams
[11:06:32] skipping recipient 'taylorswift': recipient is blocking recruitment telegrams
[11:09:04] queued telegram for 'timbz'
[11:09:04] skipping recipient 'aeruillin': recipient is blocking recruitment telegrams
[11:12:05] queued telegram for 'piss_and_miss'
[11:12:05] skipping recipient 'declanland': recipient is blocking recruitment telegrams
[11:12:05] skipping recipient 'hoarding_and_firebreathing': recipient is blocking recruitment telegrams
[11:12:05] skipping recipient 'jakarta_anyar': recipient is blocking recruitment telegrams
[11:12:05] skipping recipient 'east_svornica': recipient is blocking recruitment telegrams
[11:12:05] skipping recipient 'communist_councils': recipient is blocking recruitment telegrams
[11:12:09] skipping recipient '9_plus_10_equals_21': recipient is blocking recruitment telegrams
[11:12:09] skipping recipient 'dragon_castle': recipient is blocking recruitment telegrams
[11:12:09] skipping recipient 'molibar': recipient is blocking recruitment telegrams
[11:12:09] skipping recipient 'evdorpireat': recipient is blocking recruitment telegrams
[11:12:09] skipping recipient 'valerius_the_whisperer': recipient is blocking recruitment telegrams
[11:12:09] skipping recipient 'vainamoinenia': recipient is blocking recruitment telegrams
[11:12:13] skipping recipient 'wheelerdealer': recipient is blocking recruitment telegrams
[11:12:13] skipping recipient 'nyaryaga': recipient is blocking recruitment telegrams
[11:12:13] skipping recipient 'kencain': recipient is blocking recruitment telegrams
[11:12:13] skipping recipient 'riysa': recipient is blocking recruitment telegrams
[11:12:13] skipping recipient 'gla_stealth_general': recipient is blocking recruitment telegrams
[11:12:13] skipping recipient 'mihiyo': recipient is blocking recruitment telegrams
[11:12:17] skipping recipient 'sifaks': recipient is blocking recruitment telegrams
[11:12:17] skipping recipient 'greater_nevadian_empire': recipient is blocking recruitment telegrams
[11:12:17] skipping recipient 'the_nakamoto': recipient is blocking recruitment telegrams
[11:12:17] skipping recipient 'chicky_nuggers': recipient is blocking recruitment telegrams
[11:15:06] queued telegram for 'the_free_place'

For example^

I'm guessing that the stamp is generates after the telegram is sent to the queue, by the fact that the gap is before the stamp not after. I see that the stamps are generally 181ish seconds from the last "queued" stamp, which makes sense. What I noticed is that the number of nations checked can vary significantly - I'm guessing this is because stamps are only generated for "blocking" and not for being recruitable and added to telegrammer's internal queue? And the variation in how many calls it seems to make are just reverences in the number of "invisible" results from calls that did not return blocked? (i.e. in one case, of 50 calls 47 were blocked and only 3 got added, while in another only 30 were blocked and 20 were added)

-Souls

[Agadar]

Remnant, thanks for the suggestions. I'll try and see what I can do with them.

As for the timestamps you're seeing, my code currently does the following:

1. Check whether the current recipient can receive the telegram I want to send him;
2. If not, then notify the user, move to the next recipient in line, and goto 1.
3. If we can send the telegram, then queue it, notify the user, move to the next recipient in line, and goto 1.

[Great Cyan]

I am looking to recruit nations with your client, but am still stuck.
I have my tdid, my secret code and the Client key, I just don't know how to use the client itself. Please help

[Agadar]

I am looking to recruit nations with your client, but am still stuck.
I have my tdid, my secret code and the Client key, I just don't know how to use the client itself. Please help

Hey, Cyan. Your client key, telegram id, and secret key can be filled out in the top left of the interface. Then, you can select what type of telegram you want to send, which can be either a normal one, a campaign one, or a recruitment one. If it's one of the latter two, then you'll have to insert a region for which you want to campaign or recruit for.

In the 'Filters' section of the interface, you can then select what nations or groups of specific nations or regions and so forth you wish to send your telegram to. For recruiting, you'll probably want to select new nations, whereas for campaigning you'll probably want to target delegates or something.

After you've done all that, simply click the 'Start sending' button and the telegrams will start being sent.

[Agadar]

Version 1.3.0 has been released. Check the details in the changelog on the releases page.

Remnant: I haven't implemented a persistent history yet (i.e. storing telegram history in a file that's loaded on start-up) as I wanted to push some much needed changes to release before taking a brief break from the project to work on some other projects. I'll aim to implement something like that in a later version.

[Imperium Anglorum]

Remnant: I haven't implemented a persistent history yet (i.e. storing telegram history in a file that's loaded on start-up) as I wanted to push some much needed changes to release before taking a brief break from the project to work on some other projects. I'll aim to implement something like that in a later version.

Just serialise the entire program (well, if it's built in such a manner that this would be acceptable).

[Agadar]

Remnant: I haven't implemented a persistent history yet (i.e. storing telegram history in a file that's loaded on start-up) as I wanted to push some much needed changes to release before taking a brief break from the project to work on some other projects. I'll aim to implement something like that in a later version.

Just serialise the entire program (well, if it's built in such a manner that this would be acceptable).

I'm almost sure simply reading/writing from/to a text file is easier (and more elegant) than trying to serialize the entire program.

[Agadar]

Released version 1.4.0, which loads and saves telegram history from and to a file, causing the history to persist even after closing the application, as requested by Remnant.

[Baconbacon123]

Bug: When choosing the option: embassies of <region>, the program stops responding and after 5 hours it still does not respond. Is this a problem or is it just taking extra long to find the nations of the embassies?

[Agadar]

Bug: When choosing the option: embassies of <region>, the program stops responding and after 5 hours it still does not respond. Is this a problem or is it just taking extra long to find the nations of the embassies?

Heya, Bacon. It's not a bug: the 'embassies of <region>' filter is one of the filters that requires the nations dump file. That file is huge, so parsing it can take a long while (about 30 seconds on my own machine), and might not even be possible on older machines that don't have sufficient RAM to store the parsed nations list. It's a performance issue I'm looking to resolve at some point.