I dig ham radio, telephones, computers, privacy, vim, and my dog.

Socials: https://keyoxide.org/CD3D0D7F0C9E5FB8

  • 51 Posts
  • 105 Comments
Joined 2 years ago
cake
Cake day: June 12th, 2023

help-circle



  • So of course one of the issues with moving to a new object store is old local images are orphaned. I’m looking at how we might be able to migrate at least our user/community images, but this may be how it is for now. You may have to reupload your profile photo/banner. I’ll work on updating the community images. Honestly, this will help us save on storage in the future.














  • From experience: I can say that a topic instance such as ours is easier to moderate due to the fact that it’s narrowly focused and the number of posts here are small in comparison to a general instance such as lemmy.world or sh.itjust.works. I moderate the users that join pretty fiercely so I know that the only people that join/post from here are interested in amateur radio in some fashion. I also think we are a bit lucky in how we moderate with the fact that hams tend to moderate themselves and others already through their acts and experiences with radio communications in general (thanks everyone!).

    I sorta see how you can view niche instances as having sub-subreddits. Generally though, every community out there is just a subreddit and you can subscribe and post to any of them, even though some communities do share the same topics (there are lots of other amateur radio communities out there).

    I definitely like seeing people creating communities here, as long as they are amateur radio focused (see rule 5). I also would suggest making an account on a general lemmy instance as well, in case you would like to make a more generalized community. I think it’s probably just good practice on any federated application to create accounts on multiple instances.

    73!





  • If I remember right, there was a pretty big change in how pictrs(photo management) worked with lemmy after 0.19.3. There were a few breaking changes and Postgres updates that would take an instance down for a while as well. Not sure if that’s the reason why but it made my instance stay on 0.19.3 for longer than it should have.