人は皆、生まれたときから死へ向かっている。

星の降る夜、いつか遠い来世で俺を待っている恋人に聞いてみたい——「お前は今、> 幸せか？」

生きたがっているのか、それとも死にたがっているのか？

生と死の境界は、たった50cmのフェンスの幅よりも、もっと狭い。

それを飛び越える一瞬は、ビルの隙間に落ちる流れ星をまたぐようなものだ。

幸福でも、不幸でもない。

生きているふりをしているだけで、本当に生きていない人間は、いつかその報いを> 受ける日が来る。

その日まで、俺は自分自身の人生の傍観者だった。

運命が俺を選んだのは、もしかしたらそのせいかもしれない。

「神様、もう少しだけ……」

• The following steps are described using Microsoft® Word for Mac Version 16.93 (25011212).

• Open System Settings on macOS with English (United States) as primary language.
• Click General -> Language & Region. Scroll all the way to the bottom.

• Press + at the bottom of Applications list.

• Select Microsoft Word.app for Application.
• Select 日本語 ー Japanese for Language.

• Click Add button. Microsoft Word will be listed with 日本語 ー Japanese in the Applications list.

• Open Microsoft® Word for Mac or run open --new /Applications/Microsoft\ Word.app in the terminal.
• Default Editing Language Changed dialog box will be shown in Japanese.

• Open Microsoft Word document with non-Hiragana (平仮名) Japanese text: Katakana (片仮名) and/or Kanji (漢字).

• Select the entire example Japanese text. Here’s an example.

  日本語能力試験

• Click ルビ (Ruby / Phonetic Guide…) button inside theHome | Font Ribbon menu, and click OK.

• Furigana (振り仮名/読み仮名/ルビ) is shown.

  日本語能力試験にほんごのうりょくしけん

Fire in the works.

One moment in awe, one moment in aw.

Life in the years.

Some are latent, some are temperament.

The blink of an eye.

The blip in the sky.

Momentarily, mirthfully.

Temporarily, tearfully.

Ebbing in the dark.

Quivering in the heart.

Sign In with Google Account

  Future<String> _signInGoogleAccount() async {
    final GoogleSignInAccount googleUser = await _googleSignIn.signIn();

    final GoogleSignInAuthentication googleAuth =
        await googleUser.authentication;

    final FirebaseUser user = await _auth.signInWithGoogle(
      accessToken: googleAuth.accessToken,
      idToken: googleAuth.idToken,
    );

    assert(!user.isAnonymous);
    assert(user.email != null);
    assert(user.displayName != null);
    assert(await user.getIdToken() != null);

    final FirebaseUser currentUser = await _auth.currentUser();
    assert(user.uid == currentUser.uid);

    print("user name: ${user.displayName}");
    print("user email: ${user.email}");
    print("user photoUrl: ${user.photoUrl}");

    return 'signInGoogleAccount succeeded.... $user';
  }

E/flutter ( 7147): [ERROR:flutter/shell/common/shell.cc(184)] Dart Error: Unhandled exception:
E/flutter ( 7147): PlatformException(sign_in_failed, com.google.android.gms.common.api.ApiException: 12500: , null)
E/flutter ( 7147): #0      StandardMethodCodec.decodeEnvelope (package:flutter/src/services/message_codecs.dart:551:7)
E/flutter ( 7147): #1      MethodChannel.invokeMethod (package:flutter/src/services/platform_channel.dart:292:18)
E/flutter ( 7147): <asynchronous suspension>
E/flutter ( 7147): #2      GoogleSignIn._callMethod (package:google_sign_in/google_sign_in.dart:217:58)
E/flutter ( 7147): <asynchronous suspension>
E/flutter ( 7147): #3      GoogleSignIn._addMethodCall.<anonymous closure> (package:google_sign_in/google_sign_in.dart:269:28)
E/flutter ( 7147): #4      _RootZone.run (dart:async/zone.dart:1374:54)
E/flutter ( 7147): #5      _FutureListener.handleWhenComplete (dart:async/future_impl.dart:153:18)
E/flutter ( 7147): #6      Future._propagateToListeners.handleWhenCompleteCallback (dart:async/future_impl.dart:612:39)
E/flutter ( 7147): #7      Future._propagateToListeners (dart:async/future_impl.dart:668:37)
E/flutter ( 7147): #8      Future._addListener.<anonymous closure> (dart:async/future_impl.dart:351:9)
E/flutter ( 7147): #9      _microtaskLoop (dart:async/schedule_microtask.dart:41:21)
E/flutter ( 7147): #10     _startMicrotaskLoop (dart:async/schedule_microtask.dart:50:5)

• Note the PlatformException(sign_in_failed, com.google.android.gms.common.api.ApiException: 12500: , null) line about SIGN_IN_FAILED error.
• The local debug.keystore file under $HOME/.android/ or $USERPROFILE\.android\ directory is not recognized by Firebase Authentication services while bundled with the debug version of the Flutter app.

Upload SHA1 from Debug Key Store to Firebase

• Get SHA1 from debug.keystore file.

keytool -list -v \
-keystore debug.keystore \
-alias androiddebugkey \
-storepass android \
-keypass android

• Create debug.keystore file again at the same location if required.

keytool -genkey -v \
-keystore debug.keystore \
-storepass android \
-alias androiddebugkey \
-keypass android \
-keyalg RSA \
-keysize 2048 \
-validity 10000

• Add SHA1 obtained from debug.keystore file to the settings under Firebase Project ID.

https://console.firebase.google.com/project/FIREBASE_PROJECT_ID/settings/general/

• Download google-services.json file to FLUTTER_PROJECT_ROOT/android/app path.
• Sometimes, it helps to manually remove the installed app on device.
• Run the app against the device again. It should work now.
• See below output after signInGoogleAccount() being executed.

W/BiChannelGoogleApi(11571): [FirebaseAuth: ] getGoogleApiForMethod() returned Gms: com.google.firebase.auth.api.internal.zzal@de661b2
D/FirebaseAuth(11571): Notifying id token listeners about user ( EZG2LN2URXGNBRGFTO2FZCQZOZQ1 ).
D/FirebaseAuth(11571): Notifying auth state listeners about user ( EZG2LN2URXGNBRGFTO2FZCQZOZQ1 ).
D/FirebaseApp(11571): Notifying auth state listeners.
D/FirebaseApp(11571): Notified 0 auth state listeners.
I/flutter (11571): user name: Admin Istrator
I/flutter (11571): user email: admin.istrator@example.com
I/flutter (11571): user photoUrl: https://lh3.googleusercontent.com/-1LMWBMYEMSC/AAAAAAAAAAB/AAAAAAAAAAA/B4GC9SMQWHY/S96-C/photo.jpg

Sign Out with Google Account

• To sign out, use the below code snippets.

  Future<String> _signOutGoogleAccount() async {
    await _auth.signOut();
    await _googleSignIn.signOut();
    return 'signOutWithGoogle succeeded....';
  }

• See below output after _signOutGoogleAccount() being executed.

D/FirebaseAuth(11571): Notifying id token listeners about a sign-out event.
D/FirebaseAuth(11571): Notifying auth state listeners about a sign-out event.
D/FirebaseApp(11571): Notifying auth state listeners.
D/FirebaseApp(11571): Notified 0 auth state listeners.

pip3 install powerline-status

• Enable Powerline in Vim.

Append below lines in ~/.vimrc file.

python3 from powerline.vim import setup as powerline_setup
python3 powerline_setup()
python3 del powerline_setup

• Start a new terminal session.

#!/usr/bin/env bash

for key in ~/.ssh/id_*; do
    ssh-keygen -l -f "${key}"
done | uniq

• Generate the Ed25519 SSH keys.

ssh-keygen \
    -o -a 100 \
    -t ed25519 \
    -f ~/.ssh/id_ed25519 \
    -C "$(id --user --name)@$(hostname --short)"

• Read Risan’s post about Ed25519 for more details.

_includes/
├── analytics.html

• Insert {% include analytics.html %} after {% include head.html %} line in the _layouts/default.html file. This step ensures that the tracking code template will be included in all generated Jekyll pages.

    {% include head.html %}
+   {% include analytics.html %}

• Run jekyll build to generate the Jekyll site using the Google analytics template. You will notice that Google Analytics tracking code is included in the generated pages. For example, _site/index.html.

• Otherwise, run jekyll serve or bundle exec jekyll serve command to serve and test your site locally at localhost:4000.

Credits

Read Michael Lee’s post or Jekyll documentation on further customizing Google analytics for Jekyll for use only in production environment.

