Obvious things I don’t see mentioned:
history | grep whatever (or other useful piping), though your older commands are forgotten eventually. You can mess with the values of HISTSIZE and HISTFILESIZE environment variables in your system.Context just before that quote:
As we understand it, this contract clearly states that the terms do not intend to contradict any rights to copy, modify, redistribute and/or reinstall the software as many times and as many places as the customer likes (see §1.4). Additionally, though, the contract indicates that if the customer engages in these activities, that Red Hat reserves the right to cancel that contract and make no further contracts with the customer for support and update services.
This is rich, don’t know how many people are aware of that.
I was looking into Arch-based environment and wondered if there is an option for a scenario where you don’t have to update for a few weeks for example, because you don’t use that computer or whatever. But you still want to try the Arch configurability and wiki docs for it.
From what you’re saying, it’s still actually all rolling release. From my (flawed? correct me) understanding it is different from Ubuntu or Fedora, where you can update an outdated OS state and it isn’t supposed to break. Possibly barring changing OS versions.
Agreed, I think hosting it on localhost not exposed to the internet is a great idea if this satisfies your needs for now. Do double-check the docs for your system if firewall disallows web server connections by default (Manjaro and Endeavour are based on Arch which is supposed to have good wiki).
Then, if you want to go online, you can export the database and put it into a server install.
Yeah, I’m not disagreeing there is a convenience and ease angle, but I think there’s a middle ground where we have 2-3 communities for major interests with somewhat different vibes or approaches, so there is a topic reason for them coexisting. This already happens in the old school forums ecosystem. Fediverse’s advantage here is that you hopefully don’t need separate accounts.
Re: loss of knowledge, if some instance/community does a purge, I’m assuming the old posts are still there, at the very least on the instances that used to be federated with them. I suppose it would be a nice to have a feature for admins for “freezing” their public backups of mirrored communities when they get defederated. It’s not that different of a scenario from standard Internet drama, we just have to handle this nicely.
I agree with other people that the right to defederate is to be respected. If we rely on one hub community somewhere to congregate, this is only kinda decentralization. At the very least the central hubs shouldn’t be on instances that are too defederation-happy.
On the other hand, I see the argument that many users means more difficult moderation, where defederation might be a band-aid as they say on beehaw. The question is if they have too ambitious moderation goals to handle being a central hub, and maybe indeed it would be better for their communities to be sort of internal to them.
May be worth keeping some local communities in that case, which can also serve as sort of backup for wider community from other small servers. For example, if there is “Knitting” on a big instance, you can consider creating something more specific like “Knitting full RGB sweaters” on your smaller instance. Then there is a basis for sustained discussion there, and more people can come if something breaks. I have some ideas for comms like this that I’ll maybe come around to creating.
I don’t think we need to keep full centralization be-where-everyone-is mentality here. Or maybe be where everyone is, but don’t make it the only place where you talk with people.
There is [email protected] and [email protected].
I mean… “who needs features in 2022” is onto something. But I use both, for various Nvidia and laziness related reasons, and have a dim idea what they do inside, as probably most flamers on the topic.