count0 @ count0 @lemmy.dbzer0.com

Posts

0

Comments

24

Joined

2 yr. ago

It allows me to run any weird combination of applications I feel I need on a given day, (fairly) easily integrating basically all open source packages with a custom/local overlay and have those managed as part of the system just like everything else.

"Should 'we' do?"

Nothing. If people and/or communities coming in through Threads are engaging in good faith, cool, more nice folks to have a community with. People/communities engaging in bad faith get blocked/defederated as is already common practice (and seems to be working outstandingly already, looking at average quality of posts and discourse "here" as compared to the "big platforms").

When Meta/Threads is hosting communities I like to see/be a part of, I'll figure out how to subscribe/integrate those. Besides that, they're free and welcome to run echo chambers in their own instances and communities, I don't see how any of that would ever show up on my feed.

I guess this will already have been said, but nonetheless:

I like the feeling of community as it is right now in the Fediverse very much.

Most of me hopes that it will not successfully federate with Meta, ever; or if it "must", in a way that will be mostly irrelevant to me (communities I wouldn't subscribe to in the first place, anyway).

I don't see how that, in turn, would give Meta any control over the parts of the Fediverse that I care about. If they want to join and contribute in good faith, fine. If not, also fine. Why should it change anything for Fediverse "centered" communities?

I never cared about size or majority, but about quality of content and discourse. And I find that in those points, the current Fediverse much outshines anything else I've seen (Facebook, Twitter, Reddit, ...) in the last decade or so.

For someone coming from NeXTStep (BSD based), having worked with SCO, various BSD and mostly Linux for the last 20 years, the worst thing about systemd is documentation that's easily accessible/readable for people used to a traditional init system.

"How do I get it to do special use case X" was a basically unanswerable question when it got dragged into the mainstream (for reasons I can very well understand - the reasons for the dragging, that is, the bad docs, not so much).

Maybe that's improved in the mean time - I wouldn't know, I had to figure it out back then and now I know its lingo when searching and such.