Home | Notifications | New Note | Local | Federated | Search | Logout
Federated Timeline
にせねこ@nixeneko@nixeneko.info (2026-04-11 20:19:40)
クソ暑い日とクソ寒い日を交互にもってくることで平均すると丁度良い気温を演出
にせねこ@nixeneko@nixeneko.info (2026-04-11 20:16:15)
mstdn.jpの画像見えてる
🦉@aaa (2026-04-11 19:44:29)
x.comのリンクは踏むだけで「おすすめアルゴリズム」に作用してしまう…と思い躊躇う
にせねこ@nixeneko@nixeneko.info (2026-04-11 19:40:45)
虚無～
にせねこ@nixeneko@nixeneko.info (2026-04-11 19:37:11)
処分することを考へてものを買ふ（あるいは買はな）ことが多くなってきた
にせねこ@nixeneko@nixeneko.info (2026-04-11 19:36:28)
人は何れ死ぬのであらゆる活動は無意味
にせねこ@nixeneko@nixeneko.info boosted:
@k8i_chan@misskey.io (2026-04-11 19:24:59)
あらゆるものが潜在的ゴミに見えてきていて，本を買うことですら最近は億劫になっている
黒居シミ@k8i_chan@misskey.io (2026-04-11 19:24:59)
あらゆるものが潜在的ゴミに見えてきていて，本を買うことですら最近は億劫になっている
にせねこ@nixeneko@nixeneko.info boosted:
@na4zagin3@pawoo.net (2026-04-11 17:21:19)
そんなに精度は出ないけど、温度と相対湿度が分かってるなら露点も出せる
https://www.daiichi-kagaku.co.jp/situdo/note/arekore02/
にせねこ@nixeneko@nixeneko.info (2026-04-11 19:16:10)
今ワイのメインバンクどこなんやろな
にせねこ@nixeneko@nixeneko.info boosted:
@shibafu528@ertona.net (2026-04-11 18:46:39)
(Approve PR)行け行け行け行け！行け行け行け行け！（デプロイ）（障害発生）オイオイオイオイオイ！オーーイ！FOOOOOO おいリバートしろリバート！リバートしろ(リバートする音)FOOOOOイエイエイエイエイエイFOOパーッパパパーパッパパッパーパッパッパー(謝罪ツイート掲載)
shibafu528@shibafu528@ertona.net (2026-04-11 18:46:39)
(Approve PR)行け行け行け行け！行け行け行け行け！（デプロイ）（障害発生）オイオイオイオイオイ！オーーイ！FOOOOOO おいリバートしろリバート！リバートしろ(リバートする音)FOOOOOイエイエイエイエイエイFOOパーッパパパーパッパパッパーパッパッパー(謝罪ツイート掲載)
ささきち@ssk_chi@misskey.io boosted:
@halllki@misskey.io (2026-04-11 18:11:23)
お風呂上がりレンちゃん
---Attachments---
image: https://media.misskeyusercontent.com/io/webpublic-5c2ed38d-21ad-4bd0-9725-06b4a66b9de6.webp
ささきち@ssk_chi@misskey.io boosted:
@kamesys@misskey.io (2026-04-10 20:58:22)
ケイのロビーボイス😳
#ブルアカ
---Attachments---
image: https://media.misskeyusercontent.com/io/645ff579-8a42-474b-b175-6cc7d0470e48.png?sensitive=true
皆村春樹@halllki@misskey.io (2026-04-11 18:11:23)
お風呂上がりレンちゃん
---Attachments---
image: https://media.misskeyusercontent.com/io/webpublic-5c2ed38d-21ad-4bd0-9725-06b4a66b9de6.webp
ささきち@ssk_chi@misskey.io (2026-04-11 18:05:58)
:skeb:で描かせていただきました！:nuu_jump::twinkle:
全体▶︎ https://x.gd/Cih2M #skeb
---Attachments---
image: https://media.misskeyusercontent.com/io/webpublic-49b4e6a4-fd95-4924-92a2-a716cc82890f.png
ざぎん@na4zagin3@pawoo.net (2026-04-11 17:21:19)
そんなに精度は出ないけど、温度と相対湿度が分かってるなら露点も出せる
https://www.daiichi-kagaku.co.jp/situdo/note/arekore02/
Arnold Schrijver@aschrijver@socialhub.activitypub.rocks (2026-04-11 16:33:16)
Alt-text to the diagram. Click to expand the text.Grassroots growth has seen the fediverse gradually diverge from ActivityPub open standards.With post-facto interoperability the dominant driver, increasing protocol decay hampers innovation and growth.Fediverse as it stands today has limited its application areas, and lost attractiveness to newcomers.A shift back to open standards is possible and required for ActivityPub to remain relevant in the future.Current technology standardization process is unfit for the social dynamics in fediverse grassroots environment.Challenges to standardization are fostering shared ownership, proactive involvement, governance, and recentralization.There are four points where recentralization is a risk: server instances, app platforms, the FEP process, and W3C SocialCG.While funding is available for individual FOSS projects, it is lacking for any work on healthy technology ecosystems.Grassroots open standards allow specification documents to evolve from the bottom up in inclusive commons based ecosystems.Grassroots standardization aligns top-down protocol design with innovation in the creative cauldron of the commons.The social web offers opportunities to natively support standardization processes, and decentralize specifications.Specifications as code that may be bundled with their apps and services, and can be introspected at actor endpoints.Decentralized specification hubs can serve the interoperability needs for different interest groups and solution domains.FEP may become the fediverse evolution process and be part of protocol design that enables robust solution development.Work on the ActivityPub API offers opportunity to reposition the FEP as federated service for Grassroots standardization.With ActivityPub as a grassroots standard, fediverse can be the Future of social networking where we Reimagine social.https://social.coop/@smallcircles/116368803389082089
Thanks to @silverpill and @eprodrom, the pillars of grassroots standard
---Attachments---
https://socialhub.activitypub.rocks/uploads/default/original/2X/e/e7375986a0bf9142613042906a5dac8731f2eabd.png
https://socialhub.activitypub.rocks/uploads/default/original/2X/e/e7375986a0bf9142613042906a5dac8731f2eabd.png
https://socialhub.activitypub.rocks/uploads/default/original/2X/e/e7375986a0bf9142613042906a5dac8731f2eabd.png
Reply to @Profpatsch@mastodon.xyz
silverpill@silverpill@mitra.social (2026-04-11 16:30:16)
@Profpatsch A lot of effort is being put into reducing implementation complexity - it is just not very visible. Libraries, testing tools, documentation (such as the guide that I mentioned during our previous conversation).
However, the complexity is unavoidable in a decentralized network. A standardized representation of a quote (FEP-e232) was proposed long time ago. It was easy to implement, versatile (FEP-e232 could be used to build any kind of link, not just a quote), and it was supported by a significant number of fediverse projects. Then Mastodon developers decided to invent a different kind of quote, with all the unnecessary complexity that you described. But I'd rather deal with this complexity than have some centralized standards org telling me what to do.
Another issue is disinformation -- and that is really weird, and unique to Fediverse. You probably heard that JSON-LD is required, but that is not true. The spec doesn't require it. Only a few Fediverse projects actually use JSON-LD, and as a developer you don't need to worry about it -- adding "@context": "https://www.w3.org/ns/activitystreams" to your JSON makes your software compatible with >99% of Fediverse instances, and even that is necessary because Mastodon has a bug. Unlike the problem of competing standards, this problem can be solved by writing better documentation.
Maartje@maartje@blahaj.social (2026-04-11 15:12:20)
Dear passengers welcome in the European SEV, my name is Maartje and I am your Bus Manager. To your right you see a giant Blahaj.
---Attachments---
image: https://cdn.blahaj.social/media_attachments/files/116/384/591/779/727/433/original/9dca527b760bf3fa.jpeg
諏訪子@suwako@sns.076.moe (2026-04-11 14:21:08)
【Rust】Rust言語のレビュー
https://technicalsuwako.moe/blog/rust-review
【Rust】Review of the Rust Language
https://technicalsuwako.moe/enblog/rust-review
にせねこ@nixeneko@nixeneko.info (2026-04-11 13:41:07)
アルミのスクラップ買取価格が1円/g超えたら1円玉廃止されます？
にせねこ@nixeneko@nixeneko.info boosted:
@iroha_nano145@mastodon.irohanano.nl (2026-04-11 11:19:54)
マイナンバーカードの認証で英語設定だと気を利かせ（おせっかいで）生年月日の年が西暦からの選択になる。認証情報には和暦で登録されている。認証情報と違うので認証に失敗。
にせねこ@nixeneko@nixeneko.info boosted:
@aqz@p1.a9z.dev (2026-04-11 13:30:40)
[ 地デジの放送周波数帯が縮小の可能性（UHF52CHの使用が不可に） | JO634電波受信のブログ ]
https://ameblo.jp/hosomania/entry-12962592033.html
aqz/tamaina :futatsume:@aqz@p1.a9z.dev (2026-04-11 13:30:40)
[ 地デジの放送周波数帯が縮小の可能性（UHF52CHの使用が不可に） | JO634電波受信のブログ ]
https://ameblo.jp/hosomania/entry-12962592033.html
にせねこ@nixeneko@nixeneko.info (2026-04-11 13:29:12)
人の雑な仕事 < AI < 人の丁寧な仕事
にせねこ@nixeneko@nixeneko.info (2026-04-11 13:28:45)
3DCGアニメ、結局フレームごとに見栄えのいい画になる様に動きとモデル形状変更してるんだしAIによる見栄え調整通したら多少省力化できるのだらうか
にせねこ@nixeneko@nixeneko.info (2026-04-11 13:22:28)
羊なら全身の毛を刈って夏仕様に
にせねこ@nixeneko@nixeneko.info (2026-04-11 13:21:55)
自動中割も、原画描いた人の意図を読み取らないといけないので、簡単ではない
にせねこ@nixeneko@nixeneko.info (2026-04-11 13:20:38)
省力化していきませうね
Older Notes