Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
veganism.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Veganism Social is a welcoming space on the internet for vegans to connect and engage with the broader decentralized social media community.

Administered by:

Server stats:

265
active users

veganism.social: AboutStatusProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.4.0-alpha.5

#threadiverse

2 posts2 participants1 post today
Public
Jeff Sikes

Federated flair for PieFed communities and users is here. Think of them similar to hashtags that follow these objects around. It gives you a sense of the user's specific interest in a topic, or a way to filter a community to posts about a specific flair. Your community flair can be associated to a specific color.

join.piefed.social/2025/05/10/

PieFed · How PieFed federates "flair" on posts and comments - PieFed
More from piefedadmin
#PieFed#ActivityPub#Threadiverse
Public
julian

What would cross-posting between instances look like in ActivityPub?

Following up on this question I asked back in late March, I wanted to continue thinking about how one would handle cross-posting between categories/communities, given that there isn't current consensus on it, and especially given that NodeBB—as of v4.3.0—can now see and browse remote categories.

From that original topic, we can distil the following:

  1. Both PieFed and Mbin do not natively handle cross-posts, a new entity is made with the crucial bits (link, text, possibly title) copied over and changed if needed, sometimes a "cross-posted from..." helper text is prepended.
  2. There are legitimate concerns that a cross-post might not succeed depending on privilege settings on the receiving end, so a pre-flight check (or explicit rejection) of some kind might be required.
  3. Cross-posting can be done by the original author, or another user.

So were an FEP to be written, we'd center it around the following assumptions:

  • "A user (which may or may not be the object author) is sharing an object to additional audiences"
  • We would use the existing Announce(Object) model
  • We would not use Announce(Activity) because it is not the original object creation that is being announced, but the object itself, to a new audience.
  • Some form of Reject handling would be required for cases where the cross-post is not allowed
  • How the receiver handles the activity is out-of-scope of the FEP. It could be that the original object is contained within multiple categories/communities, or a duplicate object could be created — implementor's choice.

This is very similar to an existing announce/boost/reshare, except that instead of addressing the activity to followers list you are addressing it to a group actor's inbox.

Some additional questions:

  1. Is there desire from PieFed/Lemmy/Mbin for supporting incoming (and possibly outgoing) federation of cross-posting?
  2. What exactly happens currently if a Group actor receives an Announce(Object)? My guess is nothing, currently, but let me know otherwise :smile:
  3. Would this allow you to accept cross-posts from other AP applications without needing to refactor any existing code?
  4. Duplicating the object would mean the discussion is split between objects. The ideal implementation would be the same object present in multiple categories/communities. Is there desire for this in the threadiverse?

@rimu@piefed.social @andrew_s@piefed.social @melroy@kbin.melroy.org @bentigorlich@gehirneimer.de @nutomic@lemmy.ml @angusmcleod@mastodon.social

community.nodebb.org/post/1044

NodeBB Community · How do PieFed/Lemmy/Mbin handle cross-posting?tl;dr — how do PieFed/Lemmy/Mbin handle cross-posting? Currently, when a NodeBB admin moves a topic from the uncategorized pseudo-category into a local categ...
#threadiverse#crosspost#activitypub
Public
julian

tl;dr — how do PieFed/Lemmy/Mbin handle cross-posting?

Currently, when a NodeBB admin moves a topic from the uncategorized pseudo-category into a local category, we federate out an as:Announce, people typically think of that as a "boost" or "share".

That worked fine when the entirety of the category list was your local categories plus the "uncategorized" pseudo-category. However, now that NodeBB is moving towards supporting remote categories (via group actors), this UX makes less sense. We wouldn't want to "move" a topic out of the category it is supposed to be in, just for visibility to other local users. Additionally, topic moving was limited to administrators, and from the get-go we knew it would eventually cause issues because people other than admins would want to share topics to other local users.

This is where the "cross-post" functionality comes in, which is entirely new to NodeBB. I don't think this is new to other AP-enabled threaded discussion software. The idea would be that if a new topic comes in, whether it's uncategorized or not, any user could "cross-post" that topic to a local category, where it would be visible to other users on that instance. On the ActivityPub side, we would then federate out an as:Announce as we already do.

Is this what PieFed/Lemmy/Mbin already do, if they support cross-posting? What other alternative solutions would there be to this problem?

cc @rimu@mastodon.nzoss.nz @andrew_s@piefed.social @nutomic@lemmy.ml @bentigorlich@wehavecookies.social

