Notices by @reiver ⊼ (Charles) :batman: (reiver@mastodon.social)

@evan

Should the user calling WebFinger on tags.pub — use an acct-URI and put the tag-name as the user-name of the acct-URI. Ex:

acct:fedidev@tags.pub

(For "fedidev" tag.)

(Given the actor you showed me exists, I assume that works. But SHOULD users be doing that?)

Or, can the user calling WebFinger on tags.pub use another tag-specific URI / IRI scheme besides acct-URI. Ex:

tagged:fedidev

(Again, for "fedidev" tag.)

.

@evan

For tags.pub , have you decided how a user (of tags.pub) would determine the URL to the actor for a hash-tag?

Does it involved a WebFinger look-up?

Or, another /.well-known/ look-up?

Or, will the URL pattern be documented. (Ex: /tags/{tagName} )

Or, something else?

#TagsPub

My posts on Mastodon say that no one is permitted to quote-boosts my posts — yet I never made that choice.

(I'm actually OK with others quote-boosting my posts.)

I know enough to be aware this.
Most aren't.

A very large number of people have no idea that someone else made this choice for them.

I suspect the vast majority of them would have chosen the opposite.

I think Mastodon should have represented "user has not chosen" in the JSON-LD.

#ActivitiyPub #FediDev #FediDevs #Fediverse #fep044f

RE: https://mastodon.social/@reiver/112133984854710390

"A guide to implement ActivityPub in a static site (or any website)" by @mapache

https://maho.dev/2024/02/a-guide-to-implement-activitypub-in-a-static-site-or-any-website/

#ActivityPub #ActivityStreams #FediDev #FediDevs #Fediverse

1/

RE: https://news.dyne.org/the-future-was-federated/

I agree with this sentiment of this quotation from that article:

“My identity was always subject to the will of an admin or, if I ran my own instance, this identity was simply rented from a domain name registrar.”

Although I think you can fix this with the Fediverse.

...

2/

I've been think about this for the Fediverse for a while.

I don't want to get rid of Fediverse IDs such as:

＠joeblow＠example·com

And, I don't want to get rid of the HTTPS-URLs they resolve to, such as:

https;//example·com/users/jowblow

But, I do think cryptographic public-key should be the core way you identify a user.

But, you need to deal with key-rotation, having multiple keys (maybe for different devices), having delegated keys, etc.

@dansup

Do it!

In the old blogging software I created back in the 1990s, I had a handful of posts types

There was a type of rich-text oriented post that had a title. (Article)

And, there way another type of rich-text oriented post that did not have a title. (Note)

(There were also other types of posts, but they aren't relevant here)

These 2 types of posts were rendered / displayed differently

I.e., my 1990s software already had this distinction

#ActivityPub #ActivityStreams #FediDev #FediDevs #Fediverse

I've seen an ongoing debate between "Note" versus "Article" in ActivityPub / ActivityStreams.

When is something a "Note"‽
When is something an "Article"‽

Personally — I would probably have made the distinction this way.

An "Article" has a title.
A "Note" doesn't have a title.

(In ActivityPub / ActivityStreams, a 'title' seems to tend to get represented in the "name" field.)

#ActivityPub #ActivityStreams #FediDev #FediDevs #Fediverse

People use Discord and Slack for different reasons.

If you want to create an alternative — the place to start is NOT E2EE (end to end encryption).

A place to start is understanding all these different types of users and use-cases. And then deciding which of these user types you are making the software for.

Some of them need E2EE, but some do not.

@evan

Ideally —

...

For the former —

From a UX point of view, they (Bob's followers who don't yet follow Alice) could see a placeholder post for Alice's post(s), that says that the content cannot be shown.

If a follower of Bob's then followed Alice, then the placeholder post(s) would turn into the actual post(s).

...

For the latter —

Again, from a UX point of view — Placeholder posts, until they follow Alice or Bob.

.

@evan

By default, visible to both Alice's and Bob's followers.

But, Bob should be able to change it. Even making visible to everyone.

I have been trying to think of ways of making the Fediverse more Friendly and Welcoming.

To people outside the Fediverse.

To people thinking of joining the Fediverse.

To people who recently joined the Fediverse.

And more.

...

What do YOU think could make the Fediverse more Friendly and Welcoming?

(Reply with your answers.)

#Fediverse #FriendlyFediverse #SpreadFediverse #WelcomingFediverse

@evan

Are we meeting any particular place for dinner?

@evan

Yes, I am still around.

@evan

I just noticed this 🙁 And, it looks like it already finished.

(I had a late night late night and woke up late.)

Who did this?

@benpate

cc: @julian

RE: https://mastodon.social/@reiver/114965417856379316

#FediCon #FediCon2025 #FediConMeme #Fediverse

A new bookmark sharing Fediverse software from @raffomania :

Ties
https://github.com/raffomania/ties

#Fediverse #FOSDEM #FOSDEM2026 #SocialWeb #SocialWebFOSDEM #SocialWebFOSDEM2026

Up next is @hongminhee talking about @fedify

#Fediverse #FOSDEM #FOSDEM2026 #SocialWeb #SocialWebFOSDEM #SocialWebFOSDEM2026

BridgyFed and ANewSocial mentioned in @Bonfire talk.

CC: @quillmatiq @snarfed.org

#Fediverse #FOSDEM #FOSDEM2026 #SocialWeb #SocialWebFOSDEM #SocialWebFOSDEM2026