julian

@julian@activitypub.space

• ⁨Comment⁩ on ⁨Another Quick Test (Disabled Federated Upvotes)⁩ ⁨⁨1⁩ ⁨week⁩ ago⁩:

  @anthony@forum.unfinishedprojects.net did you just remove the privilege from "fediverse"? Leave it on for "registered-users"

• ⁨Comment⁩ on ⁨This is a federated test post from a nodeBB forum.⁩ ⁨⁨1⁩ ⁨week⁩ ago⁩:

  I put together a brief explainer here 🙂

  https://community.nodebb.org/topic/19218/federation-what-is-it-and-how-does-it-work

• ⁨Comment⁩ on ⁨This is a federated test post from a nodeBB forum.⁩ ⁨⁨1⁩ ⁨week⁩ ago⁩:

  @anthony@forum.unfinishedprojects.net said in This is a federated test post from a nodeBB forum.:

  [Edit] does anybody know if nodeBB has a way to prevent federated upvotes from contributing to forum member specific reputation points?

  I didn't see this edit until just now.

  Ah... no, this is not available, but if it is important to you, I would recommend you open a GitHub issue. This could be something toggleable by admins.

• ⁨Comment⁩ on ⁨Can Canada find digital sovereignty in the Fediverse? | BetaKit⁩ ⁨⁨1⁩ ⁨week⁩ ago⁩:

  'twas a good conference 😁

• ⁨Comment⁩ on ⁨This is a federated test post from a nodeBB forum.⁩ ⁨⁨1⁩ ⁨week⁩ ago⁩:

  It's a linear view, in case you were wondering

  1000012204.png

• ⁨Comment⁩ on ⁨This is a federated test post from a nodeBB forum.⁩ ⁨⁨1⁩ ⁨week⁩ ago⁩:

  Well, nice to see this post come up. Hello!

• ⁨Comment⁩ on ⁨⁩ ⁨⁨1⁩ ⁨week⁩ ago⁩:

  To add a remote community to your forum index, you'll want to go to ACP > Manage > Categories

  Under the "Add Category" dropdown, you can select the option to add a remote category.

  cd6c786d-c376-4b76-a1da-d301074cb142-image.jpeg

  Then you can treat them like any other category (re-order, rename, etc.)

  ---

  The page you're on now, the category synchronization, allows a category to follow another category, and automatically cross-post its posts to that category. It also kind of does what you want, but it'll be more straightforward to add the remote community directly.

• ⁨Comment⁩ on ⁨⁩ ⁨⁨1⁩ ⁨week⁩ ago⁩:

  Oh! That looks to be a bug too.

• ⁨Comment⁩ on ⁨⁩ ⁨⁨1⁩ ⁨week⁩ ago⁩:

  Related Communities is just a header, the related communities themselves are listed below that header :slightly_smiling_face:

• ⁨Comment⁩ on ⁨⁩ ⁨⁨1⁩ ⁨week⁩ ago⁩:

  @unfinishedprojects@piefed.zip said in NodeBB forum federation questions.:

  But it sounds like the federation is more so to bring traffic into the forum, rather then out. Did I understand that correctly?

  NodeBB is a two-way ActivityPub server, which means that it pushes content out to the wider fediverse, as well as allowing you to discover new content via followers and /world.

  So for your use-case, NodeBB is still a good way to push forum content into communities. You can even set up NodeBB so that your forum index doesn't contain any local categories, but is actually made up of remote categories!

  For example, look at https://activitypub.space, under the "Related Communities" section, contain a couple of sub-categories which are actually Lemmy and Piefed communities. So you are able to just post there if you have content to share :slightly_smiling_face:

