鴉PieFedFediverse-wide Interoperability
TL;DR I want Mastodon hashtags treated like communities.
Given the following homomorphism (morphism, analogy) between microblogs like Mastodon and the forumverse:
| nr | microblog | forumverse |
|---|---|---|
| 010 | subscribe to hashtags | subscribe to communities |
| 020 | include particular hashtags in their posts | (cross-)post in particular communities |
| 025 | include particular hashtags in their posts | include particular hashtags in their posts |
| 030 | list posts of a hashtag | view a community |
| 040 | comment a post | comment a post |
| 050 | star a post | upvote a post |
| 060 | boost into TL | approve "into" community |
I wish to interact with microbloggers as a piefed user. Piefed could render microblog posts that contain a hashtag as a community post within a "community" named by this particular hashtag. Also, microblog accounts could be viewed like a regular user in piefed.
Pros: Lemmy posts and communities are visible and subscriptable in Mastodon already. Piefed should complete this connectivity.
Cons: Re-interpreting microblog posts as forum entries could lead to some misunderstandings which again lead to defederation. But I cannot think of any.
Edits: Added 060, 025, TL;DR
Edit: There appears to be a Mastodon integration being planned.
If you want to do this, Mbin can be a temporary solution, they support both format already
Thanks but I don't think I want a microblogging-UI within piefed but a translation into communities.
That's how mbin does it, by tying tags to communities
Just checked on fedia.io . It's not what I meant.
From your post...
That is literally how mbin does it!
@suff@piefed.social , have you tried looking at a specific community?
https://fedia.io/m/photography has the two views: microblogs and threads
It's not two views on the same content. They keep microblogs and threads separated.
Do I miss something?
I want hashtags treated like communities.
I see you mentioned on another comment that "boost" would be "approved", but that then implies that mods of the communities have to approve every single post using that hashtag?
Counterpoint: there are very limited resources, and a whole bunch of very basic and foundational things that do not work even within the Threadiverse (e.g. links that don't go to where they were aimed at, bc of the new way that comments load and then the direct link to a specific comment does not continue forward anymore past that; also searching, extra stuff in the API for 3rd party apps, etc.), as PieFed is so new. And those take on increasing importance now that lemm.ee has shut down and so many communities migrated over. People are waiting patiently for those fixes.
Therefore, while expanding to go beyond the Threadiverse into increasingly more niche use cases is desirable, the opportunity cost of slowing down the aforementioned fixes may outweigh them.
We can have it all, but not all at once, and not for free, with the current low level of funding support.
I don't require it ASAP. But including this feature in present/early considerations could be important. Approving this request could lead to a greater dev community aswell.
I'm not in a position to make suggestions, but I think requesting something and prioritization are two different things. So I think it's fine? I mean we have a bunch of feature requests open in the issue tracker shooting for big things...
I don’t think this can work. A threadiverse community is contained by its instance and rules. A hashtag pulls everything from every instance so it’ll get unwieldy fast.
From the threadiverse point of view it would make a bit more sense to be able to follow specific microblog accounts as a way to get that content here. Microblogs (or at least Mastodon) are doing their own equivalent of that already because they can interface with threadiverse communities natively (they’re presented as groups that boost every new post & comment).
You could moderate piefed hashtag-communities.
Hey suff@piefed.social let me share what I've been working on here at ActivityPub.Space
We're running NodeBB, which is a federated forum software that interacts with the threadiverse/forumverse natively, but also interacts with microblogs.
Anything coming from microblogs has no community attached, so we throw it all into a single "uncategorized" bucket.
This forum I am posting from is about ActivityPub, so I set up an auto-categorization rule so that posts using #ActivityPub get slotted into general — sounds good, right? Except that tag has a fairly low SNR. Every day I have to remove 4 or 5 posts that are at most tangential to ActivityPub at all.
I ran into similar issues with #climbing for a rock climbing forum. People use #climbing when they climb rocks... but also trees, fences, buildings, etc...
So it can work, it just needs some ongoing curation. Essentially what I am trying to say is... hashtags are fine, but its usage is nowhere near consistent enough to use in a global context like you are saying.
Such flawed community picking while posting is one advantage of using microblogging. You can post regardless of having found the correct category or forum. Good point.. maybe.
On the other hand, maybe you should rename your community from "climbing" to "rockclimbing"?
I do really wish there was a single platform that could interact in all the same ways as all the other platforms, with a single account. That'd be really nice.
I personally don't think it makes sense. They are fundamentally different, in one you subscribe to a user in the other one to a community. If it was a centralized platform then it might work with the mapping, but how will my instance find all the mastodon instances which posted a hashtag?
There are ways but they have so much overhead that I don't think it's worth it. Why not use mastodon for it?
Until recently, there was this thing called a.gup.pe for Mastodon, which was like a PieFed community except with no moderation, like a hashtag. PieFed could treat a.gup.pe groups as communities and there was posts inside, etc. It worked, technically.
But all the a.gup.pe groups (except one) were full of weird crap & spam. People post sooo much trash on Mastodon.
The only way to use Mastodon, really, is to follow good people and unfollow those who post crap. As soon as you break that model and follow an unmoderated hashtag, it falls apart.
You can block accounts in communities, can't you? Also, there's a downvote button. Mastodon posts could start with 0 instead of 1. Unvoted posts could be deleted automatically after time.
Due to noise ratio and code overhead, I'm ready to accept the least compromise: A small, filtering Mastodon client integrated in the mod tools UI where mods can easily import toots into the community.