Nah, this plugin just has a placeholder ACP page, it doesn't have any settings. If you see the ratings on each topic and rate it is working.
-
Upgrade - nodebb-plugin-topic-ratings -
Anybody know what triggers a profile re-fetch in #mastodon ?@[email protected] whenever we fetch an actor, we also save the timestamp.
Right now we only update the actor if an update is received, but it would also make sense to also do an update after some pre-determined period, like 30 days, 1 year, etc.
But that's me, not Mastodon.
-
For the first time the #CoSocialCa Mastodon server has started to struggle just a little bit to keep up with the flow of the Fediverse.@[email protected] that's definitely a problem with the sidekiq configuration then. Keeping retries forever just clogs up the queue... I can't imagine they'd be kept forever!
-
This statement is going to live rent-free in my head for a long time to come, I suspect. #ActivityPub@[email protected] rent free? How else are you going to extract wealth from the working class?
/s
-
Upgrade - nodebb-plugin-topic-ratingsThat file should be in your nodebb folder, so it would be
/path/to/nodebb/node_modules/nodebb-theme-harmony/templates/partials/topics_list.tpl
. -
Are there any recent/current write ups about @Discourse federation model?@[email protected] yes, categories can be followed, and they actike Guppe groups. Right now you can't compose directly to a category but that's something I'll be working on soon!
Category actors in NodeBB can follow other actors too, just like regular users. Any content posted by followed users will be boosted by the category.
So if you have two categories that follow one another, which there are a couple between NodeBB and SocialHub (running Discourse), they're synced up!
-
This week's edition of @fediversereport is now also visible on the Social Hub Discourse forum!@[email protected] first Thursday of every month, but between meetings we discuss everything on the fediverse via ForumWG hashtag!
Would you like to be notified of meetings? I can add you to a list.
-
Upgrade - nodebb-plugin-topic-ratingsThose errors seem unrelated to this plugin, what version of nodebb are you using and what is the version of nodebb-plugin-mentions?
To get ratings plugin working you can open up
templates/partials/topics_list.tpl
in harmony theme and place<!-- IMPORT partials/ratings.tpl -->
after this line. After that run./nodebb build
and restart nodebb. -
AWS SES - Test Email Works, New User registration email doesn't workWhat test email are you sending? Try different ones, some fail silently
-
Setting up email for nodebb@julian I think we can reasonably assume that Zoho takes care of DKIM and SPF.
@eeeee what test email are you sending? Some will fail silently, so try a few different ones to see if that makes a difference.
Check your NodeBB logs to see if there are any errors recently logged.
You might also want to try setting a custom SMTP with the settings Zoho suggests. You also need to use an application specific password if you're using 2FA for Zoho.
-
Are there any recent/current write ups about @Discourse federation model?@[email protected] what would you like to know? Both NodeBB and Discourse are federating now.
-
Editing regressionYes, this is a bug in the v4 code. Will fix soon.
-
Setting up email for nodebb@eeeee You may need to reach out to Zoho support to figure that one out... if NodeBB reports that the email was sent.
Could be you need proper DKIM and SPF records.
-
Ghost has a (pretty funny) update on their #ActivityPub development.@[email protected] Yes, that's certainly one use-case for the outbox... to "catch up" on things you missed, on a per-user basis.
But as far as I am concerned they're separate APIs that pull from a common data source.
For example, reading the ActivityPub spec, one could draw the conclusion that the outbox is an ordered list of activities, likely read as-is from the database.. but that's not strictly defined, so it's possible to dynamically create outbox items on-demand based on user history stored elsewhere.
That would mean less duplication of content (and the syncing that is required), fewer bugs, etc... but the cost is the collection then has to be dynamically constructed.
-
Ghost has a (pretty funny) update on their #ActivityPub development.@[email protected] no legitimate reason, we just don't use it, and basic federation doesn't break when it's not implemented, so it's just very low down on our to-do list!
-
How do you use `context` (if at all)?@Chris-Moser Thanks for sharing your implementation of
context
in Yuforium!That's definitely an interest use-case, although I am curious why you did not consider using the
as:tag
property instead, given that it seems to be a rough parallel to your Topics.In that scenario, then you could limit
context
to what you would call Communities, though depending on how it is used, maybeaudience
could be a better fit (as per FEP-1b12) -
Ghost has a (pretty funny) update on their #ActivityPub development.@[email protected] personally, I'm still waiting for someone to call me out on having actors whose outboxes resolve to an empty collection
ducks
-
How do you use `context` (if at all)?I have created a spreadsheet with open editing permissions (for now) and invite implementors to add their implementations if applicable.
One thing I am noticing now (and should've expected) is that not every software has the concept of a discrete context, nor can you expect one from remote activities. In those scenarios, the fallback seems to be to point to the root-node Object and iterate via
replies
collection.For example:
- @[email protected]'s FedBOX defines
context
as the root-node Object. - @[email protected]'s (streams) has a concept of conversation containers, and if
context
is received, inherits it, but otherwise,context
becomes the root-node Object.
@[email protected] does FEP-7888 account for this use-case?
- @[email protected]'s FedBOX defines
-
Part of my frustration with #ActivityPub and one of the things I find baffling giving everything else in it: the lack of tools for backpressure.@[email protected] said:
Letterbook will. I'm flexible as to how, but my current plan is to duplicate the OP's replies collection into the context.
Good to know, I'll add your potential implementation into the table I'm creating... at present I'd want to know the current or potential usages of
context
. Hopefully there won't be too many disparate and incompatible implementations to reckon with... -
Part of my frustration with #ActivityPub and one of the things I find baffling giving everything else in it: the lack of tools for backpressure.@[email protected] Thanks for sharing this use-case, it's very helpful and quite novel, I might add!
An
inReplyTo
array addresses the problem of backfill/ghost-replies with a bottom-up approach, vs a context collection which would be a top-down approach... though depending on what direction your tree grows, perhaps it's the other way aroundA context collection would also provides the entire tree, which depending on size may or may not be preferred. Tradeoffs...
I think perhaps there is space for both, although I will admit that if my code encountered an Array in
inReplyTo
it might just terminate because it expects a single uri.
re: the original ask, specifically I was asking whether any other implementors specify
context
in anas:Note
, resolvable to a Collection.