Better to create your own instance then.
It’s about reducing risk not eradicating it and there’s a huge difference in risk in being targeted for legal action due to hosting c/piracy (via caching/mirroring) than from a single piracy post in c/hellokitty.
Yeah I agree re opaque policies as if someone can get suspended for this, it would be nice if it was easy to find a policy regarding it. Thanks for your response.
Can you or Laurence link me to the policy saying one can’t have both a paid and unpaid app? Or are you asserting Google didn’t follow their own policy in this regard?
Linking a message saying that someone was temporarily suspended doesn’t sway me especially when I see apps on the store that have both paid and free versions of their apps like the app I linked earlier. If they and others can do it, why can’t the dev for Sync?
Now if someone could share a link to a policy document by Google saying “You cannot have both a paid version and an unpaid version of an app on the play store” then I would be very happy to be corrected here and I will happily adapt my stance to support that. (Seriously, I don’t mind being corrected – I’d just prefer something official from Google.)
And so it’s a deal breaker for me. And while I never used Sync for Reddit, I am thankful to all the app creators for helping the community often out of pocket and/or while being severely underpaid for years. And I hope this dev will do well financially with other users who have loyalty or different priorities than I concerning privacy and transparency.
I appreciate your response and I agree. And likewise nothing wrong with the dev making money and fans supporting that too. (I’ve seen complaints of some people who think all Lemmy apps should be free…and I feel that’s very entitled demanding someone else’s time and effort for free, but they too can just use free apps.)
Sure and if the dev goes back on that we have no recourse to get a refund from Google or for Google to take any action towards the dev since the dev can just show we agreed to our data being collected/used regardless of whether we paid or not.
Cool. It’s great that you did this.
However, my concern is there are no guarantees it wouldn’t change and there would be no recourse for Google to give us a refund since from Google’s standpoint we gave permission for the app to track our data regardless of whether we paid or not.
Yeah I was going to try the app based on all they hype but I noped out based on the trackers and that you have to accept all those permissions regardless if you pay. A dev saying they won’t use the data of paid users – that isn’t the kind of thing I would expect to be enforceable when legally you’ve already signed permissions for the data to be collected/used.
Just because it was done like this before does not mean it’s a good or transparent practice. I can appreciate though that those who used and loved Sync for Reddit may not care.
I have not used Sync for Reddit however but upon hearing about how much people love it, I wanted to give this app a try. My main point is it’s not transparent unless their is a separate app for the paid version that lays out the permissions.
A post doesn’t matter to me if I legally agree for that data to be collected as a requirement for installing the app.
I didn’t find anything against having both a paid app and a free app in the Google’s Policy Center.
While you can’t have two apps called the same thing, e.g., both apps called ‘your app name’, you can have one app called ‘your app name’ and another app called ‘your app name pro’.
I found advice going back years saying one just needs to create a separate project like this. And here is the most recent source I found saying the same thing and it goes further and lists apps that are on the store with both paid and free versions. I also did my own search and found this example: My Lightning Tracker & Alerts is free and My Lightning Tracker Pro is a paid app.
And regardless the dev saying they won’t use the data from paid users – that doesn’t matter to me when legally by using the app I signed away permission for that data to be collected.
Based on this source the issue has been fixed but the instance owners need to update to the latest version of Lemmy (v 0.18) which has the fix.
To see what version your Lemmy instance is on, scroll down to the bottom. E.g., I’m on Lemmy.World which is not on v 0.18 yet.
This is a known issue that has been fixed in Lemmy version 0.18. However some instances are still not updated to that newest version. Once your instance owner updates to version 0.18 this should no longer happen to you. Source
Good that you mentioned that. Personally, I think it’s a fair trade off for Logseq’s functionality.
Here are some links that discuss this including some scripts
You know how you can breathe out warm/humid air to help clean eyeglasses? Dragons can do that but it’s much hotter and it’s fire.
I switched from Tiddlywiki to Logseq 3-4 months ago and LOVE Logseq.
Part of the reason I didn’t like Tiddlywiki was it kept everything in a single html file (including embedded images – eww) which made it annoying to move information around. (Note there is an option to run your own server which gives you extra flexibility, but I wasn’t interested in doing that.)
With Logseq, it’s separate markdown file per journal entry / wiki page. I like the addons that are available as well as the queries, e.g., {{query (todo doing)}} displays my do now tasks on my journal page.
Here’s a Beginner’s Guide on how to use LogSeq: YouTube video by Keep Productive
Both of you rock. I love Lemmy. :)
I’ve been using Logseq for 3-4 months now and I love it. It takes a bit of getting used too, e.g., using the journal, but one can also use it as only a wiki if they prefer.
For me, I tend to do a mix of both. For information I want more organized, I’ll update the specific page and otherwise I use the daily journal.
I also really appreciate the queries and addons.
Here’s an excellent in-depth guide for beginners on getting started with Logseq. YouTube Video by Keep Productive channel is here
I break the spaghetti into 3 pieces before cooking it as then it’s much easier to deal with. :)