Sorry, I couldn't resist :D
INeedMana
joined 1 month ago
I understand that this proposal is to have separate voting controls per cross-posted community, not automatically upvote all
I'm not sure why people want that
There often are multiple communities for the same thing. Rust for example. The result is that in some interest fields posts are often cross-posted to a bunch of same communities. With Piefed displaying all comments from all cross-posts, there is little need to switch between communities. But if the post is good, I feel it should receive a vote not only in the community that just happened to be on top of the feed
I already have a bunch of my own feeds. My issue is that from UX perspective those work best when I have them opened as separate tabs on laptop. In PWA there are no tabs. And in the feeds dropdown not all are shown, only a handful. So in order to check what's new in a bunch of feeds (too big to get notification about all that's happening in those) in PWA, I have to
- Click the feeds
- Click my feeds
- Click the one I want to check
- Repeat for the next one
- And next one
- ...
Being able to switch between my feeds like between "subscribed" and "local" would be much better
Yes, I think that would be an acceptable implementation
No, like having my feeds instead of "subscribed", "local", "popular". Ideally with a way to mark which feeds I want on the list
When I view a tag on my mastodon account, I see posts from people I don't follow because someone from my instance is following that person?
Cross-posting text-only posts
I think it's a messy idea, you will be getting conflicts on files already present in the system. You've been warned ;)
With that out of the way, I guess just download the image and start from https://wiki.archlinux.org/title/Installation_guide#Installation
UI: instead of Lemmy-like main view, offer a list of selected feeds as tabs in the main view
From the link in the OP
Both the original Markdown (MD) based version of logseq and the DB version use an internal database when you are using the app. The difference is that, in the MD version, the files are always canonical. In the DB version, while you will can export to markdown files, the database version is always canonical.
But maybe that's temporary, in the older link from my comment nothing suggests this is the design goal
view more: next ›
My 2 ¢
Topics, AFAIK, same as feeds are managed. Someone needs to add a community to it for it to start popping up in the topic. That relies on moderation and probably would work better with time the other way round - if it was the community saying which topic it belongs to and moderation would only inspect connections flagged by reports
But then, most of communities come from Lemmy, where there is no concept of topics and tags. In which case, it would have to be possible for someone from outside of community to connect it to a topic. A vote maybe?
But then, that would open up possibility of malicious connections
IMO in a way, topics is like tags for communities. A post can have a tag, you can display posts with given tag in a community, but there are no strict rules about how tags connect with communities.
But then, topics should not be created based on most popular tags. I can imagine, for example, privacy community having a lot of Microsoft tags