You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1035-Deezer serves as a DNS server which returns the current listening of a Deezer, a music streaming service, user.
7
+
8
+
9
+
## How it works
10
+
Due to limitations from the Deezer API, only the **last played music** will be returned, not the current one.
11
+
Once logged, the Oauth user token will be stored in a Redis Database later access.
12
+
When a DNS TXT query will be asked to the server, the software will lookup the Redis server, get the user token and perform an API call to the history endpoint of the Deezer API.
13
+
A DNS response will be returned containing the last played title and it's performer.
14
+
15
+
## Utilization
16
+
In theses examples, ``.dz.bb0.nl`` is the base domain and ``399552895`` is the user Deezer ID we are looking for.
17
+
18
+
### Login
19
+
If the user access token isn't registered in the Redis database, an Oauth authorization URL will be returned
20
+
21
+
Example query :
22
+
```
23
+
❯ dig 399552895.dz.bb0.nl TXT +short
24
+
"Can't get this user playing song."
25
+
"User may not exist."
26
+
"If that's you, connect the app to your Deezer account :"
0 commit comments