You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
As a developer, it would be very nice to have ultra-fine analytics on how people use Caligula. This could be stuff like:
usage frequency
keystrokes
types of files written
crashes
performance
system information
and so on.
Describe the solution you'd like
I'll self-host a server to collect analytics and crash logs. TODO: find an appropriate server
The data will be recorded regardless of opt-in or opt-out status, but it will not be transmitted unless the user consents. Look, the log files are already detailed enough to reconstruct this info, so you might as well just record it in a more structured format anyways.
Guaranteeing enthusiastic and informed consent
The config file that I will Eventually(tm) make can have a blanket opt-in flag.
When the program crashes, it will ask for consent to transmit logs and user analytics.
I may have a "🥺👉👈 pls send me data to impwove da sewvice owo" checkbox that the user can check during setup. That may be a bit too aggressive though.
Furthermore, there will be a little blurb I'll prepare that describes what kinds of information gets transmitted when you send that out.
Describe alternatives you've considered
I categorically refuse to make these analytics opt-out or forced. Since this is a specialized piece of software meant to cater to a small category of people, the small amount of data collected from the few who would opt-in (and some friends I badger into opting-in too) would be more than enough data to work off of.
The text was updated successfully, but these errors were encountered:
ifd3f
added
feature
New feature to add to the program itself. Does not include refactors or platform support.
ux
Things directly related to how the program is used
labels
Nov 27, 2024
Is your feature request related to a problem? Please describe.
As a developer, it would be very nice to have ultra-fine analytics on how people use Caligula. This could be stuff like:
and so on.
Describe the solution you'd like
I'll self-host a server to collect analytics and crash logs. TODO: find an appropriate server
The data will be recorded regardless of opt-in or opt-out status, but it will not be transmitted unless the user consents. Look, the log files are already detailed enough to reconstruct this info, so you might as well just record it in a more structured format anyways.
Guaranteeing enthusiastic and informed consent
Furthermore, there will be a little blurb I'll prepare that describes what kinds of information gets transmitted when you send that out.
Describe alternatives you've considered
I categorically refuse to make these analytics opt-out or forced. Since this is a specialized piece of software meant to cater to a small category of people, the small amount of data collected from the few who would opt-in (and some friends I badger into opting-in too) would be more than enough data to work off of.
The text was updated successfully, but these errors were encountered: