I was a bit tricky, I have an 8-core arm64 beast called Moto X Force, it's somewhat close to Nexus 5X, so there are some LineageOS builds around.
KBC Mobile app checks for Safetynet, prints out a warning but works. Kudos to the developers. Bancontact app stops working after checking Safetynet. Whatsapp app can be downloaded from the official website. Telegram is available on F-Droid, Skype can be side-loaded as well.
What else is missing?
I'll probably never do it again, but just in case:
$ECLIPSE_HOME/eclipse -nosplash -verbose \
-application org.eclipse.equinox.p2.metadata.repository.mirrorApplication \
-source http://download.eclipse.org/releases/mars/ \
-destination ~/tmp/mars-mirror-meta
$ECLIPSE_HOME/eclipse -nosplash -verbose \
-application org.eclipse.equinox.p2.artifact.repository.mirrorApplication \
-source http://download.eclipse.org/releases/mars/ \
-destination ~/tmp/mars-mirror-arte
Someone just made me a remark about the style of titles I give to bug tracker tickets. They are apparently too long and actionable, which leaves no space for the text in the description.
I am angry. If there is one area I feel being an expert, this is titles. I've been running a community website for over 15 years and it's been 10 years since my only moderation activity there is fixing titles while other people moderate comments for hate speech and obscenities.
The website is serving 600,000 page views per month, half of what it did in its heyday 6 years ago. Facebook took over its market. Still, it is one of the few websites of its kinds that survived until now.
When I started moderating titles, users took it personally, so I had to back off manual post-moderation and built a dozen pre-moderation filters that forced people to write proper titles. I blocked long sequences of uppercase letters, obscenities, too short and too long titles, duplicate postings, greetings, improper use of punctuation, series of exclamation and question marks and god knows what. It worked, but it drove away some readers from the website.
A few years later, I relaxed the pre-moderation filters and reintroduced post-moderation. This time, I sent automatic notifications to users as titles of their posts changed. I kept receiving complaints, I so I developed a few tricks that would reduce the number of complaints. Instead of rewriting a title, I took user text that represented the essence of the post and put it as the title, keeping the original spelling and even case, so that the user clearly sees that the titles come from his own post.
It takes me ~8 seconds from the key press to a fully functional environment.
I understand that Brussels Airlines has more on its shoulders than properly configured SPF records and decent email content, but still, WTF?
A CS student shows his lab assignment to the professor. The code works and even produces the correct output, but the professor mutters that the code is not OK:
— You have to choose variable names wisely. Names like i, j, foo and bar make your code unreadable. By next time, please use long, mnemonic variable names.
A few weeks later, the same student completes a new assignment and brings it to the professor. This time, his code is full of long_mnemonic_variable_i, long_mnemonic_variable_j, long_mneminic_variable_foo and long_mnemonic_variable_bar.
Just for the record and because I've been asked about this a couple of times, already:
Technically,
A couple of useful git commands for styding big git repositories:
git grep --cached -zIle '' |\
xargs -0n1 git blame -e |\
sed -n 's/^.*(<\([a-zA-Z.]*\)@.*/\1/p' |\
sort|uniq -c|sort -rn >authors-by-line.txt
git for-each-ref --sort=-committerdate \
--format='%(committerdate:short)%(authorname)%(refname:short)' refs/remotes >branches-by-date.txt
It's not a coincidence that notebook docking stations are being sold only with high-end laptops. My Dell e7740 costs over 2000 €. When I bought it in January 2014, I couldn't imagine I'll have trouble making it work under Linux. After all, it was all-intel, already well-supported hardware. The trouble came from a usually dumb piece of hardware: the docking station. I run two 1920x1200 screens in portrait mode, but this freaking docking station"intelligently" merged the two screens into a virtual 3840x1200 screen and presented just that to the notebook.
The bug-o-feature responsible for this is called Displayport Multi-Stream Transport and it was intended to drive multiple displays via one cable using daisy-chaining. When first docking stations with MST support appeared by end 2013, none was prepared for it. It took well over a year before MST support landed in mainline 3.17 kernel. And it will take another year until all major distributions move to 3.17 and past it.
Red Hat itself found it out only when they run into the problem, and it took 6 months before David Airlie came up with a patch to fix this hardware bug. Check out this talk for a good overview of the story.