#threadiverse#piefed#lemmy
Replied in thread
Public
soaproot

@Prozak @mdione If I put this URL in the search bar in Mastodon I see the post. You should be able to boost, favorite, etc, from there.

(exactly what #threadiverse posts behave like when federated to microblogging systems like Mastodon can turn into a deeper rabbit hole, but basic things like in the previous paragraph work as far as I know).

Replied to shellsharks
Public
db0

@shellsharks I crossposted you over to lemmy (lemmy.dbzer0.com/post/37326743) but do consider pinging an #threadiverse comm like @fediverse as your first mention and your note will also be crossposted to that comm (with the first sentence becoming the article title). Then all the interactions from that comm will also appear as your mastodon comments.

lemmy.dbzer0.comScroll duo - Divisions by zeroWelcome to volumen duo of Scrolls, a newsletter for sharing cool stuff from the IndieWeb, Fediverse & Cybersecurity worlds[…]
Public *
db0

@BeAware I haven't had (almost) any such issues with #fediseer, but my primary audience has been #lemmy and the #threadiverse instead of microblogging. There's surprisingly different norms that have been organically reached in mastodon over the past decade which are fairly alien outside it.

It honestly feels more like a small group of people trying to futilely hold back the Eternal September through scolding and pile-ons.

#EternalSeptember
Replied in thread
Public
Jupiter Rowland
@Eleanore Duncan That's kind of difficult, actually.

Technically speaking, there is Friendica which was created in 2010 as a Facebook alternative (better than Facebook rather than an outright Facebook clone), and there are Hubzilla and (streams), both descendants of Friendica created by Friendica's creator. They're quite powerful, (streams) more than Friendica and Hubzilla even more than (streams), and they've got everything you need for social networking.

I've made a series of tables that compare these three with one another and with Mastodon. You can find them here.

But if you say, "app," I suppose you mean, "dedicated native mobile phone app." This is the first hindrance. Native specialised phone apps are only available for Friendica and then only for Android and Sailfish OS. The only iOS Friendica app is a closed beta; it exists, but you have to join its beta test program instead of being able to load it from the App Store easy-peasy.

Technically, you can use Friendica with some apps made for Mastodon. But you'll only have those features that Mastodon has, too. You won't see threaded conversations. You won't have text formatting. You won't have groups. You won't be able to post pictures. You won't have any access to any configuration. And so forth. You'll only have the absolute, bare-bone basics.

Otherwise, and for Hubzilla and (streams) generally, there's no way around the Web interface (browser, PWA).

As for community building, Friendica, Hubzilla and (streams) not only support groups, but they have groups/forums, optionally even private ones. Organisational presentation is possible, too. All three have blogging-level support of text formatting in their posts all the way to embedding an unlimited number of images right in the middle of a post. So a group could make an introduction post with headlines and bullet-point lists and tables and pictures and all the shebang and pin it at the top for all (permitted) visitors to see. Hubzilla even supports simple webpages which could be used for presentation. Hubzilla's own website is a webpage on a Hubzilla channel.

"Easy and clear," that's the issue here. Friendica has quite a bit of a learning curve. (streams) has an even steeper learning curve. Hubzilla has the steepest learning curve of all three. None of them has the UI/UX of something created by a Silicon Valley start-up from $50,000,000 of venture capital.

Ironically, Hubzilla is the one with the best user documentation. But what I mean is not the user documentation built into the hubs, but its complete re-write by a user that's intended to be built into Hubzilla itself one day and replace the old documentation. If you want to peruse it, you'll have to be told by an experience Hubzilla user that it exists, and where you can find it. Still, Hubzilla is highly complex with quite a bit of pitfalls and the worst UX of the three.

Friendica has a wiki, but it mostly covers how-tos for certain things instead of being a full-blown user manual.

(streams)' built-in help system is gradually being rebuilt from zero, but in the style of a technical specification again. And it's very incomplete.

Still, you will need some kind of documentation to get started with all three, ideally plus how-tos for Facebook refugees on how to get started and then do Facebook things. You can't use on either of the three what you've learned from Facebook. They do have everything you need as a Facebook refugee, but it looks different, it feels different, it works differently.

For example, if you're on either of the three, and you're looking for the place where you can create a new group/forum, you can look forever in vain. Unlike on Facebook, groups/forums are not an additional feature of their own. They're accounts (Friendica)/channels (Hubzilla, (streams)) like your user account/channel, but with special settings. This alone makes many Facebook users scream out that this feature is completely unuseable, simply because it isn't what they expect it to be.

In addition, if you run a Friendica group on the same node as your personal account, you have to log out and back in again to administer or moderate the group and to get gack to your account. But nobody tells you to have your group on another node than your personal account.

On Hubzilla and (streams), it's the opposite: It's better to not only have a group or forum on the same instance as your personal channel, but on the same account. You can have multiple channels, multiple fully separate identities on the same account because your identity is fully detached from your account. If you have your personal channel and your forum channel on the same account, you can jump back and forth between the two. But this is something that practically doesn't exist outside of Hubzilla and (streams), and so, nobody will tell you about this feature.

Even if you can wrap your mind around all this, you still aren't over the hump. Especially not on Hubzilla and (streams). On Hubzilla, you can have a restricted or private group/forum. But you have to dive into the permission settings of your forum channel, a place where you're being warned that you have to act carefully, and set the corresponding permissions accordingly by hand. On (streams), there's less to configure and no warning; instead, there are not one, but four types of forums. But neither the Web interface nor the documentation tells you what's what, and what does what.

Another idea, but much less like Facebook, would be Mbin. Technically, Mbin is an alternative to Reddit and Hacker News and kind of feels like Reddit, UI-wise. But it also offers personal microblogging instead of being limited to only group discussions, and it's much more compatible with the rest of the Fediverse.

There are two caveats again. One, most Mbin users are former Redditors. This means that Mbin's culture = Reddit's culture, including, but not limited to dank maymays, shitposts all over the place and potentially also power-tripping mods (if you want to join existing Mbin magazines (= subreddits) rather than starting new ones). However, I guess that Mbin, on average, is not as hostile and xenophobic towards the rest of the Fediverse as large parts of Lemmy are.

Two, again, there's no iPhone app that works with Mbin. For Android, there's Interstellar. For iOS, there's only the Web interface.

CC: @PaulaToThePeople

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Facebook #FacebookAlternative #FacebookGroups #Friendica #Hubzilla #Streams #(streams) #Threadiverse #Mbin
hub.netzgemeinde.euMastodon vs Facebook alternativesComparison between Mastodon, Friendica, Hubzilla and (streams)
#mbin
Public
shellsharks

For anyone new (or "old") to the Fediverse that is interested in #infosec / #cybersecurity, we have a #Lemmy community (similar to Reddit) that you can join. You can join directly on infosec.pub or even directly interact with threads and replies from Mastodon / other fedi software!

Here is an example of a weekly "mentorship" thread we do on the c/cybersecurity community: https://infosec.pub/post/22645039

Infosec.pub is run by @jerry (of infosec.exchange) and as such is very stable and well-run. It is also a pretty active and lively instance with a wide variety of communities, both "technical" and not!

I wrote some stuff up on the #threadiverse (which originally meant platforms of the Fediverse that we're Reddit-esque) here if you're interested in reading - https://shellsharks.com/threadiversal-travel

Reddit doesn't deserve you, come to the Threadiverse!

infosec.pubMentorship Monday - Discussions for career and learning! - Infosec.PubWeekly thread for any and all career, learning and general guidance questions. Thinking of taking a training or going for a cert? Wondering how to level up your career? Wondering what NOT to do? Got other questions? This is the time and place to ask!
Public
maegul

Mother fucking 2 year #lemmy cake day.

For me, lemmy was the actual start of the fediverse experience.

A reddit/forum style platform on the same protocol as Twitter style platforms that even kinda interacted with each other (first time seeing which was genuinely wonderful).

Since, I’ve always said the Fedi should do more group based things, and I stand by that. I even think Reddit/forum/group-based platforms are a better story on AP than microblogging and I’d wager they could stick around longer than the Twitter clones.

Either way, whenever I come back to the Fedi, I’m usually heading for lemmy / #threadiverse first. Reddit culture aside, I find it a much nicer way to find my people.

I hope all the best for the other platforms too… #kbin , #mbin , #piefed , #nodebb (and #friendica too)!

Public *
WeirdAlex03

My contributions to #canvas / #canvas2024:

- Lemmy.zip Logo: My headliner for this year is again the logo for #Lemmy .zip, my home instance in the #threadiverse. I chose the spot and placed the first pixels, but it was a team effort with at least 15 others contributing
- Before starting the Lemmy.zip logo, I also started the #AreciboMessage. I made the template, but the idea was from @the_dopamine_fiend and I only drew the first 3 "lines" of data, the rest was all done by others
- I wanted to do something with @theowlhouse, but didn't think of that until the second day when it was too late for something big. Instead, I just made a little mini Grom Fight #Lumity for my #TheOwlHouse rep
- With time running short, I decided to use some spare pixels in the final hour to make a ghost amogus. You'd think white-on-white wouldn't be seen, but @ArieTheFloof noticed and placed the last two pixels
- Lastly, a little mini #PerryThePlatypus from #PhineasAndFerb, because why not?

The Lemmy.zip logo as seen on Canvas 2024 A pixel art drawing of an orange mouse head, with a peach nose (the nose is actually the same color as the rest of the face on the actual logo). The top of the head is "unzipped" by a zipper running diagonally to the right eye, revealing other artwork behind. The logo is surrounded by an orange border with the text ".zip" in the lower right corner
The Arecibo Message as seen on Canvas 2024 This follows the common representation with different segments highlighted in color for distinction, as seen on i.e. Wikipedia. See https://en.wikipedia.org/wiki/Arecibo_message for a more detailed description of the message itself
The Haskell logo with a small depiction of Amity Blight and Luz Noceda holding hands underneath, as seen on Canvas 2024 The Haskell logo contains (among other elements) a Greek letter lambda (λ). The Lumity scene is placed in the negative space under the lambda, standing on another piece of art. Luz and Amity are in their dresses from Season 1 Episode 16 "Enchanting Grom Fright": Amity in a dress with black top and purple bottom, and Luz in a tuxedo with a tutu. Each of them are only 3x7 pixels so there really isn't that much detail here
My ghost amogus as seen on Canvas 2024 with the "Blank canvas overlay" enabled, changing the color of the background to reveal white pixels A close-up of the lower left corner of the Lemmy.zip logo. The normally white background color has stop been changed to a light green, revealing white pixels that have been placed by users. There is a white 4x4 pixel deception of the character from Among Us in the corner of the border, next to a Stu (a red character with a purple and red tail and purple and red horns, which was incredibly prevalent on Canvas 2024. I have no idea where the character came from)
Public
julian

There have been some scattered discussions I've seen over the past year that mention that @pfefferle@mastodon.social's WordPress ActivityPub plugin federates their blog posts out as an as:Note, and that the only reason this is done is because Mastodon only treats as:Note (and as:Question) as a first-class object and relegates anything else to a fallback handler that takes a short snippet of the content, and shows a link back to the original source, thus losing any in-app benefits (boosts, replies, etc.)

Whether this is actually true or not, I do not know. So that's why I'd like to ask Mattias — or anybody else with some context — here.

For reference:

  • as:Article: Represents any kind of multi-paragraph written work.
  • as:Note: Represents a short written work typically less than a single paragraph in length.
  • as:Page: Represents a Web Page.

I have also noticed that Lemmy, perhaps out of principle, sends out an as:Page for new generated content, and only the replies federate out as as:Note. It has unfortunately led to some assertions that Lemmy's federation is "broken", even though it is arguably not the case.

@nutomic@socialhub.activitypub.rocks, care to weigh in?

I don't even blame Mattias for opting to send everything out as as:Note.

End of the day right now it doesn't matter how Mattias or Nutomic represent their higher-level collection of data, because Mastodon is the largest implementor and neither they — nor anyone else I know of, for that matter — treat anything that's not as:Note or as:Question specially.

But that ought to change. The question is how, but this WG is not at the point where we start throwing around decrees and making up standards.

What's important to me right now is what the landscape looks like right now, and why that is the case.

N.B. The discussion here will eventually make its way to online real-time discussion at one of the future WG meetings.

#swicg#threadiverse#forums
Public
Yohan Yukiya Sese Cuneta 사요한🦣

The #CIM family of #Fediverse services:

Theme: single-letter domain name.

1: c.im — a Mastodon software instance. (#microblogging)
2: c.wtf — a Rebased+Soapbox (fork of Pleroma with Soapbox frontend) software instance. (microblogging)
3: p.lu — a PeerTube software instance. (#video hosting)
4: r.nf — a Lemmy software instance. (#threadiverse)

#ActivityPub #Lemmy #Mastodon #PeerTube #Pleroma #Rebased #Soapbox

---

Inspired by c.im/@jerry@infosec.exchange/1

Mastodon hosted on c.imC.IMC.IM is a general, mainly English-speaking Mastodon instance.
VegansExploreLive feeds
About