Automatic dependent surveillance – broadcast (ADS–B) is a cooperative surveillance technology in which an aircraft determines its position via satellite navigation and periodically broadcasts it, enabling it to be tracked.

From Realtek

The RTL2832U is a high-performance DVB-T COFDM demodulator that supports a USB 2.0 interface.

Acknowledgements

Most of the below guidelines are based on or build upon on information available form SonicGoose | Using dump1090 in Windows page.

Installation

RTL1090

Use Installer and Maintenance Utility.

Special thanks to Jetvision.de, as they provided the ADS-B decoder and its Installer and Maintenance Utility for Windows that works with RTL2832U sticks called RTL1090.

Install into %USERPROFILE%\rtl1090 folder.

Use the below command to generate the checksums of the downloaded files.

 find . -type f -not -name *.sha1 \( -exec sha1sum "$PWD"/{} \; \) | tee rtl1090.sha1

You will get similar below checksums.

b9e4a7ecef7366d9864f86f24f7754ea121ebfc3 *./0_readme.important.txt
a5b1b9945f039114c9967c79b881659d8280a1e6 *./1_DO READ THIS FIRST.all.versions.txt
c9ae6e7d37a3dc028fe8e6d7723b5611dcf1021a *./libusb-1.0.dll
4e880fc7625ccf8d9ca799d5b94ce2b1e7597335 *./msvcr100.dll
7c4dac98526c0847658423bdd5d0164e2a02d661 *./radar1090.txt
2541b3b4f3df3c58123212e073ffeb1223d5d259 *./rtl1090.exe
a76da1b44f7c3c4235d6ed6b1530905bf9393c12 *./rtlsdr.dll
6740d894a7a7e39255c9aa8d1b74f992340f2874 *./terms_of_use.pdf
648c1d8bdc944c036fc80cee5dd0a1456f30f74c *./tmp/rtl-sdr-release/AUTHORS
add0478984908706aab929caf1721999d82f3a48 *./tmp/rtl-sdr-release/COPYING
a1b087217d26810acdf85a9db199e8f3605b743a *./tmp/rtl-sdr-release/COPYING.libusbx
79e0eab921d6a2ac2a88ada2b323d8b0c0217609 *./tmp/rtl-sdr-release/COPYING.pthreads-win32
fca194c07e6aefbb4367268b233d3d975e6864cc *./tmp/rtl-sdr-release/README
9885de99781aeedeaf62b2ef4c6811476751ceb8 *./tmp/rtl-sdr-release/README.windows.txt
755b82b8e445b7f57194920ff9e9a0ebcacaadda *./tmp/rtl-sdr-release/rtl-sdr.h
8fa476f22847a6635c9a1687c9749f7311f1e8ae *./tmp/rtl-sdr-release/rtl-sdr_export.h
4ecdc845c2dddb6c81b2d6761acc06d23899aa88 *./tmp/rtl-sdr-release/x32/convenience_static.lib
319190b233f1764496ecbb8cd814961d6b3d1088 *./tmp/rtl-sdr-release/x32/pthreadVC2-w32.dll
437cabb939bd5ce1b9e7816334e6d80ac6e906fe *./tmp/rtl-sdr-release/x32/rtlsdr.lib
a020b2f1cb9dabf5fd0b157c5d531154b8806dc3 *./tmp/rtl-sdr-release/x32/rtlsdr_static.lib
925ed3d5b488e519bacfb3184cdc24484627d4c2 *./tmp/rtl-sdr-release/x32/rtl_adsb.exe
ae56c125b92d9755b061412187bddf75d547de22 *./tmp/rtl-sdr-release/x32/rtl_eeprom.exe
17a04ff079591570a413d10a9b6e563bef0e556a *./tmp/rtl-sdr-release/x32/rtl_fm.exe
c72ad91081860a17c8a53439e3df3cf36d176ddd *./tmp/rtl-sdr-release/x32/rtl_power.exe
fb02433e72ad8618fffd6c04d86acf316483f421 *./tmp/rtl-sdr-release/x32/rtl_sdr.exe
3121f9a5aa7f78aaac4bc3ce9e94d0708ce763f8 *./tmp/rtl-sdr-release/x32/rtl_tcp.exe
acde4d237c61f725a0140c97798d15faf6cbec10 *./tmp/rtl-sdr-release/x32/rtl_test.exe
fa3763d410fed3350b954ea6bbf543e04627ee35 *./tmp/rtl-sdr-release/x64/convenience_static.lib
d890275bc0da86b68906c6118da4a5b79e8bdf19 *./tmp/rtl-sdr-release/x64/libusb-1.0.dll
e9d2538f3e330c5096009ea1d2a49384b0acb89e *./tmp/rtl-sdr-release/x64/pthreadVC2-w64.dll
f857a1b082220e062ab4ff82870da01593f5e1ed *./tmp/rtl-sdr-release/x64/rtlsdr.dll
e6999607bb31a830d567ac7b74c46c760ab8f65e *./tmp/rtl-sdr-release/x64/rtlsdr.lib
2c42dfca791bda4dd4b511156daff238c4719c3e *./tmp/rtl-sdr-release/x64/rtlsdr_static.lib
7b471907ac4aaac14b75378d74c71b2f882f20a7 *./tmp/rtl-sdr-release/x64/rtl_adsb.exe
947088c477f64c0207d350d6b3f8e37577603af1 *./tmp/rtl-sdr-release/x64/rtl_eeprom.exe
9278ced4d13a7524c62c31421dddc6b43dbaa31b *./tmp/rtl-sdr-release/x64/rtl_fm.exe
d5ffcab88a5db1fb824e3aa293db5883c18d094e *./tmp/rtl-sdr-release/x64/rtl_power.exe
5544d923bed84a498502953770bbbc332a3e6f53 *./tmp/rtl-sdr-release/x64/rtl_sdr.exe
d7d25f7278af5983683c61625aba5a8a7d2827f1 *./tmp/rtl-sdr-release/x64/rtl_tcp.exe
79a93686d92e80b0b0f433d91f761fb37331f5ee *./tmp/rtl-sdr-release/x64/rtl_test.exe
beddd072a72c640f8ecbea283f39bd328b43a7aa *./tmp/rtl1090.zip
5fb06bb704bc64aab1fc34f24aced49316401d5e *./tmp/rtlsdr.zip
9da1268da75498938a9c908507a8571783eb6a31 *./zadig.exe

