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.
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...