#activitypub-2 — Public Fediverse posts

[中文转载]

Mastodon 创作者分享了 Threads 出了什么问题，并思考 fediverse 的未来

原文链接（皆来自fediverse外）

https://coywolf.com/news/social-media/mastodon-creator-shares-what-went-wrong-with-threads-and-ponders-the-future-of-the-fediverse/
https://www.reddit.com/r/fediverse/comments/1p9veu4/interview_with_eugen_rochko_creator_of_mastodon/

#fedivser #mastodon #gotosocial #twitter #threads #atprotocol #activitypub #activitypub2.0 #Eugen_Rochko #社交网络 #开放社交网络 #x #socialmedia
@worldboard @board

[中文转载]

Mastodon 创作者分享了 Threads 出了什么问题，并思考 fediverse 的未来

原文链接（皆来自fediverse外）

https://coywolf.com/news/social-media/mastodon-creator-shares-what-went-wrong-with-threads-and-ponders-the-future-of-the-fediverse/
https://www.reddit.com/r/fediverse/comments/1p9veu4/interview_with_eugen_rochko_creator_of_mastodon/

#fedivser #mastodon #gotosocial #twitter #threads #atprotocol #activitypub #activitypub2.0 #Eugen_Rochko #社交网络 #开放社交网络 #x #socialmedia
@worldboard @board

[中文转载]

Mastodon 创作者分享了 Threads 出了什么问题，并思考 fediverse 的未来

原文链接（皆来自fediverse外）

https://coywolf.com/news/social-media/mastodon-creator-shares-what-went-wrong-with-threads-and-ponders-the-future-of-the-fediverse/
https://www.reddit.com/r/fediverse/comments/1p9veu4/interview_with_eugen_rochko_creator_of_mastodon/

#fedivser #mastodon #gotosocial #twitter #threads #atprotocol #activitypub #activitypub2.0 #Eugen_Rochko #社交网络 #开放社交网络 #x #socialmedia
@worldboard @board

The other thing that the #Guppe incident showed us is that the #Fediverse seriously needs the #Nomadic protocol.

Let's say the Fediverse understands the protocol: just move to a new domain, inform all instances "this is the new domain, automatically re-subscribe please", done. Life goes on for regular people.