• ⁨Comment⁩ on ⁨⁩ ⁨⁨1⁩ ⁨week⁩ ago⁩:

  Hello! I'll try my best to answer your questions :slightly_smiling_face:

  1. I honestly don't know what to do about this. I briefly played around with CloudFlare rules to get federation working, and settled on the configuration I talk about here: https://community.nodebb.org/post/105742 I later de-activated it and just set up anubis as well (although because anubis is protected by anubis, good luck getting an LLM to help you set it up LOL)
  2. The following indicator is a little wonky, you should just ignore it until I fix it :stuck_out_tongue: as long as your piefed account shows up in the page itself (/following, you're ok.
  3. /world is a feed of content from the wider fediverse. It's like a home timeline in Mastodon where it will show you content from the people you follow or content shared by your followers.
     • You should think of categories like Lemmy/Piefed communities. Instead of setting up a category to post to specific instances, you should post your content to that specific community itself (you can go to it via the /world page, by searching for its handle)
     • You can then cross-post that remote topic back to your forum. Cross-posting only works that way right now because there is no standardized way to federate cross-posts across instances, yet.

  The easiest way to integrate your forum into the fediverse is to set up some relays and use the FediBuzz relay to listen to some hashtags. You can then set up auto-categorization rules to bring those discussions into your categories.

  Easiest way to integrate your forum into the threadiverse is to just start posting. Post to other categories on other instances... encourage people to add your categories (I guess?) and it'll start showing up in peoples' home feeds.

  I'm not exactly sure what people do on the threadiverse when they want to start a new community... lemmy-federate maybe, but NodeBB is not compatible with it yet.

• ⁨Comment⁩ on ⁨⁩ ⁨⁨2⁩ ⁨weeks⁩ ago⁩:

  Can't Piefed, et al. do everything a.gup.pe/FediGroups could do, and more?

• ⁨Comment⁩ on ⁨Is the threadiverse abusing Likes and Dislikes?⁩ ⁨⁨2⁩ ⁨weeks⁩ ago⁩:

  Hmmmm, I suppose, but Facebook never had a Dislike, they added emoji reactions, technically, no?

• ⁨Comment⁩ on ⁨Is the threadiverse abusing Likes and Dislikes?⁩ ⁨⁨3⁩ ⁨weeks⁩ ago⁩:

  Eh that's that age-old Reddit argument, isn't it?

  Vote for visibility, not for agreement.

  But yeah, like probably 99% of users abuse Like and Dislike as "I agree" and "I don't agree".

  Also here's a picture just to screw with you:

  cover6.jpg

• ⁨Comment⁩ on ⁨To image cache or not to image cache⁩ ⁨⁨3⁩ ⁨weeks⁩ ago⁩:

  As @ptz@dubvee.org said, just disable it. There's very little benefit and huge (financial) dowbside.

  Yeah storage is cheap, but S3 cache costs are also like the #1 thing people hosting Mastodon complain about.

  If you're privacy conscious and worry about IP leakage... then install a camo proxy. Done. That also solves the CORS issues.

• ⁨Comment⁩ on ⁨(Serious) networking with other academics appears difficult⁩ ⁨⁨4⁩ ⁨weeks⁩ ago⁩:

  I think there's definitely an underserved space for academics on the fediverse.

  Feed-based mechanics are not good for archival or slower (read: not always online) readers, so NodeBB actually works really well to collect that stuff and present it in less of a firehose-y format.

  For example, here's a NodeBB forum that follows the #medicine tag: https://postcall.pub

  I'd be happy to work with you to start a general science (or more topic-focused) board if you're interested...

• ⁨Comment⁩ on ⁨[deleted]⁩ ⁨⁨4⁩ ⁨weeks⁩ ago⁩:

  The PixelFed kickstarter was actual money delivered to a bank account. I don't know how much more incentive one needs.

  I will try hard not to speak ill of a fellow Canuck however.

• ⁨Comment⁩ on ⁨[deleted]⁩ ⁨⁨4⁩ ⁨weeks⁩ ago⁩:

  Good on you Rimu. If NodeBB implements Activity Intents it'll be because of you.

• ⁨Comment⁩ on ⁨Recommendations for federated CMS alternatives to Wordpress?⁩ ⁨⁨1⁩ ⁨month⁩ ago⁩:

  @hendrik@palaver.p3x.de fwiw NodeBB ended up being such a joy to author things in that we switched away from WordPress to NodeBB as our blog. We just blog on our forum.

  Now, conflicts of interest are important... I wrote NodeBB, so I am obviously pretty biased :laughing: !

• ⁨Comment⁩ on ⁨Ideas for a better Lemmy experience⁩ ⁨⁨1⁩ ⁨month⁩ ago⁩:

  I'll give some insight from NodeBB.

  Adding in delays (x days until first post, y hours until upvote, etc.) do nothing to curb spam.

  If your spam is manual, they will discover the waiting period, update their rulebook, and go to town when the waiting period is over.

  If the spam is automated, it will work until the spammer admin discovers the waiting period, updates the script, and has the bots resume going to town when the waiting period is over.

  At the same time it severly hampers usability at its most crucial (the first post).

  The only thing that works to curb spam is a post queue with manual review... or locking the ability to post links behind reputation.

• ⁨Comment⁩ on ⁨Would a fediverse alternative of Discord be possible?⁩ ⁨⁨1⁩ ⁨month⁩ ago⁩:

  Except it's completely gated behind Discord corporate servers, unsearchable outside of Discord, and all ownership lies with... you guessed it, Discord.

  But oooh aah Nitro....

• ⁨Comment⁩ on ⁨Would a fediverse alternative of Discord be possible?⁩ ⁨⁨1⁩ ⁨month⁩ ago⁩:

  Discord has both private and public channels. I won't bother considering their threaded discussion offerings, because they're absolutely horrendous.

  ActivityPub is primarily public. You have scoped visibility that enables things like private messaging, but there is no implementation that allows for federated private group discussions.

  There are proposals and a few implementations, but they all rely on everybody else to implement the same proposal, otherwise messages leak out, and that defeats the entire assumption of the private group.

  It's not an unsolvable problem, merely one that hasn't been successfully solved yet.

  As for whether AP is a good fit... It'll work. At the end of the day you're exchanging messages. Whether they're long form or chat messages makes little difference.

• ⁨Comment⁩ on ⁨New Social Web Working Group at W3C⁩ ⁨⁨1⁩ ⁨month⁩ ago⁩:

  Oh I see. Yes, AP first apps would be great, but getting older apps connected via AP is important too.

  NodeBB predates ActivityPub (or came around the same time), and so we added it recently. It works quite well with our existing code. Not much of a compatibility layer.

• ⁨Comment⁩ on ⁨New Social Web Working Group at W3C⁩ ⁨⁨1⁩ ⁨month⁩ ago⁩:

  What is this proprietary layer you speak of?

• ⁨Comment⁩ on ⁨New Social Web Working Group at W3C⁩ ⁨⁨1⁩ ⁨month⁩ ago⁩:

  This is something I believe the ActivityPub API can tackle...

• ⁨Comment⁩ on ⁨New Social Web Working Group at W3C⁩ ⁨⁨1⁩ ⁨month⁩ ago⁩:

  To my knowledge, one must be an "invited expert" in order to join these discussions.

  However, the working group is only one aspect. The community group has been in existence for a number of years. I am part of that group (although I admit I don't go to as many meetings as I ought to), and try to represent the threadiverse as best as I can.

• ⁨Comment⁩ on ⁨If a Lemmy user has the same name as a community, how can I tag the community on Mastodon?⁩ ⁨⁨1⁩ ⁨month⁩ ago⁩:

  Nope, it's just a.single route, no filters or qualifiers I am aware of.

  One could go through the returned accounts and see which are users and which are groups, although that's expensive and time consuming to do.

• ⁨Comment⁩ on ⁨If a Lemmy user has the same name as a community, how can I tag the community on Mastodon?⁩ ⁨⁨1⁩ ⁨month⁩ ago⁩:

  Agreed... I didn't respond right away since I wasn't sure if I was right, but there are two constraints at play here:

  • Lemmy wants to allow communities to be named the same as a user
  • This is not allowed in webfinger (insomuch that multiple IDs reports should refer to the same entity)

  You can fault Mastodon for not handling it, but I think the onus is on Lemmy to adjust their behaviour.

  For reference, the same constraint happened with NodeBB. When we started, categories didn't have handles and were not unique with users (so, a category could be named the same as a user). I needed to make the handle unique between both categories and users, for this exact reason.

• ⁨Comment⁩ on ⁨Random idea: a federated alternative to Amazon Prime built from independent shops?⁩ ⁨⁨2⁩ ⁨months⁩ ago⁩:

  Sounds like Rakuten actually...

• ⁨Comment⁩ on ⁨Fediverse wide cross-instance / cross-platform link substitution [UX improvement thoughts]⁩ ⁨⁨2⁩ ⁨months⁩ ago⁩:

  If it's some automated feature, I don't think it should be in the source property of the federated JSON in the first place.

  Thanks, it's this.

  Edit: oh interesting, I looked into it. We serve the absolute URL in HTML but not in markdown. I had no idea threadiverse apps read the markdown. Neat!