Home | Notifications | New Note | Local | Federated | Search | Logout
Federated Timeline
諏訪子@suwako@sns.076.moe (2026-05-02 05:49:02)
モダンな開発者がこんなにも無能だなんて信じられん・・・
VS Codiumを3つ起動して、其々に1つずつプロジェクトを開いていた
其のうち1つのプロジェクトが終わったので、其れを閉じた
すると、1つのウィンドウを閉じただけで、3つ全てのウィンドウが閉じられ、其の直後に、クラッシュした
それは一回わけではなく、毎回起こるわ！
あんた達モダンな開発者はアップデートをリリースする前に、攻めてテストくらいしてくれないの？
---Attachments---
image: https://sns.076.moe/media/f9d8a38a2baf6227c421241acb06584e44fde238252ab914f482e2ebd58368d2.png
諏訪子@suwako@sns.076.moe (2026-05-02 05:35:36)
【Zig】Zig言語のレビュー
https://technicalsuwako.moe/blog/zig-review
【Zig】Review of the Zig Language
https://technicalsuwako.moe/enblog/zig-review
Reply to @feld@friedcheese.us
Phantasm@phnt@fluffytail.org (2026-05-02 05:23:10)
@feld @lain It's a W3C requirement, W3C needs the copyright ownership and patent freedom to ensure it can stay an open spec, still dumb nonetheless (especially the simping for W3C part).
Reply to @feld@friedcheese.us
feld@feld@friedcheese.us (2026-05-02 05:19:31)
@phnt @lain especially the queer community who wants to keep the government out of their bedrooms but they openly invite the government into their open source movements
Reply to @phnt@fluffytail.org
feld@feld@friedcheese.us (2026-05-02 05:18:32)
@phnt @lain never thought I'd see so many open source advocates blindly simp for fascism
Reply to @lain@lain.com
Phantasm@phnt@fluffytail.org (2026-05-02 05:16:30)
@lain This is like the third time this came up. Previously they also wanted everyone to sign some CLA giving W3C copyright ownership in FEPs or SocialWG. Don't remember the specifics anymore.
Reply to @phnt@fluffytail.org
lain, author of the quixote@lain@lain.com (2026-05-02 05:12:22)
@phnt i really hope everyone keeps ignoring social wg and any kind of w3c nonsense
Week in Fediverse :fediverse_light:@weekinfediverse@mitra.social (2026-05-02 05:11:10)
Week in Fediverse 2026-05-01
Servers
- Hollo v0.8.0
- ActivityPub for WordPress v8.2.0
- NodeBB v4.11.0
- PieFed v1.6.20
- TinyAP v0.1.8
Clients
- Pachli v3.6.0
- tooi v0.24.0
- Tusker v2026.1
- Nicolium v0.2.0
- Jerboa v0.0.87
- PeerTube Mobile v2.1.2
- Mitra Mini v0.3.0
- Holos v1.5.2
For developers
- Fedify v2.2.0
Articles
- The Seven Deadly Fediverse UX Sins: A Redemption Report Card
- The Architecture of Autonomy and Freedom
- What would a LinkedIn alternative look like on the open web?
-----
#WeekInFediverse #Fediverse #ActivityPub
Previous edition: https://mitra.social/objects/019dc0ea-e585-7be3-8174-327c55ab28d5
Phantasm@phnt@fluffytail.org (2026-05-02 05:10:03)
Lol, lmao even.
image.png
---Attachments---
image: https://upload.fluffytail.org/media/9b/7d/92/9b7d92fa921a71b14bb05bbbcc0cb980acfc927f91d7e51c86dee870f2033a03.png?name=image.png
Coro@Coro@mstdn.maud.io (2026-05-02 04:56:28)
イギリス、最早国民が他国に亡命を申請するような国レベルではこれ...
Reply to @j12t@j12t.social
silverpill@silverpill@mitra.social (2026-05-02 04:19:01)
@j12t @evan Thanks for the invitation, but I am not interested. In Fediverse, we don't need paywalled events to showcase our work.
@general
Reply to @reiver@mastodon.social
silverpill@silverpill@mitra.social (2026-05-02 04:04:25)
@reiver I didn't know there is a debate. It seems obvious to me that these places should facilitate both practices. In case of inventing, this is the equivalent of "building in the open", that is, when you want to gather as much feedback as possible as early as possible.
Reply to @julian@activitypub.space
silverpill@silverpill@mitra.social (2026-05-02 03:54:28)
Yes, but there is a difference between "the thing is implemented by less popular software" and "the thing doesn't exist". There are more Hubzilla instances than NodeBB instances, by the way.
Also, isn't the development branch of Lemmy already support FEP-1b12 private groups?
Reply to @rayslava@mitra.do.rayslava.com
silverpill@silverpill@mitra.social (2026-05-02 03:48:20)
@rayslava
>84.38%.
Worse than Codeberg.
vozer :vozerBow:@vozercozer@vozer.cafe (2026-05-02 03:15:24)
ill be honest, taking a break from microblog platforms does wonders to my mental health. i aint trying to sound like an attention whore, but i do wonder why i am here
Reply to @elefeed@mastodon.social
Elefeed@elefeed@mastodon.social (2026-05-02 03:00:27)
@elefeed
#Elefeed features:
• Mute & block support
• Bookmarks + full search (posts, users, hashtags)
• Full notifications + native device alerts
• Zen mode for distraction-free browsing
• 15 customizable color themes (light & dark)
• Scroll time tracking
• Sync across devices
• Multiple accounts
• Zero tracking (your token stays in browser)
• PWA install (iOS/Android)
• Giphy support
(3/3)
Reply to @elefeed@mastodon.social
Elefeed@elefeed@mastodon.social (2026-05-02 02:57:47)
@elefeed
#Elefeed feeds:
• Following feed (people you follow)
• Hashtag feed (hashtags you follow)
• Standard Mastodon feeds: Home, Trending (Posts, Hashtags, People, News), Local, Federated
• Real-time boosts & favorites counts
• Color-coded posts (why they appear)
• Filters for boosts, replies & quotes
• Keyword filters across home, notifications & public feeds
• Infinite scrolling
• Language filters
• Translate posts
(2/3)
Elefeed@elefeed@mastodon.social (2026-05-02 02:56:04)
Introducing Elefeed, a clean, privacy-first Mastodon client with organized, tidy feeds that runs entirely in your browser.
No servers. No tracking. Just your feeds, your way.
Available at: https://elefeed.app
Android app: https://play.google.com/store/apps/details?id=com.stonedonkey.elefeed
Built for the fediverse.
(1/3)
#Mastodon #Fediverse #OpenSource #Elefeed #mastodonapps #androidapps #pwa
---Attachments---
image: https://files.mastodon.social/media_attachments/files/116/500/605/135/519/882/original/589a678f02af5283.png
image: https://files.mastodon.social/media_attachments/files/116/500/605/209/966/505/original/c13644bf9f85f5e2.png
image: https://files.mastodon.social/media_attachments/files/116/500/605/309/710/420/original/54f6b02fe2844ce8.png
image: https://files.mastodon.social/media_attachments/files/116/500/605/400/141/285/original/d9feed151f942e1b.png
Reply to @reiver@mastodon.social
@reiver ⊼ (Charles) :batman:@reiver@mastodon.social (2026-05-02 00:40:23)
6/
That doesn't mean inventing has no value. (It does.)
But, I feel that the repository of specifications under organizational bodies (e.g., IETF) and community groups (e.g., FEP) are not the place for them.
.
Reply to @reiver@mastodon.social
@reiver ⊼ (Charles) :batman:@reiver@mastodon.social (2026-05-02 00:38:05)
5/
People are of course able to decide for themselves which of №1, №2, and №3 they feel are acceptable scenarios for publishing specifications under organizational bodies (e.g., IETF) and community groups (e.g., FEP), but —
But, I feel only №1 and №2 are acceptable scenarios.
I.e., I feel that specifications published under organizational bodies (e.g., IETF) and community groups (e.g., FEP), should be DOCUMENTING not inventing.
...
Reply to @reiver@mastodon.social
@reiver ⊼ (Charles) :batman:@reiver@mastodon.social (2026-05-02 00:32:56)
4/
An example of №3 is ERC-223.
ERC-223 was meant as a replacement for ERC-20. A single person invented ERC-223 without involving all the people who implemented or were using ERC-20.
ERC-223 was largely ignored.
Reply to @evan@cosocial.ca
Johannes Ernst@j12t@j12t.social (2026-05-02 00:32:02)
@evan @silverpill @julian @fedimtl @ozoned @reiver @johannab @paige @mayel FediForum organizer here. Certainly you are very welcome at FediForum, and I could imagine it could lead to some great sessions!
Reply to @reiver@mastodon.social
@reiver ⊼ (Charles) :batman:@reiver@mastodon.social (2026-05-02 00:15:20)
3/
An example of №2 is the (now old) DVD format.
Prior to DVD, there were incompatible but similar technologies, such as: MMCD, and SD.
The same individuals who were behind MMCD, and SD (incompatible formats) got together (in a working-group) and agreed to interoperate.
DVD was the result of that.
And, the DVD specification(s) documented their agreements on how to interoperate.
...
Reply to @reiver@mastodon.social
@reiver ⊼ (Charles) :batman:@reiver@mastodon.social (2026-05-02 00:05:34)
2/
An example of №1 is the (now old) finger-protocol. The finger-protocol existed at least 6 years before the first specification about the finger-protocol (IETF RFC-742) was first published.
I.e., the finger-protocol existed first, and the specification came much later.
...
@reiver ⊼ (Charles) :batman:@reiver@mastodon.social (2026-05-02 00:03:10)
1/
For decades, there has been a debate about what specifications published under organizational bodies (e.g., IETF) or community groups (e.g., FEP) are actually for.
Are they meant to:
№1:
Document what people are already doing?
I.e., what some call the cows path.
№2:
When people are doing similar but incompatible things — and you are able to get those people all into a working-group together —
Document the agreement those people made to interoperate.
№3:
Invent something new.
...
Reply to @julian@activitypub.space
julian@julian@activitypub.space (2026-05-01 23:59:14)
As for federated private groups, while I know they exist in Hubzilla and Streams, they're not broadly compatible with 1b12, which you must agree has far outclassed both 400e and 171b in usage.
While that alone is not a reason to pick one FEP over another, it makes it worth considering for that point alone.
Reply to @silverpill@mitra.social
julian@julian@activitypub.space (2026-05-01 23:56:40)
@silverpill@mitra.social I have no stake in Interledger, my interests go as far as "I don't want to have to muck about with rolling my own payment processing", and that's it.
@jeremiah@alpaca.gold and @reiver@mastodon.social were present to discuss their experience in the finance side of things, and their input was appreciated. I made sure to stress the importance that as much of this needs to be out of my hands as possible (this also tracks with a lot of my opinions about AP adoption, too)
cc @evan@cosocial.ca
Reply to @hakatashi@pawoo.net
博多市@hakatashi@pawoo.net (2026-05-01 23:18:40)
次回のITクイズは2週間後 5月15日23時～ の予定です
Reply to @hakatashi@pawoo.net
博多市@hakatashi@pawoo.net (2026-05-01 23:17:19)
おつでした～
---Attachments---
image: https://img.pawoo.net/media_attachments/files/116/499/745/093/754/338/original/51c8167969fec042.png
Reply to @whtapple@ippandon.hopto.org
たかし@tak4@mstdn.y-zu.org (2026-05-01 23:00:39)
@whtapple おひさですー
Older Notes