julian

joined 12 years ago
[–] [email protected] 6 points 11 hours ago

[email protected] personally, since I create AP enabled software I am on the side of votes being public data. We already have enough issues with votes being out of sync with each other. Mixing in private voting is just asking for trouble.

Emoji reactions are neat, although niche to those softwares that utilise it. They allow for greater expression which is nice. They're useless for deriving value (for ranking purposes) unless you assign value to them.

[–] [email protected] 3 points 1 day ago (1 children)

Does anyone remember way before Google had image recognition technology, the time they built a game that paired up random people on the internet, showed them each an image, and waited for them to both guess the same keyword?

It was gamified human powered taxonomy for meaningless internet points and it was hilarious (at the time.)

[–] [email protected] 8 points 2 days ago (2 children)

[email protected] A little bit, yes! There was a recent thread in the community I posted to where a discussion about the rather lacklustre search of various software took place.

 

You might've heard that search sucks on software X... maybe software Y... definitely on software Z. The default one kind of sucks on NodeBB too, admittedly.

But why? It's because search is really frickin' hard to get right, and expensive to get good at.

Remember that Google started as a search company, and they became king because they got really good at it, and it was their only product (at the time, anyway!)

The easiest type of search is "full text" search. It matches words exactly based on what you type in. For example if you search lemmy it would match posts that include the word lemmy but depending on how the content was indexed, might not match lemmy.world, lemmy.ca, lemmyverse, etc.

From there you start adding complexity like supporting AND and OR. You support partial matches (lem returns posts containing lemmy and lemmings).

Add more logic to remove stop words and articles like a, the, etc.

