I am outputting ActivityPub/ActivityStreams content for the listing of what is in a directory.
Think of it as the AP/AS version of output from the `ls` command
AP/AS has a whole bunch of stuff that can be used to represents files. Even sub-types of files […]
https://fedihollo.org/@admin
https://bot.moe.pub/
[关于联邦软件——hollo的消极吐槽（梦话）——很一般、很普通]
hollo......如果用过botkit，那差不多就相当于用过hollo了 (
虽然也是和 #gotosocial 一样的“单”用户实例；
但是gotosocial，只是推荐单用户；
而hollo，应该是一个管理员，可以创建多个账户，比如这个@admin@fedihollo.org ，还可以创建 @xxx@fedihollo.org ；
创建多账户上这一点要比botkit更好？botkit是一域名一机器人的，就像 @mybot 和 @ […]
[Original post on mstdn.feddit.social]
@COSCUP 2026（台北、8月8–9日）にて、**Fediverse & Social Web**トラックが採択されました！#フェディバース、#ActivityPub、オープンなソーシャルウェブをテーマに、丸一日・計6時間のトラックを予定しています。
発表者向けのCFPはまだ始まっていませんが、公開され次第お知らせします。お楽しみに！
#Fediverse #SocialWeb #COSCUP #ActivityPub #fedidev
@COSCUP 2026(臺北(타이베이), 8月(월) 8–9日(일))에서 저희 **Fediverse & Social Web** 트랙이 承認(승인)되었습니다! #聯合宇宙, #ActivityPub, 오픈 소셜 웹을 主題(주제)로 하루 終日(종일), 總(총) 6時間(시간)을 進行(진행)할 豫定(예정)입니다.
發表者(발표자) 募集(모집) CFP는 아직 열리지 않았지만, 始作(시작)되는 대로 바로 公知(공지)하겠습니다. 期待(기대)해 주세요!
#페디버스 #연합우주 #SocialWeb #COSCUP #fedidev
Our _Fediverse & Social Web_ track has been accepted for @COSCUP 2026 (Taipei, Aug 8–9)! We'll have a full day—six hours—to fill with talks on the #fediverse, #ActivityPub, and the open social web.
The CFP for speakers isn't open yet, but we'll announce it here when it is. Stay tuned! […]
So, an interesting issue came up in the #Fedify repo that I've been thinking about: #629.
You know how every #fediverse server uses `schema:PropertyValue` in actor `attachment` for profile metadata fields (like “Website”, “GitHub”, etc.)? Turns out, strict #AS2 validators like browser.pub […]
5/
Continuing to look for an alternative to "attachment" (for properly supporting an Actor specifying a list of Service actors associated with it) —
Maybe a call specific custom top-level attribute would be useful.
Maybe something like:
"call": [
{
"rel":"callpub",
"href":"https://videocalls […]
6/
Continuing to look for an alternative to "attachment" (for properly supporting an Actor specifying a list of Service actors associated with it) —
Maybe a custom top-level attribute would be useful.
Maybe something like:
"service": [
{
"rel":"callpub",
"href":"https://videocalls […]
5/
Continuing to look for an alternative to "attachment" (for properly supporting an Actor specifying a list of Service actors associated with it) —
I think "endpoints" would also be a poor choice, too. Again, the semantics are wrong, or at least lacking.
So —
#ActivityPub #ActivityStreams […]
4/
Looking for an alternative to "attachment" (for properly supporting an Actor specifying a list of Service actors associated with it) —
I think using "alsoKnownAs" and "sameAs" would be a poor choice. And, the semantics are wrong.
For example: a Service actor might represent my mobile phone […]
3/
But, what about the non- fall-back situation where software could properly support this (when an Actor specifies a list of Service actors associated with it)‽
I think some might say, put the associated Service actors in "attachment". And, semantically I think that would work with […]
2/
Because most people wouldn't be able to add custom attributes or custom values to most Fediverse software (including Mastodon) —
Most supporting software would probably want to support a "PropertyValue" link in "attachment" field as a fall back
For example:
"attachment": [
{
"type" […]
1/
AFAIK, there isn't a way for an ActivityPub Actor (such as a Person actor) to specify a list of Service actors associated with it.
...
For example, imagine that there is a Service actor that represents a way to make a video call to me.
And, for example, I have my Mastodon Person actor […]
Just had to add a workaround to #Fedify for `http://joinmastodon.org/ns` a JSON-LD context URL that has never actually served a JSON-LD document. Mastodon has always inlined the term definitions, but some implementations put it as a bare URL in their `@context`, so Fedify's JSON-LD processor […]
I used to not like JSON-LD. And then I got exposed to CBOR. And, since then, I ended up liking JSON-LD more than I did before.
https://j12t.social/@j12t/114581086678041245
...
I was looking for performant ways of storing JSON-LD data, so that it can be looked up, queried, etc.
CBOR might […]
For events with external registration, It's not possible for RSVP. but I let users to bookmark. and then they can see in Calendar view
For calendar view, We can see integrated view for RSVP events / Hosted Events / Bookmarked Events. Also it's possible for Google Calendar Subscription
moim.live just crossed 30 members. Shipped calendar subscription today — you can now subscribe to your personal schedule directly in Google Calendar and other apps.
Traffic is still an unknown. But I'm not ready to go door-to-door yet anyway. There's one payment […]
[Original post on hackers.pub]
Ordinary signin page, and bottom of fediverse OTP login section, we can see mastodon/misskey signin button
After input mastodon instance URL
We can see authorization page for moim.live login, and then succeed to signin
Thanks to @nyanrus https://moim.live now supports Mastodon OAuth, Misskey MiAuth
#moim_live #fedidev
RE: blog.fabiomanganiello.com/article/Federated-replie...
Madblog by @fabio is really coming along!
#fedidev
지금까지 열린 이벤트를 조회하고 우선순위를 조절할 수 있는 어드민 패널
moim.live 메인 화면에 뜨는 캐러셀에 뜨는 이벤트 배너도 우선순위를 조절할 수 있게 했다.
상업용 배너 > 그룹 이벤트 배너 (우선순위 내림차순 정렬) > 개인 이벤트 배너 (이건 그룹 이벤트가 진짜 없을때....)
커뮤니티 혹은 오피셜 그룹에서 게시한 이벤트는 최대한 우선순위를 땡기는 식으로 유연하게 대응하려고 한다.
#moim_live #fedidev
With ActivityPub / ActivityStreams...
To me, it feels like there should have been something that is a common parent of both 'Object' and 'Link'.
That just had the "name", "nameMap", and "preview" fields (along with "id" and "type, of course) — since that is what 'Object' and 'Link' share in […]
FEP website now displays the number of implementations for each implementable proposal:
https://fediverse.codeberg.page/fep/final/
These numbers are based on the information that authors provide in the "Implementations" section of a proposal.
By default, proposals are `informational`, so […]
RE: mastodon.social/@fediversereport/1161780...
Laurens Hof is at it again highlighting the problems of our lack of an adequate ActivityPub API and the hurdles that are to come in it getting adoption.
#fedidev
Check-in screen on Mobile
Admin Panel for managing group/place/moderation action
Dashboard for event organizers
#moim_live #fedidev
I'm building an open source ActivityPub service called "Moim" — 모임 in Korean, meaning gathering or meetup. It started as a federated RSVP service, but I realized I wanted to connect people even beyond events. Events are where people come […]
[Original post on hackers.pub]
#FediDev is there a generic Android intent for sharing to the Fediverse?
RE: https://mastodon.nzoss.nz/@strypey/116083422846229483
Any thoughts on this idea @silverpill, @julian, or others involved in #FediDev?
以前から、東アジアにもFediConのようなイベントがあればいいなと言い続けてきました。独自のカンファレンスはまだ難しそうですが、小さな一歩として考えていることがあります。
@COSCUP 2026（台北、8月8日〜9日）がコミュニティトラックの提案を受け付けています。FOSDEMのSocial Web devroomのような感じで、**Social Webトラック** を開けないかなと思っているところです。
まだ構想段階ですが、ActivityPubやフェディバース、ソーシャルウェブ全般に取り組んでいて、発表や共同オーガナイズに興味があるという方がいれば、ぜひ話しかけてください。 […]
東(동)아시아에도 FediCon 같은 行事(행사)가 있으면 좋겠다는 말을 여러 番(번) 해왔는데요. 獨立的(독립적)인 컨퍼런스는 아직 어렵더라도, 작은 첫걸음으로 생각해보고 있는 게 있습니다.
@COSCUP 2026(臺北(타이베이), 8月(월) 8日(일)–9日(일))이 커뮤니티 트랙 提案(제안)을 받고 있어요. FOSDEM의 Social Web devroom 같은 느낌으로, 거기서 **Social Web 트랙** 을 열 수 있지 않을까 하고 構想(구상) 중입니다.
아직 確定(확정)된 건 아무것도 없지만 […]
I've been saying for a while that we need something like FediCon in East Asia. A dedicated conference is still a stretch, but I've been thinking about a smaller step:
@COSCUP 2026 (Taipei, Aug 8–9) is accepting proposals for community tracks. It might be worth trying to open a _Social Web […]
Today @kopper shared a post on the fediverse titled _how to not regret c2s_, and I found it genuinely interesting to read, even if I'm not sure its proposed architecture actually solves what it sets out to solve.
The author's frustration with naïve #C2S implementations is well-founded. Slapping […]
When I first started working with #ActivityPub, before #Fedify existed, it felt like writing web apps in Perl and CGI in the late '90s. Interesting, even exciting—but never comfortable. That era where your business logic and your protocol plumbing were just… the same thing:
print "HTTP/1.1 […]
