[frameworks-kuserfeedback] [Bug 425050] I see you're already losing users' trust over this... Here are some suggestions.
https://bugs.kde.org/show_bug.cgi?id=425050 --- Comment #4 from Someone Concerned --- (5) Fair point. (7) Done: https://bugs.kde.org/show_bug.cgi?id=425114 (8) The point of adding an option to review data *before* it's submitted is to increase perceived trustworthiness of KUserFeedback, not to provide any actual protection. Perception != reality, especially when it comes to super-distrustful people whom you've alienated... We need such people more than ever now. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kuserfeedback] [Bug 425114] Always show the "View previously submitted data..." link
https://bugs.kde.org/show_bug.cgi?id=425114 --- Comment #1 from Someone Concerned --- It should also be shown when the slider is in "Disabled" position. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kuserfeedback] [Bug 425114] New: Always show the "View previously submitted data..." link
https://bugs.kde.org/show_bug.cgi?id=425114 Bug ID: 425114 Summary: Always show the "View previously submitted data..." link Product: frameworks-kuserfeedback Version: unspecified Platform: unspecified OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: Telemetry Provider Assignee: vkra...@kde.org Reporter: lq1prs+2rm8s1mam7fmjxo0...@sharklasers.com Target Milestone: --- This will make it immediately clear that it's possible to do so even before the first feedback report is sent. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kuserfeedback] [Bug 418981] Violation of KDE Software Privacy Policy
https://bugs.kde.org/show_bug.cgi?id=418981 Someone Concerned changed: What|Removed |Added CC||lq1prs+2rm8s1mam7fmjxo0ka2@ ||sharklasers.com --- Comment #12 from Someone Concerned --- "The policy is meant to be about data shared with KDE, ie. data actually sent to the telemetry server, not about what applications do locally. If that is unclear anywhere in the wording we can certainly improve/clarify that." You can improve the config files instead by counting down instead of up and naming the fields appropriately: ApplicationTimeUntilEncouragement=... ApplicationStartCountUntilEncouragement=... When either of the fields reaches zero, display the encouragement and replace both fields with: EncouragementShown=true Or even better yet, don't use timed encouragements and simply display them at first start (like Firefox and Atom do). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kuserfeedback] [Bug 425050] I see you're already losing users' trust over this... Here are some suggestions.
https://bugs.kde.org/show_bug.cgi?id=425050 Someone Concerned changed: What|Removed |Added Resolution|NOT A BUG |--- Status|RESOLVED|REPORTED --- Comment #2 from Someone Concerned --- I found the original post in the Internet Archive (https://bit.ly/33xZguw), and yeah, somebody found the notification timer, got a tad too suspicious, and jumped to premature conclusions... There's an interesting quote in there though: "[...] No one can resist once they have their fingers in the cookie jar. [...] We'll just be the frogs being brought up to a slow boil. We know this tune, have seen this show many times before. There's always a plan. The time for naivety on this has passed, years ago." You might be tempted to dismiss this person as overly distrustful, but such distrustfullness is actually an extremely healthy attitude to have in this day and age. Look around! Governments and corporations plan to enslave us, exploit us, they dream of replacing us with machines or turning us into mindless cyborg drones! This is secular damnation. We must defend our privacy, remain ever vigilant, and, most important of all, keep dissent and resistance possible. Please don't alienate distrustful people, listen to them instead. (5) "I have tried replacing kuserfeedback with a dummy package on Arch Linux. Plasma simply freezes during startup." "[...] allow us to nuke this thing from orbit." "[...] it's just one little "oopsie" away from behind transmitted wholesale to KDE." - that's what the split library proposal aims to address concerns like this - allow users to remove the code responsible for data logging and transmission from their computers without breaking applications. (6) "there are internal names, changing them will not change anything" - except that these names are a grade A bad rumor material... (7) Nice! The "View previously submitted data..." link should probably be simply disabled rather than hidden in order to make it immediately clear that you'll be able to do so. (8) I meant like manual crash reports. Once a report is generated, a "User Feedback" system tray icon should appear, and the user should be able to click it, review the report, and then either send it or cancel it. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kuserfeedback] [Bug 425050] New: I see you're already losing users' trust over this... Here are some suggestions.
https://bugs.kde.org/show_bug.cgi?id=425050 Bug ID: 425050 Summary: I see you're already losing users' trust over this... Here are some suggestions. Product: frameworks-kuserfeedback Version: unspecified Platform: unspecified OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: Telemetry Provider Assignee: vkra...@kde.org Reporter: lq1prs+2rm8s1mam7fmjxo0...@sharklasers.com Target Milestone: --- See for instance: - Why is kuserfeedback telemetry a required package ? (https://bbs.archlinux.org/viewtopic.php?id=252844) - KDE Plasma "kuserfeedback" collecting telemetry data even when disabled (https://www.reddit.com/r/kde/comments/f7ojg9/kde_plasma_kuserfeedback_collecting_telemetry/) - KDE Is Censoring Users Reporting Spyware in KDE (https://www.phoronix.com/forums/forum/phoronix/general-discussion/1176049-kde-is-censoring-users-reporting-spyware-in-kde) Here are my suggestions: - Don't censor users, duh... Censorship will only make it worse. - To address the perception of telemetry being mandatory, simply use two shared libraries: an interface library with only pure virtual interfaces, and an optional dynamically-loaded implementation library. This way, users can simply remove the implementation library to ensure that the code for logging and sending telemetry data is physically not present on their computers. - Make it clear that, when user feedback is disabled, usage time and startup count are only used to display delayed notifications by counting backwards instead of forwards and naming the configuration keys appropriately: ApplicationTimeUntilEncouragement = ... ApplicationStartCountUntilEncouragement = ... - For additional transparency, add an option to log every report that's been sent and allow users to review *actual telemetry data* straight from the *application's user feedback configuration dialog*. Field names should ideally be translated into the user's native language. - Even better, add an option to disable automatic reports. This way, users will be able to review telemetry report *before* they get sent and cancel them if they somehow happen to contain personal information. Sure, most people will quickly get tired of reviewing everything, and either re-enable automatic reports or turn user feedback off entirely, but the very fact that such an option exists will *tremendously* increase perceived trustworthiness of KUserFeedback. -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 425023] Report hardware anti-features
https://bugs.kde.org/show_bug.cgi?id=425023 --- Comment #1 from Someone Concerned --- Information can be sourced from we the people if needed, of course, see https://bugs.kde.org/show_bug.cgi?id=424577#c3 -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 425023] New: Report hardware anti-features
https://bugs.kde.org/show_bug.cgi?id=425023 Bug ID: 425023 Summary: Report hardware anti-features Product: kinfocenter Version: unspecified Platform: unspecified OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: System Information Assignee: plasma-b...@kde.org Reporter: lq1prs+2rm8s1mam7fmjxo0...@sharklasers.com CC: sit...@kde.org Target Milestone: --- Please report hardware anti-features such as: - Proprietary Drivers - Proprietary Firmware - Intel Management Engine - AMD Platform Security Processor Proprietary Drivers === That's proprietary code (with potenial backdoors of course) often running at the highest level of privilege. Recommend open-source alternatives if available. Proprietary Firmware Same as proprietary drivers, but potentially running with fewer privileges. Intel Management Engine === Essentially a proprietary second OS (again with potenial backdoors of course) running beside the main OS on its own CPU, running even when the computer is turned off (as long as the motherboard is receiving power), with full access to RAM and the network. More information: https://en.wikipedia.org/wiki/Intel_Management_Engine and https://itsfoss.com/fact-intel-minix-case/ AMD Platform Security Processor === Similar to the Intel Management Engine. More information: https://en.wikipedia.org/wiki/AMD_Platform_Security_Processor -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 424994] Warn about insufficient package security
https://bugs.kde.org/show_bug.cgi?id=424994 --- Comment #3 from Someone Concerned --- > I don't think KDE hosting a crowdsourced repository is an ethical plan Staying silent all while humankind plunges deeper and deeper into secular damnation with every passing day sounds even less ethical to me. We need strong information security for everyone to keep dissent and resistance possible. See: https://bugs.kde.org/show_bug.cgi?id=424577#c6 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 424577] Show anti-features in app descriptions
https://bugs.kde.org/show_bug.cgi?id=424577 --- Comment #6 from Someone Concerned --- > I don't think it's [...] ethical to do this in KDE On the contrary, it's one of the most ethical and courageous projects KDE can start. See, governments and corporations plan to enslave us, exploit us for everything we're worth, and eventually either replace us with machines outright or use bio-engineering to take away our free will. This is **secular damnation**. I don't know what else to call it. Thus, we must keep dissent and resistance possible, lest we lose everything. In today's world, neither is possible without strong privacy and information security being available to everyone, and, as we all know it, raising awareness is the necessary first step to solving any widespread issue. Besides, you can always just transfer the project to FSF, FreeDesktop.org, or some other organization that's perceived as being more impartial... > You seem pretty passionate about the idea; maybe you can work on it yourself > in a cross-desktop manner? Perhaps under the umbrella of the Free Software > Foundation or FreeDesktop.org? Unfortunately, I can't do it since I'm not a member of either of those organizations... -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 424994] Warn about insufficient package security
https://bugs.kde.org/show_bug.cgi?id=424994 --- Comment #1 from Someone Concerned --- Information can be sourced from we the people as described here: https://bugs.kde.org/show_bug.cgi?id=424577#c3 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 424577] Show anti-features in app descriptions
https://bugs.kde.org/show_bug.cgi?id=424577
Someone Concerned changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO |REPORTED
--- Comment #3 from Someone Concerned
---
Well, the "this software is proprietary" anti-feature can be easily determined
from the license. I couldn't find where to check for the rest of them though.
So let's source the information externally from we the people. Here's an idea:
1) Create a repository on https://gitlab.com or https://invent.kde.org.
2) Invite people via blogs, Reddit, etc. to contribute files like this:
{
package_names: [
"firefox",
"firefox-esr",
"firefox-developer-edition",
"org.mozilla.firefox"
],
exclude: [
{ "distribution": "debian" }
],
anti_features: [
"tracking"
]
}
3) Use these files in Discover to report anti-features. Add a "Report an Error"
link leading to a repository's wiki page.
Yes, using an external source like this would mean both false positives and
false negatives, but this hasn't stopped the likes of uBlock Origin, not to
mention movie review sites...
--
You are receiving this mail because:
You are watching all bug changes.
