Avatar
teatwo
3589b793b977c4f025175afd792e7c51d26ef683b45cbc66c56c4d14ad53847e
teatwo is derived from "T2". Author: https://api-docs-30b126.gitlab.io

BE YOUR OWN PIPELINE

BE YOUR OWN CONFIG

BE YOUR OWN BUILD FROM SOURCE

もうLinuxだけでいいか。プログラマーの45%らしいし👀

https://japan.zdnet.com/article/35206648/

コンパイル→最適化→インストーラ作成→配信のうち問題になる箇所はな〜んだ?

答え すべて

Is this fashion only california and newyork? Also texas and Florida?

https://japannews.yomiuri.co.jp/culture/manga-anime/20241108-221251/

using NIP-07 between the webview and APK in native app

https://github.com/brugeman/nostr-keystore-cordova-plugin

This month is peaceful

i think of duopoly of mobile. Android is many options and frictions, compdared to iPhone. however Android offers the free of choise.

by the way, original post,"privacy" problem, would be okay if it let user permit whether to emit accountChanged event.

Event design, especially with UX considerations across the signer provider ecosystem.

Attaching an `on` listener to `window.nostr` seems problematic, because `window.nostr` is not a persisted object, but an object injected by a specific provider. For example, when the user wants to switch or multisig signers and the i.e. `providerChanged` or `multisigUpdated` is emitted, `window.nostr` seems like an inappropriate place.

If we consider such case, is it better to only define the standard event name, and not where to listen?

What do you think?

開発中に複垢をサクサク切り替えたくなったらお声がけください💪