

But, whichever command I put in
autostart.sh
will run as if I run in terminal with the&
sign. E.g:dunst &
to run in the background.
Well, only if it’s one single command, if you have multiple commands inside of the script, they will still run sequentially (the next command will only run after the previous one completely closes) unless you add &
to them as well.
The difference is that dwm itself will not have to wait for the autostart.sh
to complete before launching itself (thanks to it being run in the background with &
)
However, autostart_blocking.sh
(which isn’t run with a &
) will stop dwm from fully launching until the script completes… I guess this is useful if you need certain things to be set up before dwm actually starts… but it would potentially add a delay on dwm startup.
It does not have to be something mandatory…
I mean, there could be some form of “metacommunities”, something like being able to group multiple communities together in a “view” that shows them to you visually as if they were a single community despite being separated. Bonus points if everyone can make their own custom groupings (but others can subscribe to them… so there can be some community-managed groupings).
In theory you could have multiple “metacommunities” for the same topic still… but at least they could be sharing the same posts if they share communities. I feel grouping like this would be helpful because small communities feel even smaller when they are split.
I think reddit has something similar to that, multireddits or something I think they are called.