- 4 Posts
- 24 Comments
suff@piefed.socialto PieFed Meta@piefed.social•Any recommendations for a mobile app?Deutsch2·4 days agoPlease share your experiences
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.
Thanks. I still think we have a lack of content problem, rather than a lack of mods problem. The community downvotes context-misfits, mods remove meaningless stuff, filters hide threads, … If we don’t have the mod tools to tackle microblogs, we will need them anyway when piefed gets more popular.
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”?
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.
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.
It’s not two views on the same content. They keep microblogs and threads separated.
Do I miss something?
- Communities are called “Magazines” on mbin. Magazines contain posts from the threadiverse (lemmy, etc.), not microblogger posts.
- “Microblog” in the header menu links to a TL of microblog posts, not posts from the threadiverse.
- From the comment section below threadiverse posts, you can upvote, reply and boost (a threadiverse comment to your microblogging TL), that’s okay but why distinguish them in the first place?
- You can passively view (and rank) the microblog TL filtered by tag. That feels redundant.
I want hashtags treated like communities.
Just checked on fedia.io . It’s not what I meant.
Thanks but I don’t think I want a microblogging-UI within piefed but a translation into communities.
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.
You could moderate piefed hashtag-communities.
nr microblog forumverse 060 boost approve
suff@piefed.socialto PieFed Meta@piefed.social•What's the best way to report the abusive modon piefed.social?English11·28 days agoHow about you founding [email protected] ?
suff@piefed.socialto PieFed Meta@piefed.social•[Feature request] Upload image by pasting from clipboardEnglish3·29 days agoI want that, too.
I heard they prefer feature requests on https://codeberg.org/rimu/pyfedi/issues
suff@piefed.socialOPto PieFed Meta@piefed.social•"Create Post" in Vertical Mode (Mobile)English3·1 month agoI made it float with this css tweak:
#side_pane div:nth-child(1) div div.row.mb-2 div:nth-child(1) a { position: fixed; top: 17vh; left: 77vw; max-width: 60pt; overflow: hidden; z-index: 999; box-shadow: 5pt 5pt 30pt black; }
I tweaked the tiling like this:
#masonry { margin-left: -5px; padding-top: 5px; } #masonry .column { padding-right: 3pt; } #masonry .item .masonry_info .row .col-8 p * { white-space: normal; line-height: 100%; } #masonry .item .masonry_info .voting_buttons_masonry { display: block; } #masonry .item .masonry_info .row .col .upvote_button { display: block; margin: 0 auto } #masonry .item .masonry_info { position: relative; bottom: inherit; }
cool you can customize the css
I imagine something like https://reddit.musicplayer.io/ Essentially a video queue looking like a TV