> The em element represents stress emphasis of its contents.

> The strong element represents strong importance, seriousness, or urgency for its contents.

HTML Standard
https://html.spec.whatwg.org/multipage/text-level-semantics.html#the-em-element

もうちっと厳密には、 em は stress emphasis だから「発音するときそこを強調する」というもので、結果として、そこが強調されたときとされないときで解釈が変わるような文に使われる。

一方の strong は内容 (contents) の重要性を示すものなので、たぶん強調があろうがなかろうが重要なものは重要なんだよな。こっちはたぶん人間や機械が重要であるとされる場所を発見しやすくする程度のマーカー。

#HTML #documentation

<strong>: 強い重要性要素 - HTML: HyperText Markup Language | MDN
https://developer.mozilla.org/ja/docs/Web/HTML/Element/strong#em_vs._strong

<em> は文章の解釈が変わるような強調で、 <strong> は特定部分の重要性を示すに留まっている、なるほど

#HTML #documentation

太もも😊

🤔

藍ちゃん塗ったー

よし

Galneを0.6に上げた
https://lists.galene.org/galene/87h71f[email protected]/T/#u
これでAndroidクライアント(PoC版?)が動くようになり画面共有が可能に
https://lists.galene.org/galene/87fsgz[email protected]/T/#u
もしこれを使う場合はウェブブラウザで通話した上でアプリで画面共有をする必要がありそう

3年毎に改訂される C++n (n∈ℕ, 0≦n＜100)、3と100が互いに素だから300年間使えるし、実に素晴らしい設計だと思う #適当

物販の内容どうだった？

ヰ世界情緒展、うーんうーん

So, I switched my main server from a dual core atom + 4 GB of memory and 900 GB of disk, to an @OpenBSDAms VM with 1 Xeon core + 1 GB of memory and 50 GB of disk

I had to change a few things...

I thought munin was a lightweight monitoring solution, but not really.

- getting data requires running many commands for each value
- gathering data requires a lot of process on the server and take a lot of time and ~40 MB of memory per process
- rendering the graphs costs a lot of CPU and memory every 5 minutes
- using fast cgi for the graphs is a huge pain

I switched to collectd for collecting data, it uses nearly no CPU and 1 MB of memory :flan_aww:

sending data to a victoria metrics server using the graphite API, it doesn't use much data to transfer things as they can be transferred in bulk

victoria metrics uses like 20 MB of memory to handle 3 systems sending metrics, and almost no CPU

and data can be visualized with grafana which is the worse part of the stack, it draws 52 MB of memory and uses nearly no CPU.

The most boring thing was to create the dashboards on grafana, and that I can't find how to automatically detect the different instances in the datasets...

In the end, this stack is a lot more lightweight and scalable than munin :flan_disappointed:

旅の先々で悪人をスピーカーに変えてく筋骨隆々の七つ星の傷の男、あまりにイヤすぎる