Yes, the rough patch on November. We didn't win any matches in that period, which is still crazy to think about.
We are going to spend big this summer. Reinders, Gibbs-White, Cherki are a few players we are chasing. Grealish, Bernardo, Stones are rumored to be on the way out. At least, that looks like the plan, we can still end up not getting any target and the squad stays the same.
Calling third place finish a "tough season" is really flattering. The standard is way too high.
We go again next season
It works! I can see piefed.social community with Thunder. Try going here !solus@piefed.social (just an example).
I just moved my account and (tiny) communities I moderate to piefed.social . The migration is pretty seamless, all post got copied over to new community.
My experience (under 24h)has been OK so far. There is many quirks that came with it tho, I am still digging all the feature available.
Maybe consider a different software altogether?
I just moved my account and two communities I moderated to piefed.social . The migration is pretty seamless, all post on previous community got copied to new one. So far, I see that piefed has pretty good moderation and better filtering tool than lemmy.
That said I will follow stardewvalley community wherever it is. Cheers!
I just did the same for !solus@lemm.ee and !aerynos@lemm.ee. Now both of them are on piefed.social. Pretty seamless!
test
This is an old comment but I am replying anyway.
The idea of statelessness is not limiting user configuration but giving user a sane default config. Many software doesn't work without a config file, the idea is that a software should ship a default (vendored) configuration that make the software can be used as is. The default config is stored at vendored directory. This default config file then should be able overriden by user own config.
For example: Alex needs program "A" for work but program "A" needs a config file to even launch. Ideally the program "A" should ship a default config file to vendored directory in
/usr. If Alex needs to modify the configuration to fit his needs, now he can do that by copying the default configuration in/usrdirectory to either/etc(system wide) or/.local/config(per-user). Alex now can modify the config file as he pleases. Now, in case some modification Alex made make program "A" doesn't work, he can just nuke his own config file and program "A" will work again because of the default config is there as a fallback.Good news is many program is already following this schema of configuration files but there are also many low-level program that does not (
bash,pam, etc).