Tapatalk - More Frustrations with Icons, Versions and User Agent String
My frustration with Tapatalk continues. After reinstalling TT for the forums, I'm trying to tweet it so we can get a lot of benefit for forum members. TT has both a free version and a "Pro" version (which we pay for). I paid for the "Pro" version, and the first thing I noticed was that the app icons on the phone are completely the same.
On the left is TT "Free" and on the right is TT "Pro"... they are identical 100%. This is frustrating when testing; and I wonder why they cannot have a sightly different icon for "free" and "pro"...
Then, while testing, I noticed that TT does not consistently follow the standard and send the TT app version number in the User Agent string. Normally, the UA string looks like:
Code:
"Mozilla/5.0 Firefox/3.5.6 Tapatalk/2.4.1"
so there is the "Tapatalk/2.4.2" in the UA string which correctly shows the version number.
However, more often the UA string is:
Code:
"Mozilla/5.0 Firefox/3.5.6 Tapatalk/"
.. where there is no version number. I'm simply confused (again) why TT developers omit this important information from the User Agent string.
So, curious about this, I try to see if certain versions of TT send the UA; so I go to my free and paid "pro" TT apps and try to find the version number in the apps.
Surprise!
There is no "About Tapatalk" page in the phone app and there is no version number to be found anywhere in the app, anywhere.
So, the icon logos on the phone apps are indistinguishable, there is no TT version number in the UA string and there is no TT version information in the app itself.
Referring back to this thread:
Tapatalk Modification for vB3 - Issue with Avatar Icons
I mentioned that we had some "system bot" code:
In this post, I describe that code and how easy it is to create a "system bot" user for Tapatalk (TT):
Basically, its quite easy. We add a hook to... (0 Replies)
This post will be soon moved to the "Web Application" forum so our Tapatalk developer friends can follow an unresolved issue with regard to how the Tapatalk app fetches can caches avatar icons.
We start this process by creating a hook in the vB 3.8 tapatalk file get_online_users.php
($hook =... (2 Replies)
Hello,
FYI, I upgraded our Tapatalk Version to version 4.8.1 today (from version 4.3.2). All seem to be OK but we never know!
Please post in this thread if you see any problems after the upgrade.
Thanks! (1 Reply)
i am having file like this
#!/bin/bash
read -p 'Username: ' uservar
match='<color="red" />'
text='this is only a test
so please be patient
<color="red" />'
echo "$text" | sed "s/$match/&$uservar\g"
so desireble output what i want is if user type MARIA
this is only a test
so please... (13 Replies)
Discussion started by: tomislav91
13 Replies
LEARN ABOUT DEBIAN
msva-query-agent
MSVA-QUERY-AGENT(1) User Contributed Perl Documentation MSVA-QUERY-AGENT(1)NAME
msva-query-agent - query a Monkeysphere Validation Agent
SYNOPSIS
msva-query-agent CONTEXT PEER PKC_TYPE [PEER_TYPE] < /path/to/public_key_carrier
ABSTRACT
msva-query-agent validates certificates for a given use by querying a running Monkeysphere Validation Agent.
USAGE
msva-query-agent reads a certificate from standard input, and posts it to the running Monkeysphere Validation Agent. The return code
indicates the validity (as determined by the agent) of the certificate for the specified purpose. The agent's return message (if any) is
emitted on stdout.
The first three command-line arguments are all required, supplied in order, as follows:
CONTEXT
Context in which the certificate is being validated (e.g. 'https', 'ssh', 'ike')
PEER
The name of the intended peer. When validating a certificate for a service, supply the host's full DNS name (e.g. 'foo.example.net')
PKC_TYPE
The format of public key carrier data provided on standard input (e.g. 'x509der', 'x509pem', 'opensshpubkey', 'rfc4716')
The fourth argument is optional:
PEER_TYPE
The type of peer we are inquiring about (e.g. 'client', 'server')
RETURN CODE
If the certificate is valid for the requested peer in the given context, the return code is 0. Otherwise, the return code is 1.
ENVIRONMENT VARIABLES
msva-query-agent's behavior is controlled by environment variables:
MONKEYSPHERE_VALIDATION_AGENT_SOCKET
Socket over which to query the validation agent. If unset, the default value is 'http://127.0.0.1:8901'.
MSVA_LOG_LEVEL
Log messages about its operation to stderr. MSVA_LOG_LEVEL controls its verbosity, and should be one of (in increasing verbosity):
silent, quiet, fatal, error, info, verbose, debug, debug1, debug2, debug3. Default is 'error'.
COMMUNICATION PROTOCOL DETAILS
Communications with the Monkeysphere Validation Agent are in the form of JSON requests over plain HTTP. Responses from the agent are also
JSON objects. For details on the structure of the requests and responses, please see
http://web.monkeysphere.info/validation-agent/protocol
SEE ALSO msva-perl(1), monkeysphere(1), monkeysphere(7)BUGS AND FEEDBACK
Bugs or feature requests for msva-perl and associated tools should be filed with the Monkeysphere project's bug tracker at
https://labs.riseup.net/code/projects/monkeysphere/issues/
AUTHORS AND CONTRIBUTORS
Jameson Graef Rollins <jrollins@finestructure.net<gt> Daniel Kahn Gillmor <dkg@fifthhorseman.net<gt>
The Monkeysphere Team http://web.monkeysphere.info/
COPYRIGHT AND LICENSE
Copyright AX 2010, Jameson Graef Rollins and others from the Monkeysphere team. msva-query-agent is free software, distributed under the
GNU Public License, version 3 or later.
perl v5.14.2 2013-04-05 MSVA-QUERY-AGENT(1)
01-22-2014
Tapatalk - More Frustrations with Icons, Versions and User Agent String
