#litepub

[autogestion]

Litepub manifesto:
https://pleroma.site/notice/2300746
As for me, interesting idea, especially for light-weight nodes.
So questions are:
Does it make sense? Shall it be supported by this package? Is there a need, that package could be a router between forks (provide a posibility to interact both with mastodon and pleroma)

[dsblank]

My main goal is to create tools to help as many people get started with ActivityPub (AP) as possible. There are many hard things to understand in creating the stack: the database, the AP objects, the AP logic, the AP interactions, the web framework, Javascript, CSS, security, speed, capacity, identity transfer, etc. So lots of places for all of us to work together, lots of unsolved problems.

Some comments:

• a subset of ActivityPub is still ActivityPub, not a fork
• JSON-LD is indeed complicated
• We don't need to focus on it now (if ever). We can just handle the defaults for now
• We should focus on getting as many instances to talk to each other via the standard as possible
• The standard has many places where we need examples of what was intended, and perhaps refinements. This is version 1.

The above is a good manifesto in my opinion. We have enough forces working against an open social network without us breaking into factions. Let's work together towards the dream open social network!

[dsblank]

Regarding differences between Mastodon, Pleroma, and ActivityPub: let's all follow the standard as best as possible. Sure, we can adapt input to slight variation, but still produce valid AP output. In the end, the projects that cooperate the best will win. I guarantee that the most popular open social network software today will not be the most popular in two years. Because if a project isn't part of the AP federation, they will lose users.