this post was submitted on 23 Jan 2025
2 points (100.0% liked)

ActivityPub

0 readers
4 users here now

Focused discussion related to ActivityPub integration in NodeBB

founded 2 days ago
 

767e2ed4-8089-40ab-92a8-7fb2204b20bd-image.png

I thought that if I entered a Fediverse address here, like '@FrankM@nrw.social,' it would follow that user, and their posts would then appear in the corresponding category.

But that's not happening. There's also no meaningful error message. The actor you see in the image probably appears because I entered an incorrect address.

Does this feature need to be enabled on the Fediverse instance 'nrw.social'?

Who can help?

you are viewing a single comment's thread
view the rest of the comments
[–] freamon@community.nodebb.org 1 points 6 hours ago

Looks like I was wrong before: whilst it's true that Lemmy isn't always great at sending an 'Accept' back, that's not the issue here. I was thinking about it from the perspective of a Person following a Group, not a Group following a Group.

It'll be interesting to see how the Lemmy devs respond. It's not really relevant for PieFed, because I'm not sure that there's communities there that have enough activity to warrant syncing to a category, but I thought about what would happen if you tried, and it would fail. The follower would be checked to see if they are a Person, and the request would go no further if not (there's no handy error returned, though).

I'm not sure it would be possible to enable, with the way the database is currently set up. We have a 'community_member' table, that looks like:

pyfedi=# \d community_member
                         Table "public.community_member"
      Column      |            Type             | Collation | Nullable | Default
------------------+-----------------------------+-----------+----------+---------
 user_id          | integer                     |           | not null |
 community_id     | integer                     |           | not null |
 is_moderator     | boolean                     |           |          |
 is_owner         | boolean                     |           |          |
 is_banned        | boolean                     |           |          |
 notify_new_posts | boolean                     |           |          |
 created_at       | timestamp without time zone |           |          |
Indexes:
    "community_member_pkey" PRIMARY KEY, btree (user_id, community_id)
    "ix_community_member_is_banned" btree (is_banned)
Foreign-key constraints:
    "community_member_community_id_fkey" FOREIGN KEY (community_id) REFERENCES community(id)
    "community_member_user_id_fkey" FOREIGN KEY (user_id) REFERENCES "user"(id)

So if the 'user_id' was actually a Group instead of a Person, then it would have a join to the wrong table.