Notices by Julian Lam (devnull@crag.social), page 2

@evan was this on the sending end or receiving end?

On the sending end, I wasn't aware that "bcc" and"bto" needed special handling that required delivery to their individual inboxes.

I was planning to send activities addressed in "bcc" and "bto" to the shared inbox, same as "to" and "cc".

@evan morning! Did you figure it out overnight?

My implementation hasn't gotten as far as handling audience delivery yet (it all just goes into a single public bucket, yay proof-of-concept software!), but what problems re: bcc and bto were you referring to?

@evan I think it's because @davew has 10,000 characters to work with on his instance 😆

I also feel constrained by this tiny box, but I don't often have much to say.

@evan you can't? I thought that was explicitly how shared inboxes worked.

In your example my understanding is domain2 would receive a single activity, and parcel out the activity to the other users internally as appropriate. How that's actually handled by domain2 is out of scope of the spec.

A potential complication could arise if you're saving a serialzied representation of that object for validation, in which case it wouldn't pass as you have to remove bcc from the object...

Today at 16:19, a @nodebb instance sent its first "Note" into the fediverse 😄

Baby steps!!

#fedidev #ActivityPub #nodebbActivityPub

@J12t #ActivityPub test case:

Claim: An instance should reject an unsigned POST request to a user inbox

Expected: The Activity should not be appended to the user inbox.

Observed: The application promptly crashed because it did not anticipate the possibility of someone sending in an unsigned POST to the inbox... but also the activity was not added to the inbox.

Result: ✅

😆

/cc @helge

@evan @daniel @evanprodromou unrelatedly, #nodebb sanitizes post content too, and I did think it was a little weird that #ActivityPub sends HTML back and forth.

It all boils down to never trusting user input (that includes input from servers acting as intermediaries!)

I would rather see #markdown passed around, but that's just me 😊

One quick question about instance keys... I have private and public keys generated for individual user actors in my implementation, and that works when attempting to access resources from an instance with AUTHORIZED_FETCH enabled. If I need to retrieve content without a local user context, would I be making the call with an "instance level" public key/signature?

That was my interpretation, but would appreciate confirmation 😃

#activitypub #fedidev #nodebbActivityPub

@wedistribute loving how there are podcasts about the #socialweb happening. Consuming it all (all two of them that I've discovered) like there's no tomorrow!

@evan ah, I just mean that things like Notes translate well to (NodeBB) posts, likes are likes, authors are users, etc.

It means I don't have to jump through major hoops to make #NodeBB federate.

Last week, I started my initial forays into retrieving and parsing remote content from the #fediverse. As expected much of the data structures are identical to #ActivityPub but named and organized differently, so there's a lot of bits and pieces that need connecting.

Nevertheless, it's thrilling to see remote content on a local instance!

Next week: federating likes, perhaps? 😃

#nodebbActivityPub #forums #fedidev

@expert @luceos @leroy @nodebb @multiverseofbadness you're right! My apologies 🙂

I must've thought it was more like Facebook

@leroy you are not wrong. What @evan, @cwebber, et al. realized was that at their core, all social networking software follows nearly identical tenets. People follow other people, people like things, people respond to things with comments, etc.

At the end of the day, we're looking at different implementations to access the same #SocialWeb, different but amazing all in their own way.

@expert @luceos @nodebb @multiverseofbadness

#Lemmy and #kbin are technically forum softwares as well, even though their design lineage shares more in common with Reddit than traditional forum software. I assume you're already familiar with them 😅

Lastly, while @luceos and I have not spoken at length about integration, it is in our best interest to work together so that compatibility between our platforms is strong. All thanks to #ActivityPub!

@leroy @nodebb @multiverseofbadness

Hi @leroy, here's the state of forum software in the #fediverse

@nodebb currently is pursuing full federation (user actors, category actors, possibly topic actors) with an alpha by end of Q1.

#Discourse has a third party dev working on their implementation but it is currently category actors only (broadcasting content out to the fediverse)

#Flarum has received funding but I am not aware of any implementation yet. However @luceos would be the person to ask about this.

@multiverseofbadness

@tchambers: "if you prove yourself to be a good actor in the #fediverse, you're welcomed — and may a thousand business models bloom"

Well said!

https://pca.st/episode/528a5ea7-f4f3-4d86-874a-a78f15e34387?t=2464

(Actually I'm not sure if I attributed the quote to the correct person, I might've been @mike 😅)

Today, like most of this week, I worked on follow logic for @nodebb (#nodebbActivityPub) — follow/unfollow is now working, and now I can browse follow lists from remote accounts too!

Now listening to @mike's #DotSocial #podcast featuring @tchambers!

https://pca.st/episode/528a5ea7-f4f3-4d86-874a-a78f15e34387

Does there exist a brief write-up of how content is federated out? Do different #ActivityPub implementors federate content differently? (@stesnac suggests so!)

Here's my head-canon at present... when a note is created, the note is sent to all followers. If users are mentioned, the note is also sent to those users' inboxes.

If a note is addressed to the public collection, do it just get blasted to all known instances' inboxes?

https://snac.bsd.cafe/stesnac/p/1704724939.498114

#fedidev

@bignose, @evan is not the appropriate person to address for implementation details, he is one of the co-authors of the #ActivityPub spec, but has (probably?) little to do with #Mastodon development...

However you are correct that this is a case of export being implemented but import not... even by Mastodon itself. There may be other software that can read it, but I am not personally aware of any.