-
@ 77911886:4b218091
2025-02-25 12:36:24
現在のブロック高さ:885249
<推奨手数料> 単位sats/vB
最速:5
1時間以内:5
[参考] 直近6ブロックの最小手数料
2,3,4,4,3,3
[参考] 次ブロック候補の最小手数料
5
-
@ deabde48:7254d531
2025-02-25 12:36:20
10分前だおしで福岡空港に到着しました。いい調子！ (@ 福岡空港 in 福岡市, 福岡県) https://www.swarmapp.com/satetsu/checkin/67bdb7b096e803120dc241e5?s=j18TlEDxv7zDzGIZsW4rEfu0hRI
-
@ 0c8f18ab:1bdaf719
2025-02-25 12:36:19
記事は、感情的なプロパガンダを通じて、どれくらい簡単に人を操ったり、騙したりできるかについて考える内容だよ。110サトシの投げ銭がついてて、コメントもできるみたい！
https://stacker.news/items/896511
-
@ 101b30ee:18a46a45
2025-02-25 12:36:03
俺には出来なかった高み
-
@ 2450d704:08ec15f0
2025-02-25 12:35:52
3等 (@ GiGO 池袋3号館 in 豊島区, 東京都) swarmapp.com/c/9otlLHU03mS
-
@ 5aaccfdd:747c5c90
2025-02-25 12:35:49
CPAP、人生変わる
-
@ 1f617e36:e66e9caa
2025-02-25 12:35:43
糖尿病治療薬のエースだが、注意点がいっぱい！「メトホルミン」解説 宮舞モカのお薬ラジオ #1【VOICEPEAK解説】
https://www.nicovideo.jp/watch/sm43407699
-
@ 2efaa715:3d987331
2025-02-25 12:35:31
Just add the line "so what did I do?" and continuously re-read the poem.
-
@ 434f9799:2d548c15
2025-02-25 12:35:29
确实
-
@ f8978eb7:7f8e8a50
2025-02-25 12:35:25
俺は痩せる食べながら痩せる！
-
@ d8f38b89:ccf72848
2025-02-25 12:35:16
Nostr DM
-
@ 0bdcf001:9fb34f96
2025-02-25 12:35:04
楽しそう
https://github.com/ggerganov/ggwave
-
@ 3ce2b51d:36fc72c7
2025-02-25 12:35:00
✄------------ 21:35 ------------✄
-
@ a6f1f450:29388f0b
2025-02-25 12:34:58
ZZ全部見た人はこのサイレント・ヴォイスの公式MAD見るべき
前も紹介したっけ？まぁ何回紹介してもええやろ
https://youtu.be/XJWRyF7FfZM
-
@ f8978eb7:7f8e8a50
2025-02-25 12:34:49
🍨２つ、ピュレマロ一袋、ハイチュウ5個、黄金糖7個
-
@ 26803787:f553fd22
2025-02-25 12:34:39
https://www.ifixit.com/News/108371/right-to-repair-laws-have-now-been-introduced-in-all-50-us-states
Right to Repair Laws Have Now Been Introduced in All 50 US States - iFixit
アメリカ全50州で修理する権利法案が提出されました。
iFixitは11年間、修理する権利のために活動してきました。
消費者が製品を修理する権利を求める声が高まっています。
-
@ 96203d66:643a819c
2025-02-25 12:34:29
その場にいる人だけが音で繋がるSNS、誰が投稿したのかverifyできる
-
@ 101b30ee:18a46a45
2025-02-25 12:34:23
教育用...？
https://x.com/ctgptlb/status/1894364104057655520
-
@ 06b7819d:d1d8327c
2025-02-25 12:34:23
Text of the objection
Below you will find the key topics of the concerns we have in adding a digital credentials API to the web platform (some of which likely will be technical addressable). However, some of these topics haven’t yet been discussed, or else have been discussed but have not led to proposals that will address the issues. These are issues that we believe need to be addressed, and it would be better to continue to iterate on them within the Web Incubation Community Group rather than moving the work to the FedCM Working Group.
On top of this, we see fundamental concerns beyond what can be technically solved. This has led us to question altogether whether this work is something that a working group should commit time to at all (now or in the future)—if work has the potential to lead to further social issues that are reinforced through tools we build, we question whether those tools are worth building. In this case, we lean towards keeping these use cases within the application layer, rather than potentially perpetuating the harms through standardizing this work too early. At the very least, we believe this work should not progress to standardization track status until we are certain these fundamental concerns are addressable. Below are the issues we see.
Perpetuates sharing of personal data by making it more available via a browser API
In simple terms, promoting the common use cases and flows of digital credentials to a browser API makes this data more accessible—it would therefore be consumed more, according to Jevons Paradox. This further request of data means that more users will be expected to hand over third-party-attested data, which will reduce their overall Web privacy. This leads to a regression of privacy for users. This topic has been discussed, but as of yet we’re not convinced the current technical proposals will address this issue.
Increased centralization through subtle tradeoffs
On the topic of centralization, since most of these systems are built around the “digitization of trust,” the approach most commonly used is to effectively digitize the trust we have in institutions and map that onto the Web. For example, the concept of a proof of personhood credential would not be trusted if it can be only self-attested. Instead, that proof is considered trusted only if it comes from a known and trusted third-party issuer. The implication of “digitization of trust” is it will lead to further centralization on the Web, just as we’ve seen with similar centralization of single sign-on systems (a limited number of providers handling the majority of use cases). This begs the question: what additional harms arise from these tradeoffs of centralizing trust in a limited number of institutions? Is further centralization of trust a net gain for the Web?
Additional centralization is also likely to occur due to the “trust” needed around wallets, as users may modify or share their credentials in a way that undermines the trust of the system. For example, if a user were to share their credential and keys (or have them stolen) then it would allow someone other than the subject of the digital credential to present it, thereby leading to impersonation attacks. The commonly suggested approach to addressing impersonation attacks is to require the keys be secured by the operating system (often backed by secure enclaves) and have the wallet software certified. But this introduces a tradeoff: it centralizes around a limited set of “trusted” operating systems and wallets that won’t allow the user to control or modify the wallet software, credentials, or keys to their desires. This ultimately undermines a user’s ability to control the software they run on their devices. In effect, this reintroduces the same issues we were faced with by the Web Environment Integrity proposal, but in slightly varied forms. We believe the Web should not be endorsing this level of centralization, as it will undermine user agency in what users can do with their devices and what software should run on it by prioritizing issuers and verifiers above users.
Content will be moved from the deep web to the “attributed deep web”
As more sites choose to restrict content and site registration behind “proof of personhood” and other uses of digital credentials, we will inadvertently further restrict the openness of the web.
A good example of this is social media companies like X and Instagram have started to build their walled gardens higher by requiring login to view content and in circumstances require identity verification. While there are moral arguments to be made that this is helpful for broader society (such as to reduce misinformation from bots), if we set aside the type of content being shared and focus instead on the pattern being employed we can see how this will lead to further restrictions on many different forms of content on the Web, which ultimately reduces openness. This problem will become more exacerbated as digital IDs become more available and easier to request further raising the walled gardens of the largest platforms today. The question we should be asking ourselves is not whether we agree with the usage of this for a particular use case, but rather whether we believe the pattern should be endorsed on the Web.
To further exemplify this problem of openness, the World Bank estimates that roughly 850 million people do not have a form of legal identity today. If we decided to endorse the utilization of proof of identity as a method of registration to certain sites, we'd effectively endorse a system that removes 850 million people from accessing those sites, creating further information divides. This would be a net loss for the openness of the Web, and could even lead to second-order effects that fracture the “single web” principle (if only citizens of certain countries become able to access certain sites).
What happens when this proof of personhood gets used on social media sites or other forums where political topics are discussed? At that point we have to expect that it will lead to a loss of freedom of expression due to the chilling effect that would occur from knowing that if they post a political opinion too far outside of the Overton window they may be investigated, arrested, or prosecuted for sharing such beliefs. Is this the direction we’d like to see the Web go?
Exchanges user agency for greater compliance and convenience
We believe that these systems will further perpetuate the imbalances of power between users and the platforms they interact with on the Web today. In most cases, these systems will only grant further power, in that they will allow the system operators to know when basic attributes will be shared; in exchange, the trust of the user to self attest their information will be deferred to third parties selected by the verifiers. As such, users will further become just subjects of the online systems they use rather than a person with agency who chooses to provide information to use a technology or service. This loss therefore only stands to further reduce the control a user has over their data, because we as individuals would be considered second-rate authorities of our own data (the authority of the "issuers" becoming the more-trusted source). A great example of this would be a credential being issued by a government that doesn’t recognize a gender change on a passport. This leads to the user being forced to misgender themselves each time a gender attribute is requested from a credential such as a digital passport. In total, this issue is one where the user loses agency and leads to a misprioritization of constituents by allowing issuers and verifiers to take precedence over the desires of users.
In many cases, these systems will not be systems we've chosen to use. Instead, the majority of the cases where this API will be used are ones prescribed by institutions. In other words, cases where "Issuers" and "Verifiers" have made decisions out of convenience, aiming to improve their business processes or bespoke regulations established to scale compliance and ivory tower regulations. These systems are chosen by those who already have power, and that subjugate users further into the trust structures established by institutions rather than treating individuals as agents of their own choice. This leaves users with only the limited “option” to share attested data or not use a Web service at all (at least in the regulated cases). As such, by extension the Web will inherit these properties through the acceptance of this API. Therefore, if we believe that user agency is a core principle of the Web, the reasonable thing for us to do is to push back on the acceptance of this API’s usage altogether.
Conclusion
It’s our position that endorsing this work will lead to further problems that are not adequately addressed, and that it’s not worth taking this work through the standardization process. We believe this work should continue to incubate in a community group where further iteration can occur. On top of that, we are concerned that some of these issues are not ones that can be technically addressed in the first place. Until it’s clear which digital credentials will be commonly issued, what they’ll be used for, and what harms may come with them, we cannot be certain that this work is worth adding to the Web platform. Therefore, we believe that if there is a desire to progress this work forward it should first be handled at the application layer so we can learn the direction this might go and further learn if these issues are solvable by committing to adding support for digital credentials to the Web platform.
-
@ 6bf2d239:1b2068b7
2025-02-25 12:34:09
今週のおやつ。
ことりっぷ 小さなチョコパイ
金沢 甘味カフェ茶ゆの東大和チョコどらアイス https://image.nostr.build/1a6b2484ad479786e05c96adaa37e7e2bd69775aedbbb8778e99c0aadccad1bb.jpg
-
@ 648c0f53:96de86a6
2025-02-25 12:33:48
this app should win the 2025 best app in all stores lmaooo
-
@ 8c631ec0:8fae6826
2025-02-25 12:33:33
🎵サンサンサンサン アサヒサ～ン🌞
みんなよろこぶ チカラコブ
おひさまよろこぶ チカラコブ
チ・カ・ラ・コ・ブ！💪
-
@ f8978eb7:7f8e8a50
2025-02-25 12:33:20
今日糖分とりすぎだな
-
@ 96203d66:643a819c
2025-02-25 12:33:14
nostr over ggwave、ちょっと楽しそう
-
@ f4d89779:2b522db9
2025-02-25 12:32:52
GM, what a time to be alive 😁
-
@ 2450d704:08ec15f0
2025-02-25 12:32:48
3等 (@ GiGO総本店 in 豊島区, 東京都) swarmapp.com/c/l8j39durwxC
-
@ 21ac2956:09d1e2df
2025-02-25 12:32:26
今日もまた飲みすぎた食べすぎた
-
@ 5f010feb:3ae9756b
2025-02-25 12:32:20
ちなみにカミーユがファにお世話されてるところまでは昨日見た
-
@ 2efaa715:3d987331
2025-02-25 12:32:06
I wonder what it would look like with stablecoins included
-
@ 06b7819d:d1d8327c
2025-02-25 12:31:43
Detailed report
https://www.w3.org/2024/10/team-report-fedid-wg-fo.html
-
@ 5aaccfdd:747c5c90
2025-02-25 12:31:42
CPAPつけて寝るか
-
@ 2efaa715:3d987331
2025-02-25 12:31:36
I have. It was for a peer to peer software system where the NFTs functioned as unique identities for the users, with the ethereum chain working as the global name resolver for peer discovery.
I don't regret it, it was a cool idea.
I prefer Nostr 's permissionless key/identity system and think the tradeoffs are better, but the discovery "problem" remains.
-
@ 4c800257:b47e3b2f
2025-02-25 12:31:26
it's more likely a bunch of shorts getting triggered after the bybit hack as traders panic to "cash out their gainz"
i got wiped out from leveraged longs back in 2015 after the cryptokitties hack
fucking ethereum and these stupid gamblers
anyhow that's part of why i just buy and hold, and now, just hold and hold (i get paid in sats)
-
@ 5f010feb:3ae9756b
2025-02-25 12:31:04
おれは弱いから商談動画を一人で見返せない。
-
@ 07804b78:c375c543
2025-02-25 12:30:57
Nostr over ggwave
-
@ e4b67f9f:33ea4d91
2025-02-25 12:30:54
🤣🤏 Yakkkibah 🤮 GM 🧡💊🫂
-
@ f8978eb7:7f8e8a50
2025-02-25 12:30:32
プリン食べようかな
-
@ a3c13ef4:d7ba24d6
2025-02-25 12:30:06
■ 流速計測
2025/02/25 21:20～21:30
[JP リレー]
きりの川: 33 posts
やぶみ川: 29 posts
ほりべあ川: 欠測
かすてら川: 6 posts
こじら川: 29 posts
しの川: 6 posts
[GLOBAL リレー]
きりの川(G): 37 posts
のこたろ川(G): 欠測
■ 野洲田川定点観測所
https://nostr-hotter-site.vercel.app
-
@ 88888888:139008d3
2025-02-25 12:30:04
很多新人不知道ETH以前回滚过一次吧？
-
@ 87e02cd9:86477412
2025-02-25 12:30:02
--------------21:30--------------
-
@ e4f9ab96:9512673a
2025-02-25 12:30:00
✄------------ 21:30 ------------✄
-
@ 96203d66:643a819c
2025-02-25 12:29:57
AIがDTMFみたいなので会話してるの、良い(ggwave)
-
@ f275ab37:bad84bfe
2025-02-25 12:29:51
Did it two years ago
-
@ 1bc70a01:24f6a411
2025-02-25 12:29:40
https://touchgrass.now/
-
@ ff2e4123:cacb9ecd
2025-02-25 12:29:28
GM TICK TOCK NEXT BLOCK 🫂🧡🤙
-
@ f275ab37:bad84bfe
2025-02-25 12:29:12
https://video.twimg.com/ext_tw_video/1894082863647395841/pu/vid/avc1/720x720/jWf5SwwT6dAJGkTk.mp4
-
@ edf0da8b:b2652fa3
2025-02-25 12:29:09
Oh no, they didn't allow embedding the video. Anyway, it's a good one when it works.
-
@ 9358c676:9f2912fc
2025-02-25 12:29:00
Uhhh eso sería increíble!!! Todas buenas ideas 😅🌟
-
@ 7232d725:a22ff54e
2025-02-25 12:28:34
擁護派は水ダウじゃなかったらボロクソ叩いてるでしょ。
そのままオンエアするのはダメだわ。
TBS『水曜日のダウンタウン』ひょうろく企画で謝罪 VTR内で実在の学校名「ご不快な思いをさせてしまった」【全文】
https://www.oricon.co.jp/news/2370906/full/
-
@ b3e43e8c:e3068b5f
2025-02-25 12:28:29
次は3/21に世界のビットコイン事情① 南アフリカ編
-
@ ab6a73e5:1c9b1fb5
2025-02-25 12:28:28
That tiny desk concert is a gem
-
@ 9358c676:9f2912fc
2025-02-25 12:28:26
GM friend Puma 😉☕
-
@ 32092ec1:8e9fd13a
2025-02-25 12:28:17
GM nostr ☕ PV 💜
Done with all caps, it really felt like yelling, idk, not my style I guess.
I'll be back on an airplane today, heading to UMD for a Nuclear Codes and Standards meeting.
If you want a nuclear word salad I am the chair of the Joint Committee on Nuclear Risk Management Subcommittee on Nuclear Risk Standards and Guidance 🫡
-
@ 88888888:139008d3
2025-02-25 12:28:10
😂
-
@ b707d6be:eb5a0c20
2025-02-25 12:28:01
イギリスとの通信がカスみたいに遅くなって泣いています
-
@ 139fcc6b:8060e65d
2025-02-25 12:27:57
You can now use the code ARTIFFREEDOM to get 10% off your tickets for @TheBitcoinConf in Las Vegas
✊🏼🎨🎉
Get them here: https://tickets.b.tc/event/bitcoin-2025?promoCodeTask=apply&promoCodeInput=ARTOFFREEDOM
-
@ 8c133b31:05371505
2025-02-25 12:27:28
GM
https://image.nostr.build/b1ee566b8a3cf0f94b6f363f8497c34a304e45d522b2459aa2e135f9c1002278.jpg
-
@ cbcb0e0b:31d2e52a
2025-02-25 12:27:26
依神女苑がやたら有名になったやつ
-
@ b3e43e8c:e3068b5f
2025-02-25 12:27:07
LLM浮気性なうささん
-
@ 0c45d7d4:5e443e4d
2025-02-25 12:27:01
Bitcoin heading to $89,000 may indicate that a brutal global recession is coming.
Be wary.
-
@ e62f27d2:e6b21cb7
2025-02-25 12:26:56
いまならみれるらしいが
うーん…
-
@ e62f27d2:e6b21cb7
2025-02-25 12:26:43
ZZ見てないや
サブスクになくて見れなかった
-
@ 23395bce:fd305cb3
2025-02-25 12:26:29
Claude3.7賢すぎてもう添い遂げたい。
-
@ 77911886:4b218091
2025-02-25 12:26:23
現在のブロック高さ:885246
<推奨手数料> 単位sats/vB
最速:5
1時間以内:5
[参考] 直近6ブロックの最小手数料
4,3,3,4,6,8
[参考] 次ブロック候補の最小手数料
5
-
@ b707d6be:eb5a0c20
2025-02-25 12:26:13
シリーズ化がすごい
https://store.steampowered.com/app/3490680/_/
-
@ cd510c42:7e5622d8
2025-02-25 12:26:04
「なにしよって、そりゃあマグロに決まってるだろ！オレサマを見て楽しむもよし、みんなでお食事するもよし、選びな！残さず食べろよ！」
-
@ 8571a2e7:63c114e9
2025-02-25 12:26:00
なにしよ
-
@ d0708145:76171fb6
2025-02-25 12:25:52
Not after 15 knots they don't😬😜.
-
@ 91aeab23:baa48660
2025-02-25 12:25:36
GM
-
@ 06b7819d:d1d8327c
2025-02-25 12:25:17
This is the formal objection that the W3C council overturned. Worth reading.
https://lists.w3.org/Archives/Public/public-review-comments/2024Sep/0017.html
-
@ 64286647:5f6c7296
2025-02-25 12:25:03
GM WHAT DID I MISS ☕️🙂↔️
-
@ 2450d704:08ec15f0
2025-02-25 12:25:01
3等 (@ GiGO 池袋1号館 in 豊島区, 東京都) swarmapp.com/c/0u99bxSOrbr
-
@ 3ce2b51d:36fc72c7
2025-02-25 12:25:00
✄------------ 21:25 ------------✄
-
@ b3e43e8c:e3068b5f
2025-02-25 12:24:53
こないだ50歳になったからなん？ https://i.nostr.build/PpSJqDw8Yv43GdN1.jpg
-
@ 24cf5e0e:9904d481
2025-02-25 12:24:16
Took your advice to heart https://image.nostr.build/e3496ebf0ba89f5d76ce1e6f439e4f8a11d6f18d978c4e7fabf2070179bf5809.jpg
-
@ 4ce6abbd:94a514dd
2025-02-25 12:23:25
Yea all the sats!
-
@ 6bf2d239:1b2068b7
2025-02-25 12:23:18
本日のライブラリ追加
INABA / SALAS 新譜
milet 新譜
サカナクション 新譜
https://image.nostr.build/48b187f63102369a35f315541ef63fbd2944601d5c31ccaff41262d6cc410a4b.png
-
@ da368de6:fe8192b5
2025-02-25 12:23:01
🍚(・～・)mogmog
-
@ a6f1f450:29388f0b
2025-02-25 12:22:55
ハマーン様がもう一人の主人公でヒロイン枠みたいなところあるにはあるけど，でもまぁハマーン様も地球に全面核攻撃を仕掛ける気概を持ってたり実際ダブリンにコロニー落としてしまってたりで明白に「悪」ではあるからな…
-
@ 516add19:e697c014
2025-02-25 12:22:20
GM✨🫡
-
@ 4ce6abbd:94a514dd
2025-02-25 12:21:48
Nice you guys are back on #nostr 🫂
https://media0.giphy.com/media/fDzM81OYrNjJC/giphy.gif?cid=9b38fe91ctpqd8o9cfl7rkz7zwrn4lqtxrmmjalu4us2e3vv&ep=v1_gifs_search&rid=giphy.gif&ct=g nostr:note1xdwd80e35vq7843k233c82t024h2spr63fdzgty9gy4xc0yjsjxqhazqcs
-
@ 527337d5:93e9525e
2025-02-25 12:21:45
人手の問題は無理でしょwww
nostr:nevent1qqsgal5vtty24djp87ckz0pfq9h7yk57xsk2wxuuv8nn7wyn2du9gjsmsx36g
-
@ e62f27d2:e6b21cb7
2025-02-25 12:21:40
うにょ
-
@ b707d6be:eb5a0c20
2025-02-25 12:21:11
と思ったけどIPA CyberLab 400Gだと500Mbps出る
-
@ b707d6be:eb5a0c20
2025-02-25 12:20:53
転送速度がカスなんだけど何が起きてるの
-
@ d947f966:abf1c11f
2025-02-25 12:20:31
（厚生）年金の支払額が夫婦のどちらかに偏ってる場合に、将来払われる年金を公平な額にするやつです
-
@ f599737d:3aa728bb
2025-02-25 12:20:11
This is just your imagination. They're on vacation.
-
@ f0e59458:4afe015e
2025-02-25 12:20:08
もこうがよく使う冗談ですやんwをヒカキンまで使うようになって感慨深い()
-
@ 891eb34a:604c7e3a
2025-02-25 12:20:06
やぶみリレーのまとめだよ ぷくー
・たこあたまさん、サイレントヴォイスがはじまるっていってる ぷく
・すうきやさん、にょいーんっていってる ぷく
・しばやま41にんさん、りこんライフハックをしょうかいしてる 🔗 ぷく
・ひよこさん、おうえんメッセージをあげてる 🖼️ ぷく
・みんな、いろいろつぶやいてる ぷしゅー
-
@ a3c13ef4:d7ba24d6
2025-02-25 12:20:05
■ 流速計測
2025/02/25 21:10～21:20
[JP リレー]
きりの川: 68 posts
やぶみ川: 56 posts
ほりべあ川: 欠測
かすてら川: 14 posts
こじら川: 56 posts
しの川: 14 posts
[GLOBAL リレー]
きりの川(G): 66 posts
のこたろ川(G): 欠測
■ 野洲田川定点観測所
https://nostr-hotter-site.vercel.app
-
@ b0c8af21:843174a6
2025-02-25 12:20:00
✄------------ 21:20 ------------✄
-
@ b707d6be:eb5a0c20
2025-02-25 12:19:49
うわさん
-
@ e519402e:55e60ae7
2025-02-25 12:19:46
にょいーん。
-
@ f768fae9:91b11cdd
2025-02-25 12:19:45
#バズワードランキング
1位: #うわさ (10)
2位: #深い (7)
3位: #寒く (5)
4位: #壁 (5)
5位: #離婚 (5)
6位: #1話 (4)
7位: #多い (4)
8位: #ZZ (4)
9位: #投稿 (4)
10位: #楽しく (4)
-
@ 91aeab23:baa48660
2025-02-25 12:19:30
GM
-
@ 06b7819d:d1d8327c
2025-02-25 12:19:28
W3C Council Report on the Formal Objection Against Federated Identity Working Group Charter — Adding Digital Credentials API
https://www.w3.org/2025/02/council-report-fedid-dig-cred.html
-
@ 21ac2956:09d1e2df
2025-02-25 12:19:13
検索よけすな
-
@ 91aeab23:baa48660
2025-02-25 12:18:58
☀️
-
@ 91aeab23:baa48660
2025-02-25 12:18:44
To the Nostr DM black hole 🕳️
-
@ 516add19:e697c014
2025-02-25 12:18:38
GM friends.
https://i.gifer.com/embedded/download/4CoT.gif
-
@ 59cb0748:9602464b
2025-02-25 12:36:44
ちょうどみてた