devicemap-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Werner Keil <>
Subject Re: User-Agents
Date Thu, 27 Nov 2014 12:48:51 GMT
I'm sure, Bertrand can add something regarding the general IP question, but
as far as user agents are concerned, I can only repeat what I said in my
They are common knowledge and come from the device (unless somebody made
one up for whatever reason;-)
So while actually committing to devicemap-data in the repository requires a
contributor agreement, I am not aware of one you have to sign before using

If we ever offered a service, then access to that may require some
click-through agreement where users who intend to contribute new data agree
they do this on their own behalf. Otherwise, say someone does it from an
employer's place or browser there could be a conflict, but that's the same
for all contributions.


On Thu, Nov 27, 2014 at 1:09 PM, eberhard speer jr. <>

> Hash: SHA1
> Hi,
> not sure I can agree with any of the flurry of comments this is
> generating, but the question remains : where did those user-agent
> strings come from ?
> I'm not so much worried about 'rights', the question is were they seen
> in the 'wild' or not : how were they collected ?
> Knowing where they came from helps to determine relevance, urgency and
> data quality.
> For example : do they already occur in the big user-agent file, ie :
> are we regurgitation data ?
> So, maybe we need a protocol for this kind of thing, if only to avoid
> having to trawl thru JIRA a few ua-strings at a time to find the
> precious data.
> esjr
> Version: GnuPG v2.0.22 (MingW32)
> z3oyaoTImir5UEoPDkowKu1vkeRdnD1ckv21DxBaFV2qfd3XanXnwWRU2GZURPPj
> oMofFRydrdXWQ1lGQWc+Ja+1wsELZ+Daa/6TDQ3LKFcxjh69yi3xwQR4scEcAWj7
> sRj1k/W1Jd0hZTMzOUn/REeBZLRjLHxRbUC8QvchUijoKrHvc9UKR3qOoc5hpKrL
> ktMdnF7UrGr7uIcZtwBgLG2LLvK9Wb/YZ+RBePIowxx925eKBGI+hM+Grf7dbHFY
> U40SVTa44UMoHCgvlP/RxwMP//OTK5qQGeWEWpsR4IQP7S1ixJba4dbF1rGqwIo=
> =kPrX

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message