Home | Notifications | New Note | Local | Federated | Search | Logout
Federated Timeline
kosui@kosui@blog.kosui.me (2026-03-19 02:50:19)
なんか食べてから寝たい気持ちもあるが、まあさすがにもう寝るべきか
kosui@kosui@blog.kosui.me (2026-03-19 02:48:16)
明日早朝待機なのにこの時間まで起きてしまった(絶望)
kosui@kosui@blog.kosui.me (2026-03-19 02:47:20)
うおーこの時間マジで腹減りすぎる
諏訪子@suwako@sns.076.moe (2026-03-19 02:33:17)
DLSS5凄いね・・・
---Attachments---
image: https://sns.076.moe/media/f550abdbf753906dcd0c5c10f3ad97d88d60e9d64588aea17eea05b0920b349f.png
🦉@aaa (2026-03-19 02:13:55)
朝起きるようにしなくては
kosui@kosui@blog.kosui.me (2026-03-19 02:11:30)
ウンチ・オブ・ウォールストリート
kosui@kosui@blog.kosui.me (2026-03-19 01:58:01)
ついにioriのCLIを実装したぞ。これでnvimからもGitHub Actionsからもioriに投稿できる。
:hosimiya_mion::star_stroke:@hos1miya@misskey.0sakana.xyz (2026-03-19 01:07:44)
ドンキPC、今後どうするんだろね
:hosimiya_mion::star_stroke:@hos1miya@misskey.0sakana.xyz (2026-03-19 01:04:19)
品川駅の工事、バカ不便そう
:hosimiya_mion::star_stroke:@hos1miya@misskey.0sakana.xyz (2026-03-19 00:57:36)
ねこ
:hosimiya_mion::star_stroke:@hos1miya@misskey.0sakana.xyz (2026-03-19 00:57:29)
Cat6eで十分
:hosimiya_mion::star_stroke:@hos1miya@misskey.0sakana.xyz (2026-03-19 00:50:15)
高山本線って今不通なの
:hosimiya_mion::star_stroke:@hos1miya@misskey.0sakana.xyz boosted:
@0u0_tuna@misskey.io (2025-10-15 18:52:59)
トリッカルのコミー
---Attachments---
image: https://media.misskeyusercontent.com/io/webpublic-9a4eeaba-90b6-40dd-b56e-8545149ca9d4.webp
Reply to @hos1miya@misskey.0sakana.xyz
:hosimiya_mion::star_stroke:@hos1miya@misskey.0sakana.xyz (2026-03-19 00:43:42)
:exploding_woozy:
---Attachments---
image: https://misskey.0sakana.xyz/files/webpublic-49f23127-309d-4cee-990d-9c4472cae7cc
:hosimiya_mion::star_stroke:@hos1miya@misskey.0sakana.xyz (2026-03-19 00:43:06)
眠気 どこ 検索
:hosimiya_mion::star_stroke:@hos1miya@misskey.0sakana.xyz (2026-03-19 00:37:32)
頭真っピンクです
:hosimiya_mion::star_stroke:@hos1miya@misskey.0sakana.xyz (2026-03-19 00:36:27)
おにゃのこのちくびすりすりしたい
warabi餅@w4rabimochi@misskey.io boosted:
@ssk_chi@misskey.io (2026-03-18 19:31:04)
:sakura:春マリー
---Attachments---
image: https://media.misskeyusercontent.com/io/ddb8513d-0bf5-443b-9380-16ecb0fa00f7.png
:hosimiya_mion::star_stroke:@hos1miya@misskey.0sakana.xyz (2026-03-19 00:26:39)
:unicode_1d54f_bg_black:(他称Twitter)
諏訪子@suwako@sns.076.moe (2026-03-19 00:24:52)
よぉ、大手ゲームスタジオの皆さん
ゲーマーに男キャラか女キャラかを選ばせる選択肢を用意してるのに、「男性」「女性」って呼びたくないなら、一体性別選択画面を置く意味って何なんなの？
だったらどっちか一方に決めて、其れだけにしとけよ
其れで、DEIの様な差別的な行為を避けられるだろ
:hosimiya_mion::star_stroke:@hos1miya@misskey.0sakana.xyz (2026-03-19 00:23:49)
ペイデイ？(難聴)
:hosimiya_mion::star_stroke:@hos1miya@misskey.0sakana.xyz (2026-03-19 00:21:49)
2回は手数料0じゃん
kosui@kosui@blog.kosui.me (2026-03-19 00:11:01)
久々にXでPostしたら変な伝わり方をして凄く消耗した
kosui@kosui@blog.kosui.me (2026-03-19 00:07:46)
AWS Lightsailの費用が意外とかかっているので、適当なタイミングでVoidに載せ替えるか
:hosimiya_mion::star_stroke:@hos1miya@misskey.0sakana.xyz (2026-03-19 00:06:34)
誰金貸し付けておいて？
:hosimiya_mion::star_stroke:@hos1miya@misskey.0sakana.xyz (2026-03-19 00:05:55)
風ドリア？
SASANO Takayoshi@uaa@social.mikutter.hachune.net (2026-03-19 00:04:29)
Xの調子が怪しい？
warabi餅@w4rabimochi@misskey.io (2026-03-19 00:04:25)
:yuri:を描くぞ
Reply to @phnt@fluffytail.org
Phantasm@phnt@fluffytail.org (2026-03-18 23:52:27)
@silverpill @grishka
>`status` should not be inlined, and instead a link to the Object for optimization reasons (Instance does not need to query DB for the latest status when Actor is being requested. Instead if remote instance is interested in the status, or it changed, it can be fetched with another request
On second thought, it might be stored in the users tables as another column I guess, but doing history that way would be annoying. At least in the case of Pleroma where Activities, Objects and Actors(users) are all separate tables.
Reply to @silverpill@mitra.social
Phantasm@phnt@fluffytail.org (2026-03-18 23:49:22)
@silverpill
I have some comments I'll think about and maybe make into an issue later
`status` should not be inlined, and instead a link to the Object for optimization reasons (Instance does not need to query DB for the latest status when Actor is being requested. Instead if remote instance is interested in the status, or it changed, it can be fetched with another request `statusHistory` probably should be ordered so syncing it can be done without refetching every page of it I don't like the usage of Remove on ActorStatus which is not a Collection, Undo might be a better replacement for clearing the status
Anyways, it might be better to cc @grishka before I go creating an issue without discussion.
Also I was more thinking of what Misskey has with the user presence status which I don't know if it federated. Which shows whether a user is online/away/busy/offline.
Older Notes