cross-posted from: https://lemmy.world/post/15187023

cross-posted from: https://lemmy.world/post/15187023

cross-posted from: https://lemmy.world/post/15187027

cross-posted from: https://lemmy.world/post/15187023

cross-posted from: https://lemmy.world/post/15187023

cross-posted from: https://lemmy.world/post/12094120

There’s an enormous and largely invisible campaign to use fraudulent notices under the US Digital Millennium Copyright Act to remove critical articles from the internet. We don’t know who is running the campaign, but we do know it’s facilitated by Google’s amazingly trustworthy approach to DMCA complaints made by companies that don’t exist.

cross-posted from: https://lemmy.world/post/12094120

There’s an enormous and largely invisible campaign to use fraudulent notices under the US Digital Millennium Copyright Act to remove critical articles from the internet. We don’t know who is running the campaign, but we do know it’s facilitated by Google’s amazingly trustworthy approach to DMCA complaints made by companies that don’t exist.

There’s an enormous and largely invisible campaign to use fraudulent notices under the US Digital Millennium Copyright Act to remove critical articles from the internet. We don’t know who is running the campaign, but we do know it’s facilitated by Google’s amazingly trustworthy approach to DMCA complaints made by companies that don’t exist.

If I create a OSS app with analytics to detect & log crashes with feature use, is it a bad practice? I think analytics is really helpful in finding:-

• which features are worth developing &
• which bugs needs to be solved first.

Edit...

Things Collected

• IP Address for use ping (for country)
• All crashes with IP
• Feature use with IP Crashes are store for upto 6 months to solve bug but rest are collected and delete after 3 months

It is opt-out but user are informed about it during first / install time. To disable analytics Settings --> Privacy

I want to know right way to introduce analytics in OSS