Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://mastodon.social/users/humanetech/statuses/108932962792197765">smallcircles (Humane Tech Now) (humanetech@mastodon.social)'s status on Saturday, 03-Sep-2022 15:05:03 JST</a><a href="https://mastodon.social/@humanetech" title="humanetech@mastodon.social"><img src="https://gnusocial.jp/avatar/7161-48-20221010081419.webp" width="48" height="48" alt="smallcircles (Humane Tech Now)" style="position: absolute; left: 0; top: 0;">smallcircles (Humane Tech Now)</a><div><a href="https://federate.hopto.org/item/167167fc-f071-431f-b4be-648865650503" rel="in-reply-to">in reply to</a><ul><li></ul></div></section><article><p><a href="https://federate.hopto.org/channel/hans">@hans</a> </p><p>These frustrations are understandable. On the whole one could say that saying "Implement <a href="https://mastodon.social/tags/ActivityPub" rel="tag">#ActivityPub</a> and federate" raises wrong expectations.</p><p>And that it is more accurate to say that AS/AP et al gives you foundation stones and building blocks that constitute a framework for federated app development. Unfortunately there's been a lot of ad-hoc interoperability and protocol decay. The trend is not to maturity but chaos.</p><p>I took notes on major challenges: <a href="https://discuss.coding.social/t/major-challenges-for-the-fediverse/67" rel="nofollow noreferrer">https://discuss.coding.social/t/major-challenges-for-the-fediverse/67</a></p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/134881#notice-236856">In conversation</a><time datetime="2022-09-03T15:05:03+09:00" title="Saturday, 03-Sep-2022 15:05:03 JST">Saturday, 03-Sep-2022 15:05:03 JST</time> <span>from <span><a href="https://mastodon.social/@humanetech/108932962792197765" rel="external" title="Sent from mastodon.social via ActivityPub">mastodon.social</a></span></span><a href="https://mastodon.social/@humanetech/108932962792197765">permalink</a><h4>Attachments</h4><ol><li><article><header><div>Domain not in remote thumbnail source whitelist: discuss.coding.social</div><h5><a href="https://discuss.coding.social/t/major-challenges-for-the-fediverse/67">Major challenges for the Fediverse</a></h5><div></div></header><div>Various forum topics highlights big challenges for the Fediverse to overcome. Below there is a list of those, and all of them are within scope of Social Coding #foundations to contribute to solutions.      Challenge Description     Lack of a shared (technology) vision People just use the Fediverse in its current state without asking what it could be in the future. The potential and opportunities are insufficiently explored.   Stuck Fediverse Adoption Lifecycle A combination of factors make onboa...</div><footer></footer></article></li></ol></footer></blockquote>

Corresponding Notice

Embed this notice
smallcircles (Humane Tech Now) (humanetech@mastodon.social)'s status on Saturday, 03-Sep-2022 15:05:03 JSTsmallcircles (Humane Tech Now)
in reply to
- Hans
@hans
These frustrations are understandable. On the whole one could say that saying "Implement #ActivityPub and federate" raises wrong expectations.
And that it is more accurate to say that AS/AP et al gives you foundation stones and building blocks that constitute a framework for federated app development. Unfortunately there's been a lot of ad-hoc interoperability and protocol decay. The trend is not to maturity but chaos.
I took notes on major challenges: https://discuss.coding.social/t/major-challenges-for-the-fediverse/67
In conversationSaturday, 03-Sep-2022 15:05:03 JST from mastodon.socialpermalink
Attachments
1. Domain not in remote thumbnail source whitelist: discuss.coding.social
  Major challenges for the Fediverse
  Various forum topics highlights big challenges for the Fediverse to overcome. Below there is a list of those, and all of them are within scope of Social Coding #foundations to contribute to solutions. Challenge Description Lack of a shared (technology) vision People just use the Fediverse in its current state without asking what it could be in the future. The potential and opportunities are insufficiently explored. Stuck Fediverse Adoption Lifecycle A combination of factors make onboa...

Public

Embed Notice

HTML Code

Corresponding Notice