I am not saying it is that easy or that's how exactly it will work. But it could've been avoided. Right now, entire communities are gone, many who were relying on it are now disconnected. (Then again, I can argue that it's time to clean the membership since many accounts are also stagnant.)

So, when? #ActivityPub2 ?

#SocialWeb #OpenSocial #OpenSocialWeb

The other thing that the #Guppe incident showed us is that the #Fediverse seriously needs the #Nomadic protocol.

Let's say the Fediverse understands the protocol: just move to a new domain, inform all instances "this is the new domain, automatically re-subscribe please", done. Life goes on for regular people.

I am not saying it is that easy or that's how exactly it will work. But it could've been avoided. Right now, entire communities are gone, many who were relying on it are now disconnected. (Then again, I can argue that it's time to clean the membership since many accounts are also stagnant.)

So, when? #ActivityPub2 ?

#SocialWeb #OpenSocial #OpenSocialWeb

The other thing that the #Guppe incident showed us is that the #Fediverse seriously needs the #Nomadic protocol.

Let's say the Fediverse understands the protocol: just move to a new domain, inform all instances "this is the new domain, automatically re-subscribe please", done. Life goes on for regular people.

I am not saying it is that easy or that's how exactly it will work. But it could've been avoided. Right now, entire communities are gone, many who were relying on it are now disconnected. (Then again, I can argue that it's time to clean the membership since many accounts are also stagnant.)

So, when? #ActivityPub2 ?

#SocialWeb #OpenSocial #OpenSocialWeb

The other thing that the #Guppe incident showed us is that the #Fediverse seriously needs the #Nomadic protocol.

Let's say the Fediverse understands the protocol: just move to a new domain, inform all instances "this is the new domain, automatically re-subscribe please", done. Life goes on for regular people.

I am not saying it is that easy or that's how exactly it will work. But it could've been avoided. Right now, entire communities are gone, many who were relying on it are now disconnected. (Then again, I can argue that it's time to clean the membership since many accounts are also stagnant.)

So, when? #ActivityPub2 ?

#SocialWeb #OpenSocial #OpenSocialWeb

The other thing that the #Guppe incident showed us is that the #Fediverse seriously needs the #Nomadic protocol.

Let's say the Fediverse understands the protocol: just move to a new domain, inform all instances "this is the new domain, automatically re-subscribe please", done. Life goes on for regular people.

I am not saying it is that easy or that's how exactly it will work. But it could've been avoided. Right now, entire communities are gone, many who were relying on it are now disconnected. (Then again, I can argue that it's time to clean the membership since many accounts are also stagnant.)

So, when? #ActivityPub2 ?

#SocialWeb #OpenSocial #OpenSocialWeb

The first, original, and true, account portability, #NomadicIdentity, is coming to #ActivityPub!

@news explained it in an easy to understand way, so be sure to read this article.

https://wedistribute.org/2024/03/activitypub-nomadic-identity/

#Fediverse #MycelialWeb #SocialWeb #SNS #Streams #Hubzilla #Zot #Nomadic #DDFON #ActivityPub2

The first, original, and true, account portability, #NomadicIdentity, is coming to #ActivityPub!

@news explained it in an easy to understand way, so be sure to read this article.

https://wedistribute.org/2024/03/activitypub-nomadic-identity/

#Fediverse #MycelialWeb #SocialWeb #SNS #Streams #Hubzilla #Zot #Nomadic #DDFON #ActivityPub2

The first, original, and true, account portability, #NomadicIdentity, is coming to #ActivityPub!

@news explained it in an easy to understand way, so be sure to read this article.

https://wedistribute.org/2024/03/activitypub-nomadic-identity/

#Fediverse #MycelialWeb #SocialWeb #SNS #Streams #Hubzilla #Zot #Nomadic #DDFON #ActivityPub2

The first, original, and true, account portability, #NomadicIdentity, is coming to #ActivityPub!

@news explained it in an easy to understand way, so be sure to read this article.

https://wedistribute.org/2024/03/activitypub-nomadic-identity/

#Fediverse #MycelialWeb #SocialWeb #SNS #Streams #Hubzilla #Zot #Nomadic #DDFON #ActivityPub2

The first, original, and true, account portability, #NomadicIdentity, is coming to #ActivityPub!

@news explained it in an easy to understand way, so be sure to read this article.

https://wedistribute.org/2024/03/activitypub-nomadic-identity/

#Fediverse #MycelialWeb #SocialWeb #SNS #Streams #Hubzilla #Zot #Nomadic #DDFON #ActivityPub2

I kinda think an #ActivityPub2 would be a good idea. Mostly to clarify and critically rethink everything, but also to cement ecosystem choices like Webfinger.

The criteria for me would be:
* No involvement from Meta. Federating with them isn't the real EEE danger, this is. They MUST be forbidden from being even remotely involved in the development of AP2.
* More clear and mandatory support for extended actor types.
* Drop JSON-LD; use well-specified schema-based JSON with some URI references instead.
* Use a URN for the "Public" special virtual actor.
* Add error conditions and well-known endpoints to the C2S API. Such endpoints might include all public activities or objects; some well known filter options should be specified but not required, like length limitations; pagination should be required too if limits are supported.
* WebFinger should be specified, as SHOULD. Domain webfingers should be added, and the lookup procedure and treatment of handles should also be specified.
* Some form of HTTP signatures should be specified, also as SHOULD.
* AP2 connections should include a new MIME type, possibly application/activity.2+json, which differentiates from AP1 and enables compatibility.
* Personal and custodial keys should be separated. Neither are required, and if both are specified, they each have different powers. Key changes must be signed but newly introduced keys are trusted on first use, as they are today. So you can create or upload your personal key after creating an account.
* An extension registry. It should be dead simple for a community or independent developer to submit extensions; corporations and their associates will have every extension and change thoroughly audited and they must be approved by the non-corporate members of SWICG before they are added; likewise, any corporate-submitted extension must have first appeared in a sufficiently FLOSS application whose source is easily available (so, WordPress can submit extensions, but not Tumblr).

This list may be incomplete.

I kinda think an #ActivityPub2 would be a good idea. Mostly to clarify and critically rethink everything, but also to cement ecosystem choices like Webfinger.

The criteria for me would be:
* No involvement from Meta. Federating with them isn't the real EEE danger, this is. They MUST be forbidden from being even remotely involved in the development of AP2.
* More clear and mandatory support for extended actor types.
* Drop JSON-LD; use well-specified schema-based JSON with some URI references instead.
* Use a URN for the "Public" special virtual actor.
* Add error conditions and well-known endpoints to the C2S API. Such endpoints might include all public activities or objects; some well known filter options should be specified but not required, like length limitations; pagination should be required too if limits are supported.
* WebFinger should be specified, as SHOULD. Domain webfingers should be added, and the lookup procedure and treatment of handles should also be specified.
* Some form of HTTP signatures should be specified, also as SHOULD.
* AP2 connections should include a new MIME type, possibly application/activity.2+json, which differentiates from AP1 and enables compatibility.
* Personal and custodial keys should be separated. Neither are required, and if both are specified, they each have different powers. Key changes must be signed but newly introduced keys are trusted on first use, as they are today. So you can create or upload your personal key after creating an account.
* An extension registry. It should be dead simple for a community or independent developer to submit extensions; corporations and their associates will have every extension and change thoroughly audited and they must be approved by the non-corporate members of SWICG before they are added; likewise, any corporate-submitted extension must have first appeared in a sufficiently FLOSS application whose source is easily available (so, WordPress can submit extensions, but not Tumblr).

This list may be incomplete.

I kinda think an #ActivityPub2 would be a good idea. Mostly to clarify and critically rethink everything, but also to cement ecosystem choices like Webfinger.

The criteria for me would be:
* No involvement from Meta. Federating with them isn't the real EEE danger, this is. They MUST be forbidden from being even remotely involved in the development of AP2.
* More clear and mandatory support for extended actor types.
* Drop JSON-LD; use well-specified schema-based JSON with some URI references instead.
* Use a URN for the "Public" special virtual actor.
* Add error conditions and well-known endpoints to the C2S API. Such endpoints might include all public activities or objects; some well known filter options should be specified but not required, like length limitations; pagination should be required too if limits are supported.
* WebFinger should be specified, as SHOULD. Domain webfingers should be added, and the lookup procedure and treatment of handles should also be specified.
* Some form of HTTP signatures should be specified, also as SHOULD.
* AP2 connections should include a new MIME type, possibly application/activity.2+json, which differentiates from AP1 and enables compatibility.
* Personal and custodial keys should be separated. Neither are required, and if both are specified, they each have different powers. Key changes must be signed but newly introduced keys are trusted on first use, as they are today. So you can create or upload your personal key after creating an account.
* An extension registry. It should be dead simple for a community or independent developer to submit extensions; corporations and their associates will have every extension and change thoroughly audited and they must be approved by the non-corporate members of SWICG before they are added; likewise, any corporate-submitted extension must have first appeared in a sufficiently FLOSS application whose source is easily available (so, WordPress can submit extensions, but not Tumblr).

This list may be incomplete.

I kinda think an #ActivityPub2 would be a good idea. Mostly to clarify and critically rethink everything, but also to cement ecosystem choices like Webfinger.

The criteria for me would be:
* No involvement from Meta. Federating with them isn't the real EEE danger, this is. They MUST be forbidden from being even remotely involved in the development of AP2.
* More clear and mandatory support for extended actor types.
* Drop JSON-LD; use well-specified schema-based JSON with some URI references instead.
* Use a URN for the "Public" special virtual actor.
* Add error conditions and well-known endpoints to the C2S API. Such endpoints might include all public activities or objects; some well known filter options should be specified but not required, like length limitations; pagination should be required too if limits are supported.
* WebFinger should be specified, as SHOULD. Domain webfingers should be added, and the lookup procedure and treatment of handles should also be specified.
* Some form of HTTP signatures should be specified, also as SHOULD.
* AP2 connections should include a new MIME type, possibly application/activity.2+json, which differentiates from AP1 and enables compatibility.
* Personal and custodial keys should be separated. Neither are required, and if both are specified, they each have different powers. Key changes must be signed but newly introduced keys are trusted on first use, as they are today. So you can create or upload your personal key after creating an account.
* An extension registry. It should be dead simple for a community or independent developer to submit extensions; corporations and their associates will have every extension and change thoroughly audited and they must be approved by the non-corporate members of SWICG before they are added; likewise, any corporate-submitted extension must have first appeared in a sufficiently FLOSS application whose source is easily available (so, WordPress can submit extensions, but not Tumblr).

This list may be incomplete.

I kinda think an #ActivityPub2 would be a good idea. Mostly to clarify and critically rethink everything, but also to cement ecosystem choices like Webfinger.

The criteria for me would be:
* No involvement from Meta. Federating with them isn't the real EEE danger, this is. They MUST be forbidden from being even remotely involved in the development of AP2.
* More clear and mandatory support for extended actor types.
* Drop JSON-LD; use well-specified schema-based JSON with some URI references instead.
* Use a URN for the "Public" special virtual actor.
* Add error conditions and well-known endpoints to the C2S API. Such endpoints might include all public activities or objects; some well known filter options should be specified but not required, like length limitations; pagination should be required too if limits are supported.
* WebFinger should be specified, as SHOULD. Domain webfingers should be added, and the lookup procedure and treatment of handles should also be specified.
* Some form of HTTP signatures should be specified, also as SHOULD.
* AP2 connections should include a new MIME type, possibly application/activity.2+json, which differentiates from AP1 and enables compatibility.
* Personal and custodial keys should be separated. Neither are required, and if both are specified, they each have different powers. Key changes must be signed but newly introduced keys are trusted on first use, as they are today. So you can create or upload your personal key after creating an account.
* An extension registry. It should be dead simple for a community or independent developer to submit extensions; corporations and their associates will have every extension and change thoroughly audited and they must be approved by the non-corporate members of SWICG before they are added; likewise, any corporate-submitted extension must have first appeared in a sufficiently FLOSS application whose source is easily available (so, WordPress can submit extensions, but not Tumblr).

This list may be incomplete.

I wonder when we'll see custom domain #WebFinger in the #Fediverse / #ActivityPub ?

For example, I want to use:
* @-live.youronly.one for my #Streams account
* @-sns.youronly.one for my #Firefish account
* @-photos.youronly.one for my #Pixelfed account
* @-mblog.youronly.one for my #Mastodon account
* @-reading.youronly.one for my #BookWyrm account

Ideally, even if I move to a new host/service, I can use the same WebFinger.

#MycelialWeb #MyceliumNetwork #ActivityPub2 #AP #AP2 #Portability #AccountPortability #Nomadic #NomadicIdentity #SNS #SocialWeb #SocialMedia #SocialNetwork

I wonder when we'll see custom domain #WebFinger in the #Fediverse / #ActivityPub ?

For example, I want to use:
* @-live.youronly.one for my #Streams account
* @-sns.youronly.one for my #Firefish account
* @-photos.youronly.one for my #Pixelfed account
* @-mblog.youronly.one for my #Mastodon account
* @-reading.youronly.one for my #BookWyrm account

Ideally, even if I move to a new host/service, I can use the same WebFinger.

#MycelialWeb #MyceliumNetwork #ActivityPub2 #AP #AP2 #Portability #AccountPortability #Nomadic #NomadicIdentity #SNS #SocialWeb #SocialMedia #SocialNetwork

I wonder when we'll see custom domain #WebFinger in the #Fediverse / #ActivityPub ?

For example, I want to use:
* @-live.youronly.one for my #Streams account
* @-sns.youronly.one for my #Firefish account
* @-photos.youronly.one for my #Pixelfed account
* @-mblog.youronly.one for my #Mastodon account
* @-reading.youronly.one for my #BookWyrm account

Ideally, even if I move to a new host/service, I can use the same WebFinger.

#MycelialWeb #MyceliumNetwork #ActivityPub2 #AP #AP2 #Portability #AccountPortability #Nomadic #NomadicIdentity #SNS #SocialWeb #SocialMedia #SocialNetwork

I wonder when we'll see custom domain #WebFinger in the #Fediverse / #ActivityPub ?

For example, I want to use:
* @-live.youronly.one for my #Streams account
* @-sns.youronly.one for my #Firefish account
* @-photos.youronly.one for my #Pixelfed account
* @-mblog.youronly.one for my #Mastodon account
* @-reading.youronly.one for my #BookWyrm account

Ideally, even if I move to a new host/service, I can use the same WebFinger.

#MycelialWeb #MyceliumNetwork #ActivityPub2 #AP #AP2 #Portability #AccountPortability #Nomadic #NomadicIdentity #SNS #SocialWeb #SocialMedia #SocialNetwork

I wonder when we'll see custom domain #WebFinger in the #Fediverse / #ActivityPub ?

For example, I want to use:
* @-live.youronly.one for my #Streams account
* @-sns.youronly.one for my #Firefish account
* @-photos.youronly.one for my #Pixelfed account
* @-mblog.youronly.one for my #Mastodon account
* @-reading.youronly.one for my #BookWyrm account

Ideally, even if I move to a new host/service, I can use the same WebFinger.

#MycelialWeb #MyceliumNetwork #ActivityPub2 #AP #AP2 #Portability #AccountPortability #Nomadic #NomadicIdentity #SNS #SocialWeb #SocialMedia #SocialNetwork

So with the surge of traffic that's coming to #ActivityPub and the #Fediverse, I stumbled into a conversation about updating ActivityPub. I'm curious what people with a better #Dev and #admin background think should be changed in regard to an #ActivityPub2 since the original standard was released in 2018 and the Fediverse has changed dramatically since then.

Also, are any changes already being proposed?

@sabogato @clacke @atomicpoet @pre sorry i was sort of absent

Do we want to chat upon the topic of #ActivityPub2/#Mastodev/#Pleroma?
ideally via Mumble/Jitsi or something.

My toots auto-delete after 1w which means the Masto toot chain broke (bad protocol implementation ; RFC 822 does chaining a lot better)