The article could use a link to upgrade walk-through

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

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

1. Click the feeds
2. Click my feeds
3. Click the one I want to check
4. Repeat for the next one
5. And next one
6. …

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

Watch tags from mastodon, even if no community was pinged. “Tag as community” so to speak

One vote action for all cross-post posts

FWIW, in my feeds that is on the same level as it was for some time now

I swear, this guy is all over the place. I’m very curious as what he will end up

Oooh. Can’t wait to test this out

Then how would they sell access in a deniable way?

Uh

https://en.m.wiktionary.org/wiki/-mancy#English

Ah. Yeah, nuke it from orbit. Since this was RAT, so it had local execution powers and the attackers knew exactly which distro they are targetting, they could have used some security vulnerability to get root and even replace the kernel in worst case. Hopefully not microcode insertion, so hardware could be ok

But then, it wasn’t an attack on an existing package. So the question is how many people did actually download those

Ah, you mean for fediverse to work as an LDAP?

My point is Let’s imagine we have a board on some instance. You use your account on another instance to ask the owner of the board to give you access to the board. The contents of the board are, IMO in most cases of such boards, “members only”. So any changes happening inside should not be sent out to federating instances. Otherwise, privacy of such boards would be at the mercy of privacy of other instances. If restricted changes were sent out, technically speaking, any server it federates to can choose to show that content to everyone. Which means you won’t be able to access the contents via any other instance. Apart from the logging in part, you will still need to go to the instance hosting the board. Unless it would be for publicly accessible boards only, like codeberg issues. That use-case could work