• 3 Posts
  • 80 Comments
Joined 3 years ago
cake
Cake day: June 11th, 2023

help-circle









  • I thinki founda small issue though I can’t be sure it’s related to the corrupted data and yesterdays maintenance. It looks like a few of my community subscriptions are a little broken? FYI I’m using voyager on IOS.

    As the server catches up, more content from the last two months has been showing up in my home feed. Fantastic! I decided that I don’t want to subscribe to !dailygames@lemmy.zip anymore. So I looked at my subscriptions, selected dailygames, tapped the “3 dots” menu button, and tried to unsubscribe. However, I subscribed again rather unsubscribed. I then looked at my subscribers again and saw daily games listed twice. Then, I unsubscribed using the same method but this only removed one instance of my subscription to dailygames.

    So the content showed up in my home feed. My subscription was seemingly working fine. But I couldn’t unsubscribe as the subscription was not recognized in some contexts. It really feels like some crossed data in the database. Thankfully, this is a very small issue.

    I have at least one more subscription that’s showing the same problem.

    Lastly, I did find a solution. Voyager’s list of community subscriptions allows you to swipe on a specific community to unsubscribe from it. That worked just fine!







  • That basic idea is roughly how compression works in general. Think zip, tar, etc. files. Identify snippets of highly used byte sequences and create a “map of where each sequence is used. These methods work great on simple types of data like text files where there’s a lot of repetition. Photos have a lot more randomness and tend not to compress as well. At least not so simply.

    You could apply the same methods to multiple image files but I think you’ll run into the same challenge. They won’t compress very well. So you’d have to come up with a more nuanced strategy. It’s a fascinating idea that’s worth exploring. But you’re definitely in the realm of advanced algorithms, file formats, and storage devices.

    That’s apparently my long response for “the other responses are right”



  • A complicated plugin ecosystem (e.g. Jenkins) makes for a terrible use experience. It’s annoying to configure a bunch of config files. Managing dependencies can be a complete nightmare. these problems also complicate your ci/cd.

    So I’ll offer a slightly different answer. I prefer a single file instead of splitting up the config. And I’ll use OpenTelemetry as an excellent example of why. the plugins are compiled right into the app binary. This offers a ton of advantages, including a great reason to merge all of your app configs in a single file.

    This really only works well if you have a good app though.