It is a hack.

Set Jira Administration -> System -> Announcement Banner -> Announcement:

<style type="text/css">
pre {
    white-space: pre-wrap!important;
}
</style>

mongo --eval "JSON.stringify(db.currentOp(true))" | \
tail -n +3 | \
jq -r .inprog[].client | \
sed 's/\(.*\):.*/\1/' \
| sort | uniq -c | sort -nr

• dump connection information in standard JSON format
• remove MongoDB header
• extract IP:port as a list
• trim port
• sort IPs by freqencies

cat book.txt | \
tr '!()[]{};:",<.>?“”‘’*/\r' ' ' | \
tr ' ' '\n' | \
grep -a -P "^[\p{L}\p{N}\-']+\$" | \
grep -a -P -v "^[\p{N}\-']+\$" | \
sed "s/'s\$//" | \
sed "s/^'//" | sed "s/'\$//" > words.txt

cat words.txt | \
sort | uniq -c | \
sort -nr | \
cut -c9- > words_desc.txt

• replace punctuations with space; remove \r from `\r\n’
• one word per line
• keep only words composed of unicode letters, numbers, hyphen and apostrophe
• remove pure numbers
• remove ’s
• remove starting and ending apostrophe

• output words.txt

• sort and count unique words

• sort by freqency in descending order

• trim the frequency column

• Mobi Format Description: http://wiki.mobileread.com/wiki/MOBI
• Python lib: https://github.com/kroo/mobi-python

Design

The UA detection algorithm is a pipeline containing 3 steps:

1. Scan: scan products and its corresponding comments from a UA string.
2. Parse: parse device info from products.
3. Detect: detect device model by looking up in a database and get related info, e.g. screen resolution.

Scan

The scanner scans the user agent string into products. Each product has its own name, version and comments. e.g.

For user agent string:

Mozilla/5.0 (Linux; U; Android ROM v3; en-us; ALCATEL ONE TOUCH 991 Build/GRK39F) AppleWebKit/533.1 (KHTML, like Gecko) Version/4.0 Mobile Safari/533.1

Its products are:

• Mozilla/5.0
  • Linux
  • U
  • Android ROM v3
  • en-us
  • ALCATEL ONE TOUCH 991 Build/GRK39F
• AppleWebKit/533.1
  • KHTML, like Gecko
• Version/4.0
• Mobile
• Safari/533.1

Parse

The parser then parses the scanned products and fill the information into a Device struct, e.g.

Mozilla:  5.0
Linux:    true
Security: U
Android:  ROM v3
Locale:   en-us
Model:    ALCATEL ONE TOUCH 991
Build:    GRK39F
Webkit:   533.1
Version:  4.0
Mobile:   true
Safari:   533.1

Detect

The detector is then able to use the parsed Device structure to detect the device type & related info: vendor, screen resolution, tablet-or-not, etc, by searching in a device database.

Design Goals

Accuracy

The accuracy of the detection is determined by the completeness of the device database, then we might have to migrate the data from multiple sources. Automatic tests will be adapted from those resources.

References

Detectors

• WURFL
• HandsetDetection
• DeviceMap
• Mobile-Detect
• Device-Detector
• Detector.

Parsers

• user agent
• uaparser

This is an insightful list from Henry Ward:

• How do I get employees to perform better? Tell them what they are doing well.
• How do I give negative feedback? By being curious.
• How do I decide what to delegate? Delegate the work you want to do.
• How should I prioritize? Fix problems. Then prevent problems.
• How should I grade employees? Don’t. Teach them to self-evaluate.
• When do I fire somebody? When you know they can’t succeed.
• How do I fire somebody? By apologizing for our failures.
• Why can’t I just tell people what to do? Because the more responsibility you have, the less authority you have.
• How do I know if I am a good manager? Employees ask you for advice.
• How do I know if I have good management team? Shit rolls uphill.

A short investigation on reliable persistence:

• Crash consistency is hard but possible at a huge performance cost

• Data safty must rely on distributed solution

  • Raft

• Perhaps we should just give up manual fsync and rely on

  • OS background flush
  • corruption detection & correction at startup
  • replication