Skip Navigation

Posts
51
Comments
269
Joined
13 yr. ago

Co-Founder (NodeBB) | Husband 🤷‍♂️ and Dad 🙉 to three | Rock Climber 🧗‍♂️ | Foodie 🥙 | Conductor 🎵 | Saxophonist 🎷

✅ Small teams craft better code.🇨🇦 Made in Canada🗨️ Federating NodeBB with funding from NLNet ♥️🇪🇺

  • @AltCode that user and the category are (I think) separate actors. I'm not sure what the user does, shares its own posts, possibly... but like you said, nobody follows that user so I suppose that's why there's not much shown as shared either.

  • It's pretty wild how wide-ranging these tariffs affect small scale manufacturers with in and out of the United States.

    I've been hearing scattered reports across different industries all saying the same thing:

    1. They have 60 days or less of inventory remaining.
    2. They cannot order more because nobody Stateside will pay for those items at prices increased to offset the tariffs.

    For companies with razor thin margins, even 1% changes the calculus. A 145% tariff is already well over the point of no return.

  • @AltCode I think it's just Flipboard, right?

    It might be because of the issue mentioned upthread where items shared by those groups don't have a back reference to the itself so it isn't slotted in it.

    They might all just be uncategorized instead. Can you find those items when you search their url or id in the NodeBB search bar?

  • @scintilla@lemm.ee that's the main thing for me too. That news orgs, political agencies, and corporations use Xitter to communicate is the real travesty.

  • :grimacing:

  • @projectmoon@forum.agnos.is have you tried navigating directly to the url without the preceding @? It isn't required (for NodeBB).

    In cases where the category is currently a user, you'll have to put the whole handle into the search box and execute the search, the category will then be migrated from the user.

  • @emperor@feddit.uk it is! The in-development stuff I'm working on makes it much easier to post directly to a Lemmy community.

    This is probably the first, yes. It was also a bit of a live test at the same time.

  • Let's clarify something here. Mastodon follower only posts don't have the "public pseudo user" addressed, do they?

    That's the important piece that this whole thing hinges upon

    If it is present, Mastodon is a fault. If not, Pixelfed messed up.

    Am I mistaken?

    For example, a followers-only post is addressed to the followers collection of the author, at minimum. When NodeBB sees this, it doesn't even consider it public, because the public pseudo user isn't addressed. We also have no concept of "followers only", but we handle them just fine.

  • @AltCode all three flipboard remote categories seem to be working now :joy:

  • The remaining questions here are:

    • whether preferredUsername is meant to be unique to the instance (in which case having multiple ids point to an identical preferredUsername would be a violation), and
    • what exactly AP software should do when it encounters this situation... store a list of "known alias" IDs? There are potential security issues to doing so.
  • @AltCode I forked this out to a new topic. I think it's time to loop @pfefferle@mastodon.social into the conversation (at the very least so this could be potentially escalated).

    Mattias, it seems that when the WPML and ActivityPub plugins are enabled together, notes federated out by the blog user in another language have different ids but the same preferredUsername.

    e.g. ruari@vivaldi.com: https://vivaldi.com/?author=46 and https://vivaldi.com/ja/?author=46

    NodeBB interprets this as two different users. Curiously, Mastodon does not, the second ID explicitly does not resolve.

    So there can be two solutions here:

    1. The underlying issue can be fixed by WordPress, the solution of which is out of scope (for me at least)
    2. NodeBB can adopt whatever mechanism Mastodon is using... which is most likely that Mastodon does a two-way when asserting an ID, and ensures that the webfinger resource points to the ID.
  • @AltCode okay! Thanks for reporting, it sounds like there are two issues going on:

    1. Categories losing their handle-to-id association
      1. Frustratingly, this read very similarly to #13283, and both remote users and categories share similar logic. I have so far not been able to reproduce it at all on local development.
    2. Separate users (different IDs) sharing the same preferredUsername.
      1. This is an interesting one, and I am not entirely sure where the fault lies. I wonder how other software handles it?