Afternoon everyone,

I wanted to go over a few points related to pricing, stats and the roadmap


Pricing

  1. Sync for Lemmy is completely free with ads (the same as Sync for Reddit)

  2. You can remove ads in the account picker or drawer for a one time fee of ~$20

  3. Sync Ultra also removes ads but it’s not required

  4. I’ll be working on regional prices over the coming weeks


There are now 24k installed users up from 100 the previous day!

I’m going to be spending the next few days going through all of the comments / messages and fixing any crashes.

As always thanks for the support and hope you’re liking Sync!

Lj

Edit: testing edit

  • @jmeel
    link
    English
    41 year ago

    Hey. Great work putting the app up so soon. There seems to be an issue every once in a while with loading content regardless of the origin Lemmy server. I’m guessing something on the API end. Is the API host specific instances (i.e. is the host of the sync API currently just the Lemmy.world instance)?

    • godless
      link
      English
      31 year ago

      Every instance is hosting the API for their own users, and unfortunately lemmy.world has plenty of outages recently.

      The way Lemmy works is that when you have an account with lemmy.world and subscribe to a community hosted on lemm.ee (for example), the lemm.ee server copies the content over to lemmy.world, and you see it all “locally”. Hence a lemmy.world server outage reflects what you see with your lemmy.world account. Local communities will always be shown “as local” of course, so a server outage then means it’s completely offline for the time being.

      A quick fix would be to sign up with a smaller instance and subscribe to the communities from there (including the ones on lemmy.world), in that case even if lemmy.world is offline, you would be able to see and interact with their cached copies on the target instance. I’ve made an account with infosec.pub for that purpose.

      • @jmeel
        link
        English
        41 year ago

        Ah, I figured there’s that kind of problem. I was wondering if the alternative was that the server running the API were a different process or potentially machine from the one running the web front.