mastodon.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
The original server operated by the Mastodon gGmbH non-profit

Administered by:

Server stats:

373K
active users

Woo Hoo! Check out Baby's first FEP...

If you're a developer, please check out FEP-3b86 at codeberg.org/fediverse/fep/src

I'm working on "Remote Likes" and "Remote Shares" that help you jump back to your own home server to post when you find something cool on another website.

Imagine those "Share on Facebook" buttons, without all the ick.

I know it needs some work (that's what FEPs are for, yea?) so please read, comment, and help me get this over the finish line.

Codeberg.orgfep/fep/3b86/fep-3b86.md at mainfep - Fediverse Enhancement Proposals

@benpate According to RFC 8288 section 3.3, "registered" relation types can not contain a colon:

relation-type  = reg-rel-type / ext-rel-type
reg-rel-type   = LOALPHA *( LOALPHA / DIGIT / "." / "-" )
ext-rel-type   = URI

"Unregistered" relation types should be URIs (though you can argue that intent:Follow is a URN).

IETF DatatrackerRFC 8288: Web LinkingThis specification defines a model for the relationships between resources on the Web ("links") and the type of those relationships ("link relation types"). It also defines the serialisation of such links in HTTP headers with the Link header field.

@silverpill Yeah, I knew I was probably going to get bit by web standards. And I *DO* want to follow the best standards.

What do you think would be the best approach here? I think it's important to keep it short, and as semantic/descriptive as possible.

Ben Pate 🤘🏻

@silverpill @trwnh

Sorry, I meant to answer this directly, but I'm still catching up.

In the original FEP, I tried to address the FEP namespace from w3id.org. There's a lot of good reasons to use it. But I'd hate to have to type `/fep/3b86` over and over. It's not very semantic, so I went looking for something else.

What do you think of using `w3.org/ns/activitystreams/#Follow`? Are those IRIs off limits for some reason? If not, it seems like a pretty good fit.

@benpate @silverpill i don’t think it makes sense to be concerned about typing things. and if that was the case, then the fep iri is shorter and easier to type. but it doesn’t matter because these are intended to be machine-readable primarily, right?

@trwnh @silverpill

Yeah... typing is just an analogy. Machine readability is obviously a requirement, but I'd like to make them as "human readable" as possible.

I was on my phone before, so the URLs were getting garbled. I think like your suggestion best of all - using URLs like: `w3c.org/ns/activitystreams#Follow`

That seems pretty human-and-machine-readable, and is owned by the W3C. Would that work?

@benpate @trwnh A conflict may arise if other developers will start using same IRIs for something different. So I think FEP namespace is preferable, but you can indicate in the proposal that you want to switch to w3.org/ns/activitystreams namespace later.

@silverpill @trwnh This is an excellent point. We should go ahead like this.

Once this get out in the wild, changing these identifiers is nearly impossible, so let's just go with `w3id.org/fep/3b86/*` and not plan on any changes.

It looks like this will forward directly to the FEP on codeberg, so there's nothing else I need to do to "reserve" this URL.

Awesome. I'll make some changes and send an update :)