To verify the checksums of the downloaded files on your side, use the below command.

sha1sum -c rtl1090.sha1

WinUSB Driver for RTL2832U

Plug in your USB dongle and then install RTL1090. All of the necessary libraries and drivers are located in %USERPROFILE%\rtl1090 directory.

You may have to run the Zadig setup, which you will find in the RTL1090 folder.

Make sure the USB ID is 0BDA:2838 Realtek Semiconductor Corp.

Dump1090

Once that’s done, download dump1090 for Windows and unzip the contents of the file to the same directory as RTL1090. Don’t overwrite any existing files. You should now have dump1090.exe and dump1090.bat among your RTL1090 files.

Extract dump1090 to %USERPROFILE%\dump1090 folder.

Use the below command to generate the checksum of the downloaded archive.

 sha1sum.exe dump1090-win.1.09.0608.14.zip | tee dump1090-win.1.09.0608.14.zip.sha1

To verify the checksum of the downloaded archive on your side, use the below command.

sha1sum -c dump1090-win.1.09.0608.14.zip.sha1

Then, you will see that you get similar below result.

d933e420d59ac5be328b40768c6202d92139190f *dump1090-win.1.09.0608.14.zip

The pthreadVC2.dll library is included by default at the time of writing. If you are missing pthreadVC2.dll, copy pthreadVC2.dll from %USERPROFILE%\dump1090\tmp\rtl-sdr-release\{x32|x64} folder into %USERPROFILE%\dump1090 folder.

Use the below command to generate the checksums of the extracted files in %USERPROFILE%\dump1090 folder.

find . -type f -not -name '*.sha1' \( -exec sha1sum "$PWD"/{} \; \) | tee dump1090.sha1

You will get similar below checksums.

