Added announce handling #13
Conversation
src/app.ts
Outdated
| @@ -105,6 +111,13 @@ fedify | |||
| ) | |||
| .setCounter(followingCounter); | |||
|
|
|||
| fedify | |||
There was a problem hiding this comment.
If we're using this - then I think we need to remove the custom inbox handler on line 220, as well as the backing code behind it
There was a problem hiding this comment.
👍 Didn't realise we already had an inbox handler 🤦♂️ I'll move the logic to the existing handler and create an issue to refactor the existing handler to utilise setInboxDispatcher in the future
src/dispatchers.ts
Outdated
| const thing = await ctx.data.globaldb.get<StoredThing>([result]); | ||
|
|
||
| // If the object is a string, it's a URI, so we should to look it up | ||
| // in the globalDb. If it's not in the globalDb, we should just |
There was a problem hiding this comment.
Long term we probably want to fetch it from the network and store it - but this is fine for now
There was a problem hiding this comment.
Not sure I'm following - In the case of Announce we retrieve the announced object and store it at the point of handling the Announce activity. So at this point, we already have the object in the db?
(obviously this is only valid for Announce activities that have been handled by the handler)
mike182uk
force-pushed
the
initial-announce-handling
branch
from
0ac916c to
8893c0a
Compare
mike182uk
force-pushed
the
initial-announce-handling
branch
from
8893c0a to
8f9381b
Compare
mike182uk
force-pushed
the
initial-announce-handling
branch
from
f343e97 to
e50bb2a
Compare
Added announce handling
refs MOM-280