hi, so there is something interesting. I tested everything possible yesterday. Everything worked until the loading of the "known network" timeline.
I optimize my postgresql config with…
hmm so resources technically, there should actually be no problems. I'm using an AMD Ryzen 9 5950X 16-core processor. The VM has 16GB RAM of which hardly anything is used and an ssd nvme is…
i change the logging now from info to debug..
the diagnostic output looks okay i think.. https://envs.sh/hcw.txt
and this is the pleroma log: https://envs.sh/hcq.log
okay, thanks.. i just updated and ran the task. here is the output:
@floatingghost can we reopen the issue please?
now after ~1 hour, the home timeline has re-operated itself in the pleroma-fe and shows something again. The "known network" tab continues to throw errors.
what i notice is that my home timeline with mastodon-fe loads but not with the pleroma-fe. the "know network" tab load nothing in both fe's.
i try now this way:
-
su pleroma -s $SHELL -lc "./bin/pleroma_ctl config dump_to_file pleroma instance instance.json" -
modify the instance.json and remove the rewrite_policy tuple
-…
it is a pity that there is no interest in explaining to people who do not understand your system how it works.
i would like to, but the question is how
i try this:
-
su pleroma -s $SHELL -lc "./bin/pleroma_ctl config dump_to_file pleroma instance instance.json" -
modify the instance.json and remove the rewrite_policy tuple
-
su pleroma…
i see no way to change this entry.
looks like it is in the DB. but no idea how to change it..
$ su pleroma -s $SHELL -lc "./bin/pleroma_ctl config dump"