26d3ff9f57f6c88374b0bd9a6deb1a282615e5ac *./dump1090.bat
a41439f4fccd49a82b918bf0c3491a0291433578 *./dump1090.exe
025e9a24fde104b126298257b8b0662509b21a66 *./libusb-1.0.dll
4e880fc7625ccf8d9ca799d5b94ce2b1e7597335 *./msvcr100.dll
210af5a3682af9df8585f4e88ac89e436de120f9 *./pthreadVC2.dll
213b8a0b52b79cd3373bd459b29a4b32a98cf385 *./public_html/config.js
9eae459ab27d2002c363a65ccf53a7a554a7e4a3 *./public_html/coolclock/coolclock.js
9343008ad38988a03955090f60a05d2ee16b0942 *./public_html/coolclock/excanvas.js
57aaf42f34543ceac0b51053bebc51480a9d5c35 *./public_html/coolclock/moreskins.js
c56a1ad59179624b2c366cfa4fa2b252e8d81e8c *./public_html/extension.js
a67ba48e9f3cda7c8482aaefbcca01e92acdd8e1 *./public_html/gmap.html
501f973efab87e108f469b640edb7b8a0a815e85 *./public_html/options.js
c8f63bec7ef8a934d1ff6e315a72c0c6a46e7f81 *./public_html/planeObject.js
6e3309febf5908402aca29d6e92c86bd2e6e46a7 *./public_html/script.js
0a9e36434fa24e467e38b35701f70641fd6f4601 *./public_html/style.css
21815d04e305640855371feed14651cfc1301032 *./readme.txt
9ab47e4495e94237b0dc7538049062652e89c91a *./rtlsdr.dll
7ee8ef57a51f383f26f72dbbad3d3c862f7c7be0 *./view1090.exe

To verify the checksums of the downloaded files on your side, use the below command.

sha1sum -c dump1090.sha1

Configuration

The below text is verbatim copy from SonicGoose.

Running dump1090.exe -h in a command prompt window will return a list of all of the parameters supported by dump1090.

dump1090.exe --interactive --net --net-ro-size 500 --net-ro-rate 5 --net-buffer 5 --net-beast --mlat
pause

The second line, pause, ensures the application window stays open for you to see.

Issue(s)

Use Flightradar24 feeder with own dump1090 program

From Flightradar24

If you already have the necessary ADS-B equipment it’s quick and easy to share your data with Flightradar24. When you share data with Flightradar24 you get a free premium account.

Flightradar24 includes its own mr-dump1090.exe program. The issue is that I do not want to use the mr-dump1090.exe program provided by Flightradar24. Use the dump1090 that was earlier extracted into %USERPROFILE%\dump1090 folder.

Check the fr24feed command options.

fr24feed.exe --fr24key=fr24sharingkey --receiver=beast-tcp --host=localhost:30005 --bs=no --raw=no --logmode=3 --bind-interface=127.0.0.1

Note that --host option sets to localhost:30005. Note the port is 30005.

The fr24feed program is feeding data to Flightradar24 servers when the below line(s) is shown.

2015-08-31 18:00:00 | [feed][i]sent 1 AC in 1 packet

Once the fr24feed program is running, the below pages should be accessible in your localhost through port 8754.

• FR24 Feeder Status - index.html
• FR24 Feeder Settings - settings.html
• FR24 Feeder Tracked Aircraft - tracked.html
• FR24 Feeder Status Variables - monitor.txt

Under ~/qtproject/qtquickcontrols directory,

$ git diff
diff --git a/src/dialogs/plugin.cpp b/src/dialogs/plugin.cpp
index 74672f6..f7523f5 100644
--- a/src/dialogs/plugin.cpp
+++ b/src/dialogs/plugin.cpp
@@ -59,7 +59,7 @@
 #include <private/qguiapplication_p.h>
 #include <qpa/qplatformintegration.h>

-//#define PURE_QML_ONLY
+#define PURE_QML_ONLY
 //#define DEBUG_REGISTRATION

 static void initResources()
$

We need to build qtbase, qtxmlpatterns, qtdeclarative, and qtquickcontrols sources from their stable branch in correct sequence, with the developer build options being set with qtbase module.

Under ~/qtproject/qtbase directory,

$ ./configure -developer-build -opensource -confirm-license -verbose
$ time make -j 64

Under ~/qtproject/qtxmlpatterns directory,

$ ../qtbase/bin/qmake && time make -j 64

Under ~/qtproject/qtdeclarative directory,

$ ../qtbase/bin/qmake && time make -j 64

Under ~/qtproject/qtquickcontrols directory,

$ ../qtbase/bin/qmake && time make -j 64

Under ~/qtproject directory,

$ qtbase/bin/qmlscene qtquickcontrols/examples/quick/dialogs/systemdialogs/FontDialogs.qml

The above steps was used to implement input for entering non-standard font size for Qt Quick Controls Font Dialog.

Special thanks to Liang Qi and J-P Nurmi for helping along the way.