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.
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!
@[email protected] , 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.
I think blaze was a bit confused at what you were saying but I got it as its kinda how I would like it as well. Basically mastadon in your feed. Like you could have a setting to do it at the user level. Honestly I would sorta like the logins in the fediverse to be able to be used in other fediverse instances. That would make a lot of things easier. Like I have 3 hubert manne accounts. one kbin, one on an mbin instance, and this piefed one. If I want to look at mastadon or loops I have to make a new account. Would love to click on links and have it just accept [email protected] as a user. This would also make it where it is no longer necessary to fix links so they come up in an instance and decrease how much caching a particular instance needs to do.
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?
It would be an acceptable variant or configuration for very busy/misused hashtags. I think if many users can join the mod team, it would work well.
If you look at https://fedia.io/m/photography/microblog , there are several posts per hour. That’s not going to be doable to have mods approve all of those posts.
Mods should be able to switch from opt-out (manually remove Mastodon posts from the hashtag-community) to opt-in (manually “boost” Mastodon posts into the hashtag-community). That switch could also flip like a fuse when a threshold is reached, with an admin-configured max_toots_per_day.
The flooded mod tool could help itself with filters by min_boosts, min_stars, links, media and max_age, etc.
See this other comment about signal to noise ratio: https://piefed.social/post/1289879#comment_8099521