Home | Notifications | New Note | Local | Federated | Search | Logout
Federated Timeline
:hosimiya_mion::star_stroke:@hos1miya@misskey.0sakana.xyz (2026-08-24 01:43:44)
情報技術系の話何も分からないので結構TLについていけなくなる
:hosimiya_mion::star_stroke:@hos1miya@misskey.0sakana.xyz (2026-08-24 01:42:23)
:twitter:の昔からのFF、誰一人として:fediverse:に定着していない
博多市@hakatashi@pawoo.net (2026-08-24 01:41:26)
サービス立ち上げ直後という大事な時期に、電源ケーブルに足を引っ掛けて障害を起こすという1990年代みたいなミスをする
:hosimiya_mion::star_stroke:@hos1miya@misskey.0sakana.xyz boosted:
@hos1miya@misskey.0sakana.xyz (2026-08-23 21:53:24)
✅ 飯テロではありません
---Attachments---
image: https://misskey.0sakana.xyz/files/webpublic-2936cf7a-661f-445f-b6f7-60e3f6782a1a
おだら@s3_odara@mastodon.hakurei.win (2026-08-24 01:36:52)
ActivityPubにいる人は基本ここに来て知り合ってるからあんまり付き合い長い人いないかも
おだら@s3_odara@mastodon.hakurei.win boosted:
@ponkotuy@social.mikutter.hachune.net (2026-08-24 01:32:44)
駐車場精算機「ロック板が下がってるか確認してね」
ぽんこつ「さすがに大丈夫やろw」
スマホ精算「ロック板下がってるか確認してね」
ぽんこつ「それは怖い確認しないと」
ぽんこつ 27L@ponkotuy@social.mikutter.hachune.net (2026-08-24 01:32:44)
駐車場精算機「ロック板が下がってるか確認してね」
ぽんこつ「さすがに大丈夫やろw」
スマホ精算「ロック板下がってるか確認してね」
ぽんこつ「それは怖い確認しないと」
:hosimiya_mion::star_stroke:@hos1miya@misskey.0sakana.xyz (2026-08-24 01:31:24)
ァー
:hosimiya_mion::star_stroke:@hos1miya@misskey.0sakana.xyz (2026-08-24 01:12:41)
今日買った物
---Attachments---
image: https://misskey.0sakana.xyz/files/webpublic-5060435c-3650-444b-862d-af75a88f794a
fedicat@fedicat@pc.cafe boosted:
@silverpill@mitra.social (2026-08-24 00:57:35)
The ap-next developer guide was removed from the https://activitypub.rocks website: https://github.com/swicg/activitypub.rocks/issues/63 (by the father of the Fediverse, no less).
The reason:
It's a fork outside the SocialCG.
This is utter nonsense. The guide refers to the original ActivityPub specification and even to SocialCG reports covering Webfinger and HTTP signatures. The other ap-next project is NomadPub - a collection of FEPs that significantly expand the capabilities of the protocol but don't diverge from the original spec.
However, since dissenting opinions about the present and the future of ActivityPub are now openly censored, a fork may indeed be necessary.
:hosimiya_mion::star_stroke:@hos1miya@misskey.0sakana.xyz (2026-08-24 01:07:28)
帰還
:hosimiya_mion::star_stroke:@hos1miya@misskey.0sakana.xyz boosted:
@uniuni00630@misskey.io (2026-08-20 20:47:33)
#超かぐや姫
ヤッチョ好き😊
---Attachments---
image: https://media.misskeyusercontent.com/io/webpublic-32ca40b9-0fa8-4d29-b4ee-6aeaf2ba256b.png
silverpill@silverpill@mitra.social (2026-08-24 00:57:35)
The ap-next developer guide was removed from the https://activitypub.rocks website: https://github.com/swicg/activitypub.rocks/issues/63 (by the father of the Fediverse, no less).
The reason:
It's a fork outside the SocialCG.
This is utter nonsense. The guide refers to the original ActivityPub specification and even to SocialCG reports covering Webfinger and HTTP signatures. The other ap-next project is NomadPub - a collection of FEPs that significantly expand the capabilities of the protocol but don't diverge from the original spec.
However, since dissenting opinions about the present and the future of ActivityPub are now openly censored, a fork may indeed be necessary.
東京都@Tokyo@unnerv.jp boosted:
@UN_NERV@unnerv.jp (2026-08-24 00:56:15)
【東京都 気象警報・注意報 2026年08月24日 00:56】
小笠原諸島では、高波に注意してください。
#気象警報注意報 #東京都
---Attachments---
image: https://media.unnerv.jp/media_attachments/files/117/145/637/666/639/191/original/1a4b3a63c052a679.png
特務機関NERV@UN_NERV@unnerv.jp (2026-08-24 00:56:15)
【東京都 気象警報・注意報 2026年08月24日 00:56】
小笠原諸島では、高波に注意してください。
#気象警報注意報 #東京都
---Attachments---
image: https://media.unnerv.jp/media_attachments/files/117/145/637/666/639/191/original/1a4b3a63c052a679.png
:hosimiya_mion::star_stroke:@hos1miya@misskey.0sakana.xyz (2026-08-24 00:18:55)
野宿回避
:hosimiya_mion::star_stroke:@hos1miya@misskey.0sakana.xyz (2026-08-24 00:07:56)
Reply - kz & かぐや(cv.夏吉ゆうこ) #NowPlaying #なうぷれ
検索
:hosimiya_mion::star_stroke:@hos1miya@misskey.0sakana.xyz (2026-08-24 00:04:20)
眠い
fedicat@fedicat@pc.cafe boosted:
@blueb@eepy.zone (2026-08-23 12:21:39)
snowdrop drafts soon. i implemented the storing mechanism and a sloppy test ui but it will be real by next release.
Reply to @mookie@weredreaming.com
neverbeaten@neverbeaten@mas.to (2026-08-23 23:49:44)
@mookie
You know it is boring when the commentators talk more about the history of the track than what is happening on the track. Glad to see this one go, but Monaco should have gone first for the same reasons.
fedicat@fedicat@pc.cafe boosted:
@jorijn@social.jorijn.com (2026-07-29 03:32:45)
Today, I’m letting you know that toot.community will close permanently on 28 October 2026.
This decision is final, and the server won’t be handed over to anyone else.
When I started running toot.community, I really enjoyed it. Over time, it became more stressful and less rewarding.
Every day, I deal with spam, bots, technical issues, abuse reports, and user conflicts. Much of the moderation ends up being about personal disagreements rather than actual rule-breaking.
More importantly, I don’t enjoy how people interact on social media anymore. Too often, conversations turn hostile or confrontational. A small amount of conflict and bad actors takes up a disproportionate amount of time and energy.
I find myself feeling more angry or discouraged after spending time as an admin, and that’s not what I want from social media or a volunteer project.
There’s also the financial side. I’m very grateful to everyone who donated, but donations haven’t covered costs for a long time. I’ve had to shoulder most of the expenses, time, and responsibility myself.
The server is now closed to new registrations and will remain online until 28 October 2026, so you’ll have three months to find another Mastodon or Fediverse server and move your account.
You can find Mastodon’s official migration guide here: https://docs.joinmastodon.org/user/moving/
Please note that Mastodon can move your followers, but it can’t transfer your old posts or uploaded media to your new account. If you want to keep a copy, download an archive.
If you’d like to stay in touch, you can follow my personal account here (@jorijn).
Coro@Coro@mstdn.maud.io (2026-08-23 23:32:12)
Framework Laptop には CAMM2 モデルがあるっぽい。
KOBA789@koba789@misskey.io (2026-08-23 23:25:56)
めちゃくちゃラベンダーの香りがする
KOBA789@koba789@misskey.io (2026-08-23 23:24:27)
酔っ払って公園でくたばっていたらめちゃくちゃ蚊に刺されたのでブラジルで買った虫刺され薬を塗った
:hosimiya_mion::star_stroke:@hos1miya@misskey.0sakana.xyz (2026-08-23 23:21:22)
北千住.7zに備える
KOBA789@koba789@misskey.io (2026-08-23 22:30:38)
DDI って Daini Denden Inc. だったのかよ
:majidekapurin_cry_up:マジでデカいプリン@majidedekaipurin@misskey.io (2026-08-23 22:17:47)
🩵💙:bunhd::ohana_nemophila:🍮🩵💙
---Attachments---
image: https://media.misskeyusercontent.com/io/b925ac54-5e09-460c-b5f2-e6ec6b98f2df.png
Reply to @mookie@weredreaming.com
Starcade@Starcade@sfba.social (2026-08-23 22:17:23)
@mookie
Amazon has been testing AI for a few months now but it's not currently on for me.
Their search function has been horrible for ages. To me, it's their achilles heel, but I digress. 🤔
Were you accessing via your phone?
It appears AI is built into their mobile app.
A potential solution would be to access Amazon via a third party browser and not use the dedicated app.
There are third party blockers such as Adios Alexa for Shopping on Chrome, Edge, and Firefox
https://www.modemguides.com/blogs/ai-infrastructure/how-to-disable-amazon-rufus?srsltid=AfmBOopWD2Ont0HHjmkieUAmGT90fxLRqm_cNnB84M-OOE3nm0vKDvkf
pocche@pocche@misskey.io (2026-08-23 22:14:03)
あぁ
---Attachments---
image: https://media.misskeyusercontent.com/io/4fd34a52-6c20-4338-8069-8036443aaedc.png
おだら@s3_odara@mastodon.hakurei.win boosted:
@opptape@akkoma.xn--t8jzbl7g.jp (2026-08-23 21:53:28)
著作権法ではAIに生成させても人が描いても扱い変わらないので、AI生成かどうかを判断する必要が発生しない
Older Notes