Put in some sorting logic to rank stuff higher (what's your algo? Recency? Votes? etc.)

That's just the tip of the iceberg... this problem domain is so vast that entire companies have been built around just providing searching as a service (e.g. Algolia), and it isn't cheap!

[–] [email protected] 6 points 2 days ago (7 children)

Very interesting article! I have immense respect for [email protected], he was one of the first people I found on the fediverse, and it's no wonder why, he's revered quite highly by others as being a generous and kind admin.

I do want to point out one thing, and that is that Mastodon has some design decisions that make it rather resource and storage intensive.

There are oodles of lighter software out there, some with even more features than Mastodon, and some with less. For example, snac.bsd.cafe (https://snac.bsd.cafe/) runs on Snac, which is fast as hell.

I am going to guess that a not insignificant portion of Jerry's bill is caching assets. Mastodon likes to save everything it encounters, videos, images, avatars, everything... forever (though I imagine this is customisable). Most likely the assets are viewed a handful of times in one day and never seen again... but you'll pay to store it forever!

[–] [email protected] 2 points 2 days ago

Thanks! It's something that I personally feel is more performant and future proof for other important things like private discussions (which Mastodon also doesn't support natively yet — mention spamming doesn't count.)

[–] [email protected] 23 points 3 days ago (3 children)

Sure, check out my post about it here:

https://community.nodebb.org/topic/18844/backfilling-conversations-two-major-approaches

There are steps being taken in the right direction.

[–] [email protected] 34 points 3 days ago (5 children)

Lemmy and lots of other software use a fediverse extension called 1b12 to keep everything in sync.

In a nutshell it means Lemmy communities can follow other communities, and they keep each other in sync. The same applies for other types of communities, like PieFed communities, Mbin magazines, NodeBB categories, etc.

Mastodon doesn't have a concept of community or categories, so they don't support this kind of synchronization.

[–] [email protected] 8 points 4 days ago

There's NodeBB if you want a forum/BBS style UX for the threadiverse!

[–] [email protected] 4 points 1 week ago

For what it's worth your blog does show up fine in NodeBB as well. Perhaps you are missing the @context property and so Mastodon is refusing to parse it?

[–] [email protected] 2 points 1 week ago

[email protected] not directly, but there was a session at FediForum on Thursday that discussed the website and next steps for updating it. It's been stagnant for quite awhile but [email protected] and [email protected] finally have write access to the repo and control of the domain.

[–] [email protected] 4 points 1 week ago

[email protected]

beep beep boop boop boop boop beep... EEEEEEEEEEeeeeeeee awwwwwww ka-dong ka-dong da kshhhhhhhhhhhhhhHHHHHHHHHHHHHHHHHHHHHHHHHH

eerie silence

[–] [email protected] 4 points 1 week ago (2 children)

you can still have it with NodeBB!

26
submitted 2 weeks ago* (last edited 2 weeks ago) by [email protected] to c/[email protected]
 

1000009207.png

Speed run through the fediverse baby!

 

1000008047.png

1000008048.jpg

0
NodeBB 4.1.0 (community.nodebb.org)
submitted 3 months ago* (last edited 3 months ago) by [email protected] to c/[email protected]
 

We just released version 4.1.0 of NodeBB. Here are the latest features you can now take advantage of!

As an aside, for the first time in a long while, both @baris and I are working on the same codebase again. Up until version 4 was released, I'd been working on the activitypub branch and periodically merging in the latest changes from develop. It's nice to be home! :house_with_garden:


Improved federation of Group actors :left_speech_bubble:

We've improved the activity synchronization for followed group actors. Local updates/likes/etc. are now federated outward by the category in addition to those from remote users. Thanks to @[email protected] and @freamon who worked with me on debugging this one.

Mentions and Emoji now federating out in source.content :wave:

Emoji and mentions have been sent out to followers since v4, but that wasn't reflected in the raw markdown content that we also send along. That has been remediated now, and this change improves nodebb-to-nodebb federation.

Video object type now parseable :tv:

NodeBB is now able to ingest Peertube Video objects, and render then in a topic just like other pieces of content. Thanks @[email protected] for prodding me to get this sorted out!

 

If you have problems upgrading to v4.0.0, you can ask for help here.

 

Tonight I set aside some time to listen to @[email protected] on @[email protected]'s DotSocial podcast.

A lot a lot a lot of what John says mirrors the very same potential that many ActivityPub devs see as well. There are far too many points in that podcast that made me nod my head in agreement (and wish I was a third guest too!), but there was one that was incredibly timely:

Mike: ... you've been thinking about actually embedding the whole article in the ActivityPub post, which is a mind-blowing thing... it's not a link to something else... the whole article is in the post. John: Yes, this is something that makes perfect sense but is somehow completely new, which is weird... Mike: You can have formatted text... images? video? John: ActivityPub is fairly agnostic, you could in theory shove almost anything into it. The question is what is the client on the other side prepared to receive? Do they have some way to display it? John: If we get platforms in the ActivityPub network to start innovating with content types, it might cause those things to be adopted and it might drive the standard and what it is possible to display

Emphasis mine.

John, Mike, this is almost word-for-word exactly what the Forum and Threaded Discussions working group has been working towards! The main problem is we need buy-in from implementers to push this forward.

We can do this, we can send richer HTML across the protocol in such a way that all those things you two mentioned — in-line images, embedded videos, tables, etc. — can all show up as intended by the sender.

We've got commitment from (but not limited to) representatives from NodeBB, Discourse, and WordPress, and having Ghost and Flipboard sign on would help push this forward just that much more.

Let's do this, let me get you caught up with the state of the protocol re: the Article object type. Let's chat (but publicly, since I can't receive DMs here on NodeBB).

 

I'm happy to announce that I have tagged the latest commit in the activitypub branch as v4.0.0-alpha. That designation means (mostly symbolically) that we have moved past the "proof-of-concept" stage of ActivityPub research and development, and into the alpha phase.

This release has been a long time in coming. Work on the ActivityPub integration back in late 2023, although work accelerated around February of this year. The initial idea was to create a proof-of-concept build of NodeBB that could communicate with other fediverse apps, and federate local content outwards for other applications to consume.

As it turns out, it is difficult to temper your expectations when using a protocol with implementations that expect richer compatibility than one can provide! It seemed like a disservice to only offer a minimal subset of expected features, and so we started a deeper integration into ActivityPub with the aims of providing full user-to-user following, notifications, and two-way communication.

In the interim, FediForum happened, causing us to once again re-evaluate our short-to-medium term plans. Devs from NodeBB and Discourse, along with many other interested parties, formed the SWICG Forum and Threaded Discussions Task Force, which aims to promote the use and broader acceptance of threaded discussions as a modality of communication, as opposed to the expected "microblogging" format.

What this release contains

The alpha build contains a fully-capable ActivityPub server instance, including:

  • Two-way follow relationships between local and remote users
  • Two-way communication with fediverse content
  • A dedicated page (/world) to view remote content that is not organized into local categories
  • Categories followable from the fediverse (via FEP 1b12)
  • Integration with local flagging tools (reports sent to originating server)
  • Server-wide domain blocks (allow/deny list capability)

What this release does not contain

  • Support for emoji (images are federated out, which are sometimes stripped)
  • Support for non-public notes, as NodeBB does not currently have the facility to maintain or display them. Research on this problem is ongoing.

Roadmap

Now that the alpha has been tagged and released, I will be making our working roadmap public → you can take a look at it here

I will be starting a new backlog/roadmap for beta items, and existing backlogged items will be carried over.

Final Thoughts

We wouldn't have even thought to implement ActivityPub if it were not for the funding granted to us by the NLNet foundation. They allowed us the runway to pursue the necessary R&D work, and we're pleased that everything has been pointing positively so far!

This entire time, it has been particularly satisfying to continually see the integration working on this instance (the NodeBB support forum). Expanding the reach of NodeBB beyond the confines of the "local" mindset and into the "global fediverse" mindset has been daunting, but is well worth the price of admission.

I'm happy to also say that now that we've proceeded to the alpha stage, it signifies a commitment toward a beta phase, then an RC, and then towards the release of NodeBB v4. ActivityPub has legs, and we're invested in making it work!

view more: next ›