新しいものを表示

Kindleのハイライト集合無知みたいな感じでどうか

電子書籍の方がバックリンクを表現しやすそうだが、アノテーションは誰がやるねん

WPA 3, WPA 2と5 GHz, 2.4 GHz混在環境で、一旦WOA3を切らないとKindleの接続に失敗した。
Quest 2も残ってたな

スレッドを表示

WiFi のパスワード変更
Desktopでルーターに入れれば、管理画面に表示されたQR codeでmobileとtabletで繋げる。Alexaは手動でセットアップすることになるが、Amazon plugはネットワークの変更する項目経由で再接続できた。Switch Botもパスワードのみ更新可能。Kindleは同一ネットワークにあるAndroid版のKindleを用いてセットアップできた。

その🦜 さんがブースト
その🦜 さんがブースト

Re: open letter

I became a member of the Nix team when it formed in '22, because at the time, this important project only had a single maintainer and was virtually incapable of accepting contributions.

It was clear to me that change would be difficult, as Nix is a complex project. We have made great strides as a team in the past 1,5 years, building confidence and trust with the code and each other, and making increasingly significant improvements.

Unfortunately, the largely volunteer team (including me) can't spend the time the project deserves. We are aware of this, and we are looking to expand the team, but that can't happen overnight, due to the nature of the project, the time available, and the latency of async communication.

Communication also seems to be the core of the issue. Our broader communication of the status of the project has been lacking severely. Saying things like "we're still working to improve" and "we're dependent on volunteer time for all of this, including my own" isn't easy - but necessary.

This leads to bad expectations in everyday communication too. Is a to-the-point GitHub comment cold or technical?
We aren't cold. I invite anyone who's skeptical to join the Nix team meetings.

If you're interested in the open letter, I hope you may (re)read it from this perspective.
While it is rooted in real grievances, I can not trust it, because it assumes the worst, and extrapolates a lot. I'm not here to "debunk" the whole letter or anything like that, but these are some of the facts that are important to me:

- We did move the meeting to an American-friendly time (probably 1-3 weeks too late to matter).
- The installer received almost no attention from the Nix team, because it required almost none.
- Eelco tends to make absolute statements, but that doesn't mean they're not up for discussion, and frequently he can be convinced.
- Nix is a critical project, so we tend to lean towards consensus rather than quick action.
- I am not aware of psychological safety issues in the team, and the authors haven't asked me.
- The team is capable of blocking rushed features from any party including DetSys, Example: flake schemas.

I don't know what will happen. I don't oppose the idea of a fork. Competition is good, but I wouldn't like a part of the broader community to be lead by a person or group that appears to prefer threats over collaboration.

I hope something good comes out of this.
Regardless, I will keep contributing where it's needed.

ReScriptってOCamlの環境を錬成せずにLSP等使えるんだっけ

> ライセンスの都合でVRRPを喋れないルータが稼働する場合もあるので敢えて使わない様にしている。代わりに、自宅内のコアルータでPBRを使って
ns-lab.org/digiloog/2021/03/ar

その🦜 さんがブースト

Proton and Standard Notes are joining forces! We’re excited that #StandardNotes will be joining the Proton family to bring end-to-end encrypted note-taking to Proton users.

Standard Notes will remain free, #opensource, and fully supported: proton.me/blog/proton-standard

その🦜 さんがブースト

モダンなフレームワークでもアクセシビリティ対応ちゃんとしてれば比較的しっかり読み上げできるはずだけど、UIライブラリとかいれてるとライブラリによっては爆発四散する

たぶん阿部寛のホームページとかとほほのWWW入門みたいな方がアクセシビリティ高いのよね…。

その🦜 さんがブースト

1日2章進めれば試験までに2周できると思ったけど無理だな
1日1章もできん
:neko_neru_nya:

Miss key ioの不活性アカウントが消えちゃった

諸事情でSSDMを使う必要があるのだが、plasma 消すとthemeも壊れた

Libuntuのgrub themeを消すとファイルを探そうとして一時的に止まるようになったな

古いものを表示
Fedibird

様々な目的に使える、日本の汎用マストドンサーバーです。安定した利用環境と、多数の独自機能を提供しています。