offen/website
2
0
Fork 0
mirror of https://github.com/offen/website.git synced 2024-12-23 05:20:21 +01:00
Code Issues Projects Releases Wiki Activity

fix opt-/opt spelling

Browse Source
This commit is contained in:
Hendrik Niefeld 2021-01-04 11:14:47 +01:00
parent 31e424c957
commit 1d9f1f938a
6 changed files with 21 additions and 21 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
homepage/content/articles/0060-milestone-4.md
View File

@ -51,7 +51,7 @@ This is why we built a downloadable demo of Offen that you can run on your local
- A demo is now populated with randomly generated usage data at start, so that users will get an idea of how an install that is already in use will look like, instead of having to generate usage data themselves beforehand.
- We added a dedicated landing page for demo users that explains them how to use the demo from both a user's and an operator's perspective.
<img class="screencast mt3 mb2" alt="Demo" src="/theme/images/offen-blog-0060-demo.gif"/>
<img class="screencast mt3 mb2" alt="Demo" src="/theme/images/offen-blog-0060-demo.gif"/>
You can try using the demo yourself by running the following snippet:
@ -65,7 +65,7 @@ Relevant PRs are: [367](https://github.com/offen/offen/pull/367), [346](https://
An ongoing part of our work on Offen is implementing features and fixes that come from our own experience with running our own Offen instance. This is why Milestone 4 contains a few UX improvements and fixes regarding the operator facing Auditorium. Among others, we improved the referrer stats, improved the mobile UX for tabular data and fixed issues with the user flow for resetting your password.
Relevant PRs are [361](https://github.com/offen/offen/pull/361), [363](https://github.com/offen/offen/pull/363), [364](https://github.com/offen/offen/pull/361https://github.com/offen/offen/pull/364),
Relevant PRs are [361](https://github.com/offen/offen/pull/361), [363](https://github.com/offen/offen/pull/363), [364](https://github.com/offen/offen/pull/361https://github.com/offen/offen/pull/364),
---
@ -122,7 +122,7 @@ describe('Consent', function () {
Now that we have a basic idea of how such a test looks like, let's add interaction and check for their immediate effects on the UI:
```jsx
it('displays a link to the Auditorium after opt in only', function () {
it('displays a link to the Auditorium after opt-in only', function () {
cy.visit('/')
cy.contains('Open Auditorium').should('not.exist')
cy.contains('Yes please').click()
@ -151,10 +151,10 @@ it('allows users to opt out and delete all of their data', function () {
cy.contains('Open Auditorium').click()
cy.url().should('include', '/auditorium/')
cy.contains('Opt out').should('exist')
cy.contains('Opt out').click()
cy.contains('Opt-out').should('exist')
cy.contains('Opt-out').click()
cy.contains('Opt out').should('not.exist')
cy.contains('Opt-out').should('not.exist')
cy.contains('Unique websites').prev('p').should('eq', '0')
})
```

2
homepage/content/articles/0080-beta.md
View File

@ -23,7 +23,7 @@ We as Offen are convinced that all these 'privacy friendly' approaches are an im
Users continue to be unaware what kind of data is collected and how it is being used. They still cannot access or delete it. This leaves them in the dark about their situation and does not help to reduce the latent distrust against web operators. A problem that GDPR also addresses explicitly under the headline 'Rights of the data subject'.
This is why we develop a fair and open web analytics tool that finally treats *operators and users as equal parties.*
Usage data is only collected after opt in. If users choose to opt in, they have full access to their data and can also delete it. The collected data is presented to the user with explanations that describe why a particular metric is relevant and what the privacy implications are.
Usage data is only collected after opt-in. If users choose to opt in, they have full access to their data and can also delete it. The collected data is presented to the user with explanations that describe why a particular metric is relevant and what the privacy implications are.
At the same time essential metrics give operators the chance to gain valuable insights. They can improve their services without violating the privacy of their users.
By the way, Offen is in beta phase now. [Please take a look and give it a try.](/try-demo/)

4
homepage/content/articles/0100-matomo.md
View File

@ -17,7 +17,7 @@ Operators interested in open and privacy friendly web analytics particularly app
### Room for improvement
Despite the general popularity, there are some problems with Matomo's decisions regarding privacy. By default, the software only offers an opt out feature for website users. This way, *consent is practically a preset.* In addition, access to usage data is not automated and therefore can be very complex and laborious for users. A common problem which the GDPR mandates explicitly under the heading ["Rights of the data subject"](https://en.wikipedia.org/wiki/General_Data_Protection_Regulation#III_Rights_of_the_data_subject){: target="_blank"}.
Despite the general popularity, there are some problems with Matomo's decisions regarding privacy. By default, the software only offers an opt-out feature for website users. This way, *consent is practically a preset.* In addition, access to usage data is not automated and therefore can be very complex and laborious for users. A common problem which the GDPR mandates explicitly under the heading ["Rights of the data subject"](https://en.wikipedia.org/wiki/General_Data_Protection_Regulation#III_Rights_of_the_data_subject){: target="_blank"}.
On the technical side, the following issues are particularly apparent. Installing Matomo can be a bit of a pain as there are many dependencies that must be pre-installed on the system. This also applies to the requirement to use a dedicated MySQL database, which makes installation even more complex. Last but not least, the tracking script that Matomo uses is extensive and therefore delays the loading of the pages considerably.
@ -27,7 +27,7 @@ On the technical side, the following issues are particularly apparent. Installin
To address the above mentioned issues we develop a fair and lightweigt web analytics tool that treats operators and users as equal parties. It is called Offen and is [available as a beta version.](https://www.offen.dev/get-started/)
*Offen's default is to NOT collect any data.* Usage data is collected after opt in only. If users choose to opt in, they have full access to their data. They can delete it any time or opt out completly.
*Offen's default is to NOT collect any data.* Usage data is collected after opt-in only. If users choose to opt in, they have full access to their data. They can delete it any time or opt out completly.
The collected data is presented to users with explanations that describe why a particular metric is relevant and what the privacy implications are. This helps to strengthen trust in operators.

16
homepage/content/articles/0120-opt-in-quality.md
View File

@ -1,4 +1,4 @@
title: Opt in for quality insights
title: Opt-in for quality insights
description: Collecting data only with user consent has a less obvious implication: the quality of insights from web analytics increases.
date: 2020-10-28
slug: opt-in-quality
@ -8,7 +8,7 @@ author: Hendrik Niefeld
must_read: True
bottom_cta: matomo
# Opt in for quality insights
# Opt-in for quality insights
### Fair web analytics
@ -18,13 +18,13 @@ Collecting data only with *user consent has a significant impact on the quality
### Analyzing our own turf
Our own homepage [offen.dev](https://www.offen.dev/), on which of course an Offen instance is installed, can be described as rather small. It currently has an average of 280 unique users after opt in and 660 verified page views per month.
Our own homepage [offen.dev](https://www.offen.dev/), on which of course an Offen instance is installed, can be described as rather small. It currently has an average of 280 unique users after opt-in and 660 verified page views per month.
We estimate our opt in rate, meaning the percentage of website users who agree to the data collection, to be about 40%. This figure is a subjective estimate and derived solely from the personal feedback of a relatively small group of test users.
We estimate our opt-in rate, meaning the percentage of website users who agree to the data collection, to be about 40%. This figure is a subjective estimate and derived solely from the personal feedback of a relatively small group of test users.
We cannot and do not want to measure the actual rate for obvious data protection reasons. What we are sure about is that it depends very much on the content offered. In our particular case, where product and presentation are so closely interwoven, it should be rather high compared to other content.
However, we do not think it really matters to know what your opt in rate exactly is. But more about this later.
However, we do not think it really matters to know what your opt-in rate exactly is. But more about this later.
### Collecting data differently
@ -56,15 +56,15 @@ Common web analytics tools try to solve this problem by blocking single traffic
### Real human users
We don't think so. An "opt in only" policy for data collection, which is necessary anyway for privacy reasons, solves the problem along the way. Even if you wanted to, the opt in banner can only be bypassed with a lot of engineering effort. This assures real human users with a very high probability. The best starting point for the optimization of your website.
We don't think so. An "opt-in only" policy for data collection, which is necessary anyway for privacy reasons, solves the problem along the way. Even if you wanted to, the opt-in banner can only be bypassed with a lot of engineering effort. This assures real human users with a very high probability. The best starting point for the optimization of your website.
Talking about these real users brings us back to the question of whether it is important to know your exact opt in rate. For an answer, consider for which users you want to optimize your website and what kind of users you want to attract.
Talking about these real users brings us back to the question of whether it is important to know your exact opt-in rate. For an answer, consider for which users you want to optimize your website and what kind of users you want to attract.
*Those who consent are most likely interested in your content.* They support you with their usage data and may therefore be willing to support you in any other way. The exact share of these users is less interesting.
### Deeper insights for optimization
Nevertheless, common web analytics tools that collect data without user consent provide at least better results than the analysis of your server logs. Yet their quality is bound to be lower compared to the results obtained with the smaller amount of data generated by opt in only data collection. This is caused by the fact that some further issues are simply not manageable without some form of consent banner.
Nevertheless, common web analytics tools that collect data without user consent provide at least better results than the analysis of your server logs. Yet their quality is bound to be lower compared to the results obtained with the smaller amount of data generated by opt-in only data collection. This is caused by the fact that some further issues are simply not manageable without some form of consent banner.
Many users are recorded even though they have visited your website with very little or no interest. Some bounce off immediately and may just have been there by mistake. Still, all these data points are included in your analytics and will give you a distorted impression. The resulting false assumptions distract you from the important users and make it difficult for you to keep the necessary focus.

4
homepage/theme/templates/base.html
View File

@ -137,14 +137,14 @@
<div class="w-100 w-50-l">
<figure class="ma0 pr3-l mb3 mb0-l">
<a href="/blog/opt-in-quality/">
<img alt="Opt in for quality insights" src="/theme/images/offen-blog-0120-opt-in-quality.jpg">
<img alt="Opt-in for quality insights" src="/theme/images/offen-blog-0120-opt-in-quality.jpg">
</a>
</figure>
</div>
<div class="w-100 w-50-l cclr-bg-yellow-mid">
<div class="pl3-l">
<h3 class="f3 normal lh-title ma0 mb2">
<a href="/blog/opt-in-quality/" class="link b dim cclr-fnt-black-mid">Opt in for quality insights</a>
<a href="/blog/opt-in-quality/" class="link b dim cclr-fnt-black-mid">Opt-in for quality insights</a>
</h3>
<p class="ma0">
Collecting data only with user consent has a less obvious implication: the quality of insights from web analytics increases. <a href="/blog/opt-in-quality/" class="link b dim cclr-fnt-black-mid">Read more</a>

4
homepage/theme/templates/index.html
View File

@ -89,7 +89,7 @@
</em>
</h2>
<p class="wx18 center ma0">
Opt in only. <i>Users must actively give their consent to data collection. All data is</i> encrypted end-to-end.
Opt-in only. <i>Users must actively give their consent to data collection. All data is</i> encrypted end-to-end.
</p>
</div>
@ -638,7 +638,7 @@
</tr>
<tr class="bg-near-white">
<td class="tl truncate pv2 pl2 pr1">Opt in only data collection</td>
<td class="tl truncate pv2 pl2 pr1">Opt-in only data collection</td>
<td class="truncate pv2 pl2 pr1">
<svg width="15" height="15" viewBox="0 0 15 15" fill="none" xmlns="http://www.w3.org/2000/svg">
<circle cx="7.5" cy="7.5" r="7.5" fill="#CCCCCC"/>