For me, I have to do ‘url: “http://pictrs:8080/” ‘ instead of 127.0.0.1 in the config.hjson file
I also had to remove the tls line in the email section to get mine to work. I think this release is a lot more finicky regarding the config file, but it’s little idiosyncrasies don’t appear to be documented.
That being said, Lemmy is still kind of broken because I can’t even see this thread on my own instance and only see one comment on this one…
Lemmy does not have upvote and downvote buttons
But… it does?
I can’t even see this post on my selfhosted instance, so that’s fun.
With regard to #6, you apparently have to search for the URL of the Kbin magazine (e.g. https://kbin.social/m/RedditMigration) and then you can subscribe as normal from that point on.
And yeah, the discovery and comments thing is super annoying. There will be completely different conversations based on where you’re viewing the post, which kind of kills the idea of all these instances federating in the first place.
That being said, it appears to be feeds coming from lemmy.world and lemmy.ml that have the majority of the problems with comment/post sync. Unfortunately that’s the selfhosted community.
running scripts like these make me nervous, especially on the host machine of a hypervisor. My (limited) understanding is that a compromised host system compromises all the VMs and containers within. Seems like you could be one command away from letting an attacker into everything.
As a few people have pointed out, Kavita is a solid one. I ultimately used it because it saves your spot in the book server-side instead of with the browser (like calibre-web) so you can pick up where you left off on different devices.
Also has a pretty good PWA for your phone if you want to read on there.
Because federation is broken between many servers, I have to use multiple accounts to see all the communities.
I’m doing my part!