I’ve been having trouble keeping this instance up - right now, it’s a problem with proxy errors between the docker containers as well as with the Ansible scripts. It’s taking too much time to maintain. I’ll be shutting down wayfarershaven.eu per 31 October 2023.
That means that the fountainpens community here will also disappear. Anyone who would like to restart this on another instance is more than welcome to do so.
That’s unfortunate, thank you for giving it a solid try!
My primary instance is stable, and the admin is quite able. I’d consider stepping up. I definitely don’t want to be the only mod for any period of time. It’s not just the time commitment, it’s the implicit non-democratic status of the sub when one person makes all the mod calls. I’m @____@infosec.pub there, incidentally.
Edit: Went ahead and created it as a placeholder, pending any necessary further discussion or other volunteers here. !fountainpens@infosec.pub
Since content is instance-dependent, it might be nice to have a mirror on some other stable instance - not sure how to sync them so both get each others’ posts, but don’t duplicate though. This group in particular tends to have a lot of high-quality content and losing it is a blow - especially to noobs, who we actively want to be friendly and accessible to.
Is there a library for the API? Would be nice to seed a new community with some/all of the content here, if you don’t object. Not like the reddit mirror bot posting a ton of things, but for initial content. Would prefer not to lose it all.
@MidwayTheMagnificent I guess you could always archive posts and whatnot on wayback machine or archive.ph and follow the fediverse links for the full discussions? (i.e. the fediverse icon next to each comment/post).
I’ll try and archive myself as many threads as possible as well.
It sucks because I found many interesting communities on this server besides the Fountain Pen one.
Thanks @hsl for your hard work!
@____
That could work and is simpler - Might be scriptable, have to think on that. Don’t recall whether the request archive button is a GET or POST. Parsing out the links to posts and throwing away the others would be straightforward, ‘if /post/ in url’
I do know that I won’t get to it today - my work is finance-adjacent, and with a deadline in the next week, work is keeping me rather busier than usual.
@MidwayTheMagnificent There’s still some time until 31st of October I guess 😁
I just looked - six pages of posts. Might not even bother scripting, that’s not a ton of copy/paste.
@MidwayTheMagnificent I personally just finished archiving @onebag @happiness and @solotravel. Both on wayback machine and on archive.ph for redundance. I archived both post links and post links with
?scrollToComments=true. Good luck with the rest whenever you can if you start to 😁 It’s already late here for me.Hi there! Your text contains links to other Lemmy communities, here are correct links for Lemmy users: !onebag@wayfarershaven.eu, !happiness@wayfarershaven.eu, !solotravel@wayfarershaven.eu
@CommunityLinkFixer Those ones, yeah!