@Todd Sundsted
Better dead than bored.
Relays (1)
- wss://relay.ditto.pub – read & write
Recent Notes
Someone should make a JJ wrapper that adds back all the git complexity, like a "checkout" command to revert changes, swap branches, or create new branches. Separate staging area. Lock the CLI until al...
@willhbr i keep trying, but every time i pick up jj my brain breaks. i think i have so many bad git practices that no amount of jj can make sense of them.
how widely adopted/supported/implemented is FEP-8a8e? is that a safe direction to converge for federated events?
I’m working on handling OAuth token expiry as part of #ktistec Mastodon API support. Is my understanding that Mastodon issues OAuth tokens with no expiration correct?!?
1
does anyone use GNU Cash? any free (software) alternatives anyone recommends?
1
OK, this is going even MORE sideways so I need to make a few things clear:
1. I took a complex point and made it poorly
2. My goal was to ask for more inclusiveness
3. I am sickened by what happend to...
@scottjenson you are absolutely not the problem here.
nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpqv7h4w0jectyrjd6ydql0232e83mz003grlqt0ylftum58c5pvn7sf277cu You mean, the entry point for a developer? I started with consuming
@silverpill thanks! yes, as a developer. i'd love to see this in action.
1
Announcing Mitra Mini v0.1.0
Mitra Mini is an ActivityPub client that implements nomadic identity. It has become stable enough that I decided to cut the first release.
The basic features have been i...
@silverpill what's the entry point for trying this out? consuming portable objects?
1
nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpq22glfka8k4m5p8g5radee5hmhmh620slp5jyt7fhwvcjs6nd7azq5r872v nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpqv7h4w0jectyrjd6ydql0232e83mz003...
@liaizon based on your posts, you seem to be caring and thoughtful, but a boatload of the fediverse imo is not right now. just look at this thread. i desperately want mozilla to focus on building a better browser. but the thread devolved into a hate-fest, and that is 1) not going to bring mozilla around, 2) not going to bring the undecided over to the cause, 3) going to run off the newcomers who stumble into that, 4) turns my space here into a much more negative and unhealthy place. i predict that a list focused on tracking vibe-coded fediverse servers will quickly turn into targeting tool for the people i'm talking about here. we don't need that.
cc @mkljczk
cc @mkljczk
1
Slop coded fediverse servers are multiplying I guess we need to start tracking this somewhere!? What happens when there are more AI generated server frameworks then human written ones? The do-ocracy o...
@liaizon I think these are good concerns but I am concerned about the idea of “tracking”. right now my perception of the fediverse is that it has become by far the most overtly hostile social network I’ve been on with wrath regularly directed at “those who don’t conform” even if they diverge in trivial ways. and I am not the only one with a stake in this saying this! more of that made easier to direct is not going to benefit the fediverse in the long term.
1
@kris
https://github.com/toddsundsted/ktistec
it's an activity pub server designed for individuals (multiple users are supported but there's nothing like open registration).
https://github.com/toddsundsted/ktistec
it's an activity pub server designed for individuals (multiple users are supported but there's nothing like open registration).
nodeinfo fixed in 3b56d2a6
FEDERATION.md added in cb3ef061
Before creating and publishing FEDERATION.md for #ktistec I wanted to understand what existing practice looked like across the Fediverse.
FEP-67ff describes the requirements of the FEDERATION.md file in loose terms and provides a non-normative template. I scraped the URLs of FEDERATION.md files from FEP-67ff itself and confirmed I could fetch them. The FEP listed 30 accessible projects (31 total, but one project—FIRM—does not appear to exist).
If a file had a section with the heading "Supported FEPs" per the non-normative template, I only looked there for supported FEPs. Otherwise I scanned the entire document.
Implemented FEPs, ranked by the number of implementations that attest support, are:FEP Name #
---- --------------------------------------------------------- --
67ff FEDERATION.md 18
f1d5 NodeInfo in Fediverse Software 16
8b32 Object Integrity Proofs 7
044f Consent-respecting quote posts 7
2677 Identifying the Application Actor 7
e232 Object Links 6
1b12 Group federation 6
3b86 Activity Intents 6
521a Representing actor's public keys 5
2c59 Discovery of a Webfinger address from an ActivityPub actor 5
7888 Demystifying the context property 5
5feb Search indexing consent for actors 5
4adb Dereferencing identifiers with webfinger 4
d556 Server-Level Actor Discovery Using WebFinger 4
fb2a Actor metadata 4
ef61 Portable Objects 4
8fcf Followers collection synchronization across servers 4
844e Capability discovery 4
7628 Move actor 3
61cf The OpenWebAuth Protocol 3
c390 Identity Proofs 3
400e Publicly-appendable ActivityPub collections 3
c0e0 Emoji reactions 3
0151 NodeInfo in Fediverse Software (2025 edition) 3
fffd Proxy Objects 2
f228 Backfilling conversations 2
fe34 Origin-based security model 2
eb48 Hashtags 2
171b Conversation Containers 2
a5c5 Web Syndication Methods 2
There are obvious flaws in the methodology. Or maybe in the data. Only 18 out of the 30 projects I could access had a FEDERATION.md that attested FEDERATION.md support. Only 19 mentioned "FEDERATION.md". Only 21 mentioned "67ff". The remaining projects clearly did support FEP-67ff—the file itself was evidence. (FEDERATION.md is not meant to be machine readable—there's an issue about that).
It was more difficult to rank implemented federation protocols. I extracted keywords from documents with a "Supported federation protocols and standards" section and created a dictionary of terms. If a file had a section with the heading "Supported federation protocols and standards", I only looked there. Otherwise I scanned the entire document.Feature #
---------------- --
activitypub 26
webfinger 24
http_signatures 21
nodeinfo 19
json_ld 2
ld_signatures 2
ostatus 2
authorized_fetch 1
atproto 1
If time allows, I'm going to try to rank these documents by "utility", though I haven't yet determined the exact metric. These documents clearly provide valuable information, but their lack of standardization makes them harder to analyze systematically.
#ActivityPub #Fediverse #Fep67ff #fep
FEP-67ff describes the requirements of the FEDERATION.md file in loose terms and provides a non-normative template. I scraped the URLs of FEDERATION.md files from FEP-67ff itself and confirmed I could fetch them. The FEP listed 30 accessible projects (31 total, but one project—FIRM—does not appear to exist).
If a file had a section with the heading "Supported FEPs" per the non-normative template, I only looked there for supported FEPs. Otherwise I scanned the entire document.
Implemented FEPs, ranked by the number of implementations that attest support, are:FEP Name #
---- --------------------------------------------------------- --
67ff FEDERATION.md 18
f1d5 NodeInfo in Fediverse Software 16
8b32 Object Integrity Proofs 7
044f Consent-respecting quote posts 7
2677 Identifying the Application Actor 7
e232 Object Links 6
1b12 Group federation 6
3b86 Activity Intents 6
521a Representing actor's public keys 5
2c59 Discovery of a Webfinger address from an ActivityPub actor 5
7888 Demystifying the context property 5
5feb Search indexing consent for actors 5
4adb Dereferencing identifiers with webfinger 4
d556 Server-Level Actor Discovery Using WebFinger 4
fb2a Actor metadata 4
ef61 Portable Objects 4
8fcf Followers collection synchronization across servers 4
844e Capability discovery 4
7628 Move actor 3
61cf The OpenWebAuth Protocol 3
c390 Identity Proofs 3
400e Publicly-appendable ActivityPub collections 3
c0e0 Emoji reactions 3
0151 NodeInfo in Fediverse Software (2025 edition) 3
fffd Proxy Objects 2
f228 Backfilling conversations 2
fe34 Origin-based security model 2
eb48 Hashtags 2
171b Conversation Containers 2
a5c5 Web Syndication Methods 2
There are obvious flaws in the methodology. Or maybe in the data. Only 18 out of the 30 projects I could access had a FEDERATION.md that attested FEDERATION.md support. Only 19 mentioned "FEDERATION.md". Only 21 mentioned "67ff". The remaining projects clearly did support FEP-67ff—the file itself was evidence. (FEDERATION.md is not meant to be machine readable—there's an issue about that).
It was more difficult to rank implemented federation protocols. I extracted keywords from documents with a "Supported federation protocols and standards" section and created a dictionary of terms. If a file had a section with the heading "Supported federation protocols and standards", I only looked there. Otherwise I scanned the entire document.Feature #
---------------- --
activitypub 26
webfinger 24
http_signatures 21
nodeinfo 19
json_ld 2
ld_signatures 2
ostatus 2
authorized_fetch 1
atproto 1
If time allows, I'm going to try to rank these documents by "utility", though I haven't yet determined the exact metric. These documents clearly provide valuable information, but their lack of standardization makes them harder to analyze systematically.
#ActivityPub #Fediverse #Fep67ff #fep
1