Far Shiverpeaks
Community information => Forum & TS Info (services) => Website Announcements => Topic started by: Goldi on August 08, 2015, 22:41:45
-
You can now verify yourself on our Teamspeak server using the GW2 API
How does it work?
Once you log onto Teamspeak, you will be greeted with a message containing a unique link that will link your Teamspeak user with your Forum user. This means your access to teamspeak will be linked with your access to the website that currently uses the GuildWars2 API for that.
For a more detailed description, see Help: Teamspeak Integration (http://farshiverpeaks.com/index.php?page=teamspeakintegration)
Do you get access to my username and password?
No, the only information available through the standard permissions from an API Key is
Account Info
- Account ID
- Display Name (example: test.1234)
- World ID
- Your Guilds
If you have ever used any of the other services, utilizing the GuildWars2 Authenticated API, this is exactly the same.
But i already have access?
If you already have access, you will not see this message and you will keep you access for the time being while the system is being evaluated
So i don't ever have to do this?
Eventually, manual assignment of the FSP Servergroup will be phased out completely in favor of this new automatic system, maybe finally get rid of some of the spies we have had lately?
(http://i.imgur.com/RArKEb7.png)
-
Good job Dansker and thank you I think we all appreciate that!
-
it worked for me after a reinstall of windows, good job ;D
-
Dankser, you da man and of course, Goldi... thanks for working with us to make this possible with the TS! :)
-
Good job all who worked on the system and thank you Goldi for the announcement. Hopefully this will get rid of the spies!
-
What an awesome addition to the teamspeak/forum systems :D hope it gets rid of all the spies :P
-
Regarding to this topic:
https://forum-en.guildwars2.com/forum/community/api/F2P-accounts-WvW-and-API-accessibility
Every can just make a account and then join the ts who do api verify.
So this still gonna be live , or we wait a bit more until they found a solution for this unseen problem?
-
I remember reading that there is also a level check in place now before given permission? Character must be at least level 60 (which is the set level restriction for f2p to join wvw) That would solve the problem for the next little while before F2P characters turn lvl 60 it should be fine, by then the web team will have likely put in a flag stating its an F2P or bought account?
EDIT: Our lord and saviour Dansker.
-
I remember reading that there is also a level check in place now before given permission? Character must be at least level 60 (which is the set level restriction for f2p to join wvw) That would solve the problem for the next little while before F2P characters turn lvl 60 it should be fine, by then the web team will have likely put in a flag stating its an F2P or bought account?
indeed just saw dansler also included that so gj!!!
-
Gonna revoke access for accounts made after the free accounts was introduced, if they do not have the characters permission later today.
From the time it took me to add the characters requirement, to i got the level check created, 6 accounts at level 2 got added to the site... (they have had a day to level it more since then and still level 2...)
-
It's a good idea Dansker ;)
-
Thanks a lot, it isnt working that load of crap.
-
It doesn't work because you didn't read the instructions and have the patience of a 2 year old person (stupid post requires stupid reply...)
it says clearly
API Keyname Invalid. Key name has to be: FarShiverpeaksAPIKey-xxxxxxxxxxxxxxxxxxxxxx
If you only rename the API Key, it might take up to 5 minutes before it is updated.
Might be faster to just make a new key
from what i can see, you attempted it once and decided that you don't want to bother reading the instructions and instead post here?
Watch the video guide https://www.youtube.com/watch?feature=player_embedded&v=GiWnDJkjJYc (https://www.youtube.com/watch?feature=player_embedded&v=GiWnDJkjJYc) if you don't know what to do...
PS you named your key "patjila" in case you don't know what the api key name is
-
Your forum account has been linked with TeamSpeak user: "Tyrandtt"
If you are not given the FSP Server group, please reconnect to the Teamspeak server and see if it worked
If you are still not assigned the FSP Server group, please contact an admin
Could you change the text? ;)
-
Added way to register a music bot with your teamspeak user
This means the music bot is only allowed onto the server if it has the same IP as you do.
Super simple, all you do is join the "Music Bot - join to register" channel and if you are logged into the forum (and verified ofc^^) it will instantly give the user the music bot group
-
Nice :>
-
Hi! I have problems whit the authenticate on TS.
Problem is i cannot click where you supposed to click :) "Sorry for really bad english"
Instead of (Authenticate) i see this.
: Authenticate1 (http://farshiverpeaks.com/index.php?page=tsl&tsu=18280&ls=b49bfaeab8a4e7d1)
-
Dont know wat happend but it working now! :)
-
It's super-easy and it works flawlessly. Good job! :)
-
I have the same problem as Frissyy.
I get the following message when I try logging into fsp TS:
"Far Shiverpeaks Bot" pokes you: Welcome to Far Shiverpeaks Community Teamspeak Server!
23:03 - "Far Shiverpeaks Bot" pokes you: If you want access to the restricted channels you need to be authenticated at
23:03 - "Far Shiverpeaks Bot" pokes you: Authenticate
I have created that API key so that should not be the problem.
Can anyone help me?
Thx (http://farshiverpeaks.com/index.php?page=tsl&tsu=660&ls=a8e8d3a67a715b75)
-
wauw, there was something wrong with the link, stupid me
problem solved :D
-
Thanks for replying :)
-
Lesson of the day, avast sucks.
if you are using avast, the site might have been down for you today (including verification page) because avast was blocking cdn.rawgit.com and all sites that uses resources from cdn.rawgit.com (you can't just block cdn.rawgit.com and everyone who uses it!)
Anyway should be fixed for now until they decide to block ajax.googleapis.com or something as dumb...
-
Good job =)