February Update on ActivityPub Development
-
@Jon-Pincus said in February Update on ActivityPub Development:
Also, what's the best way to provide feedback as I run into quirky behavior ... on here, via the fediverse, filing a bug, or ... ?
Here. Be gentle
-
I appreciate it if you can put a
/worldshortcut on the left side panel, because I have to type the url each time... additionally, will this be added as sub-category or just a shortcut to the side?Additionally, these pages look strange... clearly mastodon posts are too long to be a header but it can be edited shorter since we have to click the link to read it anyway? Or posted to the
/worldpage as posts rather than title, but when clicked on it, it will lead to the related title?
-
There is one fairly important caveat currently: only public posts are supported; NodeBB will drop any content that isn't addressed to the public address.
The reason for this is that NodeBB itself doesn't have the capability to restrict visibility at the post level.
We're exploring various options so that we'd be able to support this, but at current I've simply restricted the logic so non-public posts are silently dropped.
Clearly not the ideal solution, so the sooner we resolve that the better
-
@julian We (#activitypub) need to get encryption and private messages right, consistently across apps, this is the right approach for now.
-
@julian said in February Update on ActivityPub Development:
Remote users currently cannot create topics (they'd need to "address" a category, and that's not available yet).
this will eventually be added, right?
will it function similarly to the session-sharing plugin?
-
@crazycells yes, but I'm not entirely sure what the NodeBB UI would look like for a message sent to another category.
It wouldn't work like session sharing. That's logging into another forum, which isn't my plan for this. Most ActivityPub implementations have all of the activity centred around the main server, pulling in content from outside.
It's easier than allowing anyone to log into your server. Different set of problems I guess.
-
Totally with Ю ⁂replied to Guest on last edited by [email protected]
@julian Does this work?
EDIT: OMG, it does, yay! What I don't see from my masto instance is the other replies. -
@[email protected] Yes, that's a common problem with the fediverse, inherent because of its design as a decentralized network of nodes talking to one another.
An instance/node will only know of replies to posts and topics that it is informed of, so while anyone can talk to anyone (in theory), each node may not see the entirety of responses to any given topic.
I have some ideas to address that, but it is not something that can be easily surmounted without some sort of centralized authority (which goes against the decentralization ethos that makes up much of the fediverse
) -
@julian @Totally with Ю :questified: Also because there's the difference between conversation-oriented projects (Friendica, Hubzilla, (streams), the Threadiverse, nodeBB) and Twitter-like micro-blogging projects that don't have a concept of conversations.
The former are built around being able to follow conversations, the latter lack that feature completely.
#FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta
