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 OPENSOLARIS
dat_cno_create
dat_cno_create(3DAT) Direct Access Transport Library Functions dat_cno_create(3DAT)NAME
dat_cno_create - create a CNO instance
SYNOPSIS
cc [ flag... ] file... -ldat [ library... ]
#include <dat/udat.h>
DAT_RETURN
dat_cno_create (
IN DAT_IA_HANDLE ia_handle,
IN DAT_OS_WAIT_PROXY_AGENT agent,
OUT DAT_CNO_HANDLE *cno_handle
)
PARAMETERS
ia_handle Handle for an instance of DAT IA.
agent An optional OS Wait Proxy Agent that is to be invoked whenever CNO is invoked. DAT_OS_WAIT_PROXY_AGENT_NULL indicates that
there is no proxy agent
cno_handle Handle for the created instance of CNO.
DESCRIPTION
The dat_cno_create() function creates a CNO instance. Upon creation, there are no Event Dispatchers feeding it.
The agent parameter specifies the proxy agent, which is OS-dependent and which is invoked when the CNO is triggered. After it is invoked,
it is no longer associated with the CNO. The value of DAT_OS_WAIT_PROXY_AGENT_NULL specifies that no OS Wait Proxy Agent is associated with
the created CNO.
Upon creation, the CNO is not associated with any EVDs, has no waiters and has, at most, one OS Wait Proxy Agent.
RETURN VALUES
DAT_SUCCESS The operation was successful.
DAT_INSUFFICIENT_RESOURCES The operation failed due to resource limitations.
DAT_INVALID_HANDLE The ia_handle parameter is invalid.
DAT_INVALID_PARAMETER One of the parameters was invalid, out of range, or a combination of parameters was invalid, or the agent
parameter is invalid.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Interface Stability |Standard: uDAPL, 1.1, 1.2 |
+-----------------------------+-----------------------------+
|MT-Level |Safe |
+-----------------------------+-----------------------------+
SEE ALSO libdat(3LIB), attributes(5)SunOS 5.11 16 Jul 2004 dat_cno_create(3DAT)
01-22-2014
Tapatalk - More Frustrations with Icons, Versions and User Agent String
