Jeg synes at min service var god nok til at fortjene sit eget domænenavn på internettet, men alle de gode navne, jeg kunne komme i tanke om, var optaget.
Ét af de domæner, jeg havde kig på, var wishlist.dk. Et sigende, relativt kort, globaliseringsparat domæne. På det tidspunkt så forsiden af wishlist.dk ca. sådan her ud:
Det må man ikke!
I Danmark er det ikke tilladt at oppebære registreringen af et domænenavn udelukkende med henblik på videresalg.
Derfor startede jeg en sag hos Klagenævnet for Domænenavne. Det koster 160 kr. for private, men man får pengene tilbage, hvis man vinder. Jeg dokumenterede min nye service, den nuværende brug af wishlist.dk og så skrev jeg ellers:
Jeg har lavet en gratis, ukommerciel og overvågningsfri ønskeseddelservice som alternativ til kommercielle services – der har været nogle sager i medierne for nylig om problemer med overholdelse af persondatalovgivningen for disse sider.
Siden er klar til at gå i luften, men mangler et sigende domæne. Jeg har vedhæftet et skærmbillede af den side, jeg har udviklet, som pt. ligger på https://wallnot.dk/wish/ (bilag 1).
Jeg ønsker at benytte domænet wishlist.dk (engelsk for ønskeseddel) som et sigende domæne for sidens indhold. Wishlist.dk er dog registreret. Registranten er ikke angivet som anonym i whois, men er en service, der tilbyder anonym registrering af domænenavne (Anonymize, Inc., https://anonymize.com/). Jeg har derfor ikke været i stand til at kontakte ejeren af domænet.
Wishlist.dk har ikke noget indhold, bortset fra en salgsside, der udbyder domænet til €2.500 (bilag 2). Salgssiden er drevet af https://dan.com som er en virksomhed, der – så vidt jeg kan se – udelukkende beskæftiger sig med salg af allerede registrerede domæner. På siden udbydes wishlist.dk også til €2.500 og står listet med en privat sælger (“private seller”, https://dan.com/buy-domain/wishlist.dk, bilag 3).
[…]
Jeg mener, at domænet wishlist.dk bør overdrages til mig, da jeg, da jeg allerede har udviklet en service/hjemmeside til at oprette ønskesedler, og dermed har interesse i et sigende domænenavn til min side.
Den nuværende anvendelse af domænet er i strid med god domæneskik og Lov om internetdomæner §25, stk. 2, der siger at “Registranter må ikke registrere og opretholde registreringer af domænenavne alene med videresalg eller udlejning for øje.” Den nuværende registrering oppebæres udelukkende med videresalg af domænet for øje, hvilket fremgår tydeligt da man mødes af en salgsside for en virksomhed, der udelukkende beskæftiger sig med salg af allerede registrerede domæner, når man besøger wishlist.dk. Domænet har været registreret i en lang periode muligvis af flere forskellige registranter – men har så vidt jeg kan se aldrig været anvendt til indhold med nogen form for relation til domænenavnet.
Derfor mener jeg at domænet wishlist.dk bør overdrages til mig.
Jeg indsendte klagen d. 3. juli og den 11. september kom der svar til mig. Personen bag den tidligere registrering havde ikke svaret i sagen.
Efter en behagelig og ukompliceret dialog med de flinke advokater hos Kønig Advokater, der ejede brugsretten til domænenavnet lnk.dk, har jeg fået lov til at overtage lnk.dk – og nu er en opdateret udgave af min kortlinkservice i luften.
På lnk.dk kan du lave automatisk generede korte links (tænk lnk.dk/ab0g) eller selv vælge, hvad dit korte link skal hedde (tænk lnk.dk/morten).
Som sædvanlig har jeg brugt Django til arbejdet.
I models.py definerer jeg datamodellen, lidt ekstra validering til brug i formularen til at lave korte links, og hvad jeg gerne vil se i admin-interfacet for siden:
from django.db import models
from django.utils import timezone
from django.contrib import admin
from django.core.exceptions import ValidationError
def validate_destination(destination):
if "lnk.dk/" in destination.lower():
raise ValidationError('For at undgå risiko for uendelige viderestillinger, kan du ikke tilføje korte links fra lnk.dk som destination.')
def validate_shortlink(shortlink):
if shortlink == "om":
raise ValidationError('Det korte link "om" bruger lnk.dk til at fortælle om lnk.dk. Vælg et andet selvvalgt kort link.')
elif shortlink == "administration":
raise ValidationError('Det korte link "administration" bruger lnk.dk til at administrere lnk.dk. Vælg et andet selvvalgt kort link.')
class Link(models.Model):
destination = models.URLField('Destinationslink', max_length=65535, validators=[validate_destination])
shortlink = models.SlugField('Kort link', max_length=100, unique=True, allow_unicode=True, validators=[validate_shortlink])
LINK_TYPE_CHOICES = (
('automatic', 'Automatisk'),
('manual', 'Manuelt'),
)
type = models.CharField('Type', max_length=10, choices=LINK_TYPE_CHOICES)
date = models.DateTimeField(default=timezone.now, editable=False)
class LinkAdmin(admin.ModelAdmin):
list_display = ('destination','shortlink','type','date')
list_filter = ('type', )
search_fields = ['destination']
I forms.py definerer jeg formularen, som brugeren indtaster sit lange link og evt. et selvvalgt kort link i. Jeg forsøger også at formulere nogle forståelige fejlmeddelelser:
from django.forms import ModelForm
from .models import Link
class LinkForm(ModelForm):
def __init__(self, *args, **kwargs):
super(LinkForm, self).__init__(*args, **kwargs)
self.fields['destination'].widget.attrs['placeholder'] = 'https://eksempel.dk/meget/lang/url'
self.fields['shortlink'].widget.attrs['placeholder'] = 'eksempel'
self.fields['shortlink'].label_suffix = "" # Remove colon after label
self.fields['shortlink'].required = False # Not required in form
class Meta:
model = Link
fields = ['destination', 'shortlink']
labels = {
'shortlink': ('Evt. selvvalgt kort link, lnk.dk/'),
}
error_messages = {
'destination': {
'max_length': ('Din destinationsurl er for lang til denne kortlinkservice.'),
'invalid': ('Din destinationsurl er ikke en gyldig adresse. Husk http://, https:// eller ftp:// foran dit link, hvis du har glemt det.'),
},
'shortlink': {
'unique': ('Det selvvalgte link, du har valgt, er allerede i brug. Find på et andet.'),
'max_length': ('Dit selvvalgte link må maksimalt være 100 tegn langt.'),
'invalid': ('Du kan kun bruge unicode-bogstaver, cifre, bindestreg og understreg i din selvvalgte adresse.'),
}
}
Mine visninger forberedes i views.py som har:
En funktion til autogenerede kortlinks. Linket tilføjet en tilfældig streng hashes til en ny tilfældig streng. Der tilføjes en tilfældig streng hver gang for at sikre, at der genereres en ny streng hver gang (for at undgå en uendelig løkke, hvis et links hash-værdi skulle kollidere med et andet links hashværdi).
En visning til forsiden med dens formular, validering af formularen og visning af kortlink og eventuelle fejl.
En visning, der sørger for at viderestille fra et kort link til et destinationslink, hvis det korte link findes. Ellers vises en fejlside.
En visning til en “om lnk.dk”-side.
from django.shortcuts import render
from django.http import HttpResponseRedirect
from .models import Link
from .forms import LinkForm
from django.urls import reverse
import hashlib
import bcrypt
# Function to create a random hash to use as short link address
def create_shortlink(destination):
salt = bcrypt.gensalt().decode() # Random salt
destination = destination+salt # Salt added to destination URL
hash = hashlib.md5(destination.encode()).hexdigest() # Hashed to alphanumeric string
return hash[:4] # First 5 characters of that string
# Front page with a form to enter destination address. Short URL returned.
def linkindex(request):
form = LinkForm() # Loads form
# If a destination is submitted, a short link is returned
if request.method == 'POST':
form = LinkForm(request.POST) # Form instance with submitted data
# Check whether submitted data is valid
if form.is_valid():
destination = form.cleaned_data['destination'] # Submitted destination
shortlink = form.cleaned_data['shortlink'] # Submitted slug
# User has specified a unique (validated) short link
if shortlink:
link = form.save(commit=False)
link.type = "manual"
link = form.save()
site_url = reverse('redirect', args=[link.shortlink])
sharelink = request.build_absolute_uri(site_url)
# User wants an automatic link
else:
# If a short link with same destionation of same type already exists,
# it is fetched from database and served. No need to use up a new
# URL for the same destination.
try:
link = Link.objects.get(destination=destination, type="automatic")
site_url = reverse('redirect', args=[link.shortlink])
sharelink = request.build_absolute_uri(site_url)
# If a link of same type with same destination does not exist, one is
# created.
except:
# Loop to create a unique hash value for short link
unique_link = False
while unique_link == False:
hash = create_shortlink(destination) # Return hash
# First we check whether the hash is a duplicate
try:
Link.objects.get(shortlink=hash) # Check whether hash is used
# If not a duplicate, an error is thrown, and we can save the hash
except:
link = form.save(commit=False) # Prepare to save form destination data and hash
link.shortlink = hash # Sets short link to hash value
link.type = "automatic"
link.save() # Saves destination and short link to database
site_url = reverse('redirect', args=[link.shortlink])
sharelink = request.build_absolute_uri(site_url)
unique_link = True # If check causes error, hash is unused, exit loop
context = {'sharelink': sharelink, 'form': form} # Dictionary with variables used in template
return render(request, 'links/index.html', context)
# If form is invalid, check whether a user is trying to create a duplicate manual
# shortlink.
else:
# Check if there's a valid destination link
if 'destination' in form.cleaned_data:
# Check if there's a shortlink that's not unique
try:
link = Link.objects.get(shortlink=form.data['shortlink'])
# If so, check whether the destination is the same
if form.cleaned_data['destination'] == link.destination:
# Show sharelink to user
site_url = reverse('redirect', args=[link.shortlink])
sharelink = request.build_absolute_uri(site_url)
form.errors['shortlink'] = "" # Error replaced by empty string
# Render form with sharelink already used error
else:
sharelink = ""
# Render form with error
except:
sharelink = ""
# Render form with errors
else:
sharelink = ""
context = {'form': form, 'sharelink': sharelink}
return render(request, 'links/index.html', context)
# Render page with form before user has submitted
context = {'form': form}
return render(request, 'links/index.html', context)
# Short link redirect to destination URL
def redirect(request, shortlink):
# Query the database for short link, if there is a hit, redirect to destination URL
try:
link = Link.objects.get(shortlink=shortlink)
return HttpResponseRedirect(link.destination)
# An error means the short link doesn't exist, so error 404 is shown
except:
return render(request, 'links/404.html', status=404)
# About page
def about(request):
context = {'request': request}
return render(request, 'links/about.html', context)
urls.py sørger for at forbinde den adressse, brugeren har tastet i browseren, med de rette visninger fra views.py:
Endelig har jeg skabelon-filer, der sørger for selve html-koden på siden. base.html er min overordnede skabelon med det overordnede design, meta-tags, sidefod osv.:
Tja: Nu har jeg i hvert fald lavet et bud på en gratis, ukommerciel, overvågningsfri og frem for alt: let ønskeseddelservice på wishlist.dkhttps://wallnot.dk/wish.
Som sædvanlig er siden udviklet med Django i Python og selve datamodellen er enkel og gemmer så få oplysninger som muligt om brugeren af siden:
class Wishlist(models.Model):
title = models.CharField('Titel', max_length=500)
emailconfirmationstatus = models.BooleanField('Bekræftet e-mail', default=False)
emailconfirmationtoken = models.CharField('E-mailbekræftelseskode', max_length=32)
editwishlisttoken = models.CharField('Redigeringskode', max_length=32)
readwishlisttoken = models.CharField('Læsningskode', max_length=32)
created_at = models.DateTimeField('Oprettet den', default=timezone.now, editable=False)
class Wish(models.Model):
wishlist = models.ForeignKey(Wishlist, on_delete=models.CASCADE)
title = models.CharField('Ønske', max_length=500)
description = models.CharField('Beskrivelse', max_length=500, blank=True)
shopurl = models.URLField('Link til ønske', max_length=500, blank=True)
imageurl = models.URLField('Link til foto', max_length=500, blank=True)
price = models.DecimalField('Pris', max_digits=20, decimal_places=2, validators=[MinValueValidator(0, message="Må ikke være et negativt tal")], blank=True, null=True)
reserved = models.BooleanField('Reserveret', default=False)
reservation_note = models.CharField('Giver', max_length=500, blank=True)
sort_order = models.PositiveIntegerField('Sortering', null=True, blank=True, default=0)
Ønskesedler kan tilgås med koder i webadressen. Der er en kode, der giver adgang til at redigere ønskesedlen, en der giver adgang til at se ønskesedlen og reservere ønsker, og en der bruges til at bekræfte, at man har modtaget en e-mailnotifikation med link til ønskesedlen. E-mailen bruges til at brugerne kan finde ønskesedlen igen og som en lille-bitte sikkerhedsforanstaltning, idet man først kan dele sin ønskeseddel med andre, når man har bekræftet sin mailadresse. Koderne genereres med Python-modulet Secrets og kan fx være g_q-3bTURYWYCwq6rH1Vu06tumI.
Sådan her ser det ud i Djangos views.py, når en bruger har indtastet en titel på en ønskeseddel og sin mailadresse og systemet bag skal oprette en ønskeseddel:
Lidt ligesom med kortlinksgeneratorer, kan man godt have flertallet af danske webudviklere mistænkt for at have udviklet deres eget bud på en ønskeseddelservice – der dukker i hvert fald en del op, når man søger. Nu har jeg lavet mit bud på danmarks nemmeste ønskeseddel.
Hvis du har børn i skolealderen, kender du måske Aula. Det har jeg, og derfor har jeg lavet en lille programmeringsøvelse, hvor jeg trækker data ud fra Aula’s API.
Det kan ikke rigtigt bruges til noget i nuværende form (jeg bruger heller ikke rigtig selv Aula til noget endnu), men senere kunne det være relevant at udvide med mulighed for at tilgå visse hyppigt brugte funktioner uden at logge ind på hjemmesiden, eller til at lave sit eget personlige Aula-interface.
Ift. mine andre hente-data-fra-API’er-øvelser, har jeg her gjort to ting, som jeg synes er smarte:
Jeg bruger en “session” i Python-modulet requests. Det gør, at jeg ikke behøver at rode med, hvilke cookies, de enkelte trin i loginproceduren, har brug for. De gemmes og benyttes i stedet automatisk gennem trinnene.
I stedet for at gentage en masse kode i hver enkelt trin i login, bruger jeg en løkke, der, selv finder formularer og viste og skjulte input-felter på de enkelte trin, udfylder dem og sender dem af sted.
Hvis du har lyst til at prøve det af, finder du koden her. Du kan finde flere API-forespørgsler ved at bruge din browsers udviklerværktøjer på Aulas side. Koden burde også nemt kunne bruges til at logge ind og hente data fra andre hjemmesider end Aula, det kræver blot et par småjusteringer.
# aula.py
# Author: Morten Helmstedt. E-mail: helmstedt@gmail.com
''' An example of how to log in to the Danish LMS Aula (https://aula.dk) and
extract data from the API. Could be further developed to also submit data and/or to
create your own web or terminal interface(s) for Aula.'''
# Imports
import requests # Perform http/https requests
from bs4 import BeautifulSoup # Parse HTML pages
import json # Needed to print JSON API data
# User info
user = {
'username': '',
'password': ''
}
# Start requests session
session = requests.Session()
# Get login page
url = 'https://login.aula.dk/auth/login.php?type=unilogin'
response = session.get(url)
# Login is handled by a loop where each page is first parsed by BeautifulSoup.
# Then the destination of the form is saved as the next url to post to and all
# inputs are collected with special cases for the username and password input.
# Once the loop reaches the Aula front page the loop is exited. The loop has a
# maximum number of iterations to avoid an infinite loop if something changes
# with the Aula login.
counter = 0
success = False
while success == False and counter < 10:
try:
# Parse response using BeautifulSoup
soup = BeautifulSoup(response.text, "lxml")
# Get destination of form element (assumes only one)
url = soup.form['action']
# If form has a destination, inputs are collected and names and values
# for posting to form destination are saved to a dictionary called data
if url:
# Get all inputs from page
inputs = soup.find_all('input')
# Check whether page has inputs
if inputs:
# Create empty dictionary
data = {}
# Loop through inputs
for input in inputs:
# Some inputs may have no names or values so a try/except
# construction is used.
try:
# Save username if input is a username field
if input['name'] == 'username':
data[input['name']] = user['username']
# Save password if input is a password field
elif input['name'] == 'password':
data[input['name']] = user['password']
# For all other inputs, save name and value of input
else:
data[input['name']] = input['value']
# If input has no value, an error is caught but needs no handling
# since inputs without values do not need to be posted to next
# destination.
except:
pass
# If there's data in the dictionary, it is submitted to the destination url
if data:
response = session.post(url, data=data)
# If there's no data, just try to post to the destination without data
else:
response = session.post(url)
# If the url of the response is the Aula front page, loop is exited
if response.url == 'https://www.aula.dk:443/portal/':
success = True
# If some error occurs, try to just ignore it
except:
pass
# One is added to counter each time the loop runs independent of outcome
counter += 1
# Login succeeded without an HTTP error code and API requests can begin
if success == True and response.status_code == 200:
print("Login lykkedes")
# All API requests go to the below url
# Each request has a number of parameters, of which method is always included
# Data is returned in JSON
url = 'https://www.aula.dk/api/v12/'
### First example API request ###
params = {
'method': 'profiles.getProfilesByLogin'
}
# Perform request, convert to json and print on screen
response_profile = session.get(url, params=params).json()
print(json.dumps(response_profile, indent=4))
### Second example API request ###
params = {
'method': 'profiles.getProfileContext',
'portalrole': 'guardian',
}
# Perform request, convert to json and print on screen
response_profile_context = session.get(url, params=params).json()
print(json.dumps(response_profile_context, indent=4))
# Loop to get institutions and children associated with profile and save
# them to lists
institutions = []
institution_profiles = []
children = []
for institution in response_profile_context['data']['institutions']:
institutions.append(institution['institutionCode'])
institution_profiles.append(institution['institutionProfileId'])
for child in institution['children']:
children.append(child['id'])
children_and_institution_profiles = institution_profiles + children
### Third example API request, uses data collected from second request ###
params = {
'method': 'notifications.getNotificationsForActiveProfile',
'activeChildrenIds[]': children,
'activeInstitutionCodes[]': institutions
}
# Perform request, convert to json and print on screen
notifications_response = session.get(url, params=params).json()
print(json.dumps(notifications_response, indent=4))
### Fourth example API request, only succeeds when the third has been run before ###
params = {
'method': 'messaging.getThreads',
'sortOn': 'date',
'orderDirection': 'desc',
'page': '0'
}
# Perform request, convert to json and print on screen
response_threads = session.get(url, params=params).json()
#print(json.dumps(response_threads, indent=4))
### Fifth example. getAllPosts uses a combination of children and instituion profiles. ###
params = {
'method': 'posts.getAllPosts',
'parent': 'profile',
'index': "0",
'institutionProfileIds[]': children_and_institution_profiles,
'limit': '10'
}
# Perform request, convert to json and print on screen
response_threads = session.get(url, params=params).json()
print(json.dumps(response_threads, indent=4))
# Login failed for some unknown reason
else:
print("Noget gik galt med login")
Jeg har udviklet en lille hjemmeside, der monitorerer priserne på skyr i Storkøbenhavn. Du kan finde den på https://wallnot.dk/skyr.
Sådan ser hjemmesiden med historiske og (et lille bitte stykke) fremtidige priser på skyr ud.
Sådan virker det…
Skyrpriser består af:
En database med en model defineret i Django’s models.py
Et python-script, cron_skyrpriser.py, der køres som job en gang i døgnet og skraber tilbud på skyr fra https://etilbudsavis.dk og gemmer dem i databasen
Et view i Django’s views.py, der gør data fra databasen klar i en struktur, der er brugbar i sidens skabelon
En skabelon (index.html), som indeholder sidens HTML-kode, stylesheet og det javascript der, ved hjælp af biblioteket Chart.js, genererer grafen over Skyrpriser
Jeg starter med datamodellen i models.py. Hovedtabellen hedder “Offer” og gemmer typen af skyr, hvilken butik, der er tale om, hvilken dato tilbuddet gælder og kiloprisen for tilbuddet:
from django.db import models
from django.utils import timezone
from django.contrib import admin
class Offer(models.Model):
skyr_type = models.CharField('Skyrtype', max_length=100)
store = models.CharField('Butik', max_length=100)
date = models.DateField('Dato')
price_per_kilo = models.FloatField('Kilopris')
added_at = models.DateTimeField('Tilføjelsesdato', default=timezone.now, editable=False)
class OfferAdmin(admin.ModelAdmin):
list_display = ('store','skyr_type','date')
list_filter = ('store', 'skyr_type')
search_fields = ['store', 'skyr_type']
Så kommer jeg til cron_skyrpriser.py. Jeg har brugt min browsers udviklerværktøjer til at finde ud af, hvordan jeg taler med API’et for etilbudsavis.dk og får data tilbage i JSON-format. Jeg henter de felter, jeg har brug for og gemmer dem i databasen, hvis de ikke allerede findes i databasen:
import requests
from datetime import datetime, date, timedelta
from bs4 import BeautifulSoup
import psycopg2
from psycopg2 import Error
import pytz
now = datetime.now()
cph = pytz.timezone('Europe/Copenhagen')
# Connect to database
try:
connection = psycopg2.connect(user = "[slettet]",
password = "[slettet]",
host = "[slettet]",
port = "",
database = "[slettet]")
cursor = connection.cursor()
except (Exception, psycopg2.Error) as error:
print ("Error while connecting to PostgreSQL", error)
### INSERT SKYR IN DATABASE FUNCTION ###
def insert_in_database(connection, offer):
with connection:
with connection.cursor() as cur:
try:
sql = ''' SELECT * from skyrpriser_offer WHERE skyr_type = %s AND store = %s AND date = %s'''
cur.execute(sql, (offer[0], offer[1], offer[2]))
results = cur.fetchall()
if not results:
sql = ''' INSERT INTO skyrpriser_offer(skyr_type,store,date,price_per_kilo,added_at)
VALUES(%s,%s,%s,%s,%s)'''
cur.execute(sql, offer)
except Error as e:
print(e, offer)
# Scrape prices of skyr and save to database
def main():
url = "https://etilbudsavis.dk/api/squid/v2/sessions"
session = requests.Session()
headers = {
'authority': 'etilbudsavis.dk',
'accept': 'application/json',
'dnt': '1',
'user-agent': 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/81.0.4044.129 Safari/537.36',
'x-api-key': '[slettet]',
'sec-fetch-site': 'same-origin',
'sec-fetch-mode': 'cors',
'sec-fetch-dest': 'empty',
'referer': 'https://etilbudsavis.dk/search/skyr',
'accept-language': 'en-US,en;q=0.9',
'cookie': 'sgn-flags=^{^%^22flags^%^22:^{^}^}; sgn-consents=^[^]',
}
session.headers.update(headers)
response = session.get(url)
url = "https://etilbudsavis.dk/api/squid/v2/offers/search?query=skyr&r_lat=55.695497&r_lng=12.550145&r_radius=20000&r_locale=da_DK&limit=24&offset=0"
response = session.get(url)
response_json = response.json()
for item in response_json:
skyr_type = item['heading']
store = item['branding']['name']
valid_from = item['run_from']
valid_from = datetime.strptime(valid_from, '%Y-%m-%dT%H:%M:%S%z').astimezone(cph).date()
valid_to = item['run_till']
valid_to = datetime.strptime(valid_to, '%Y-%m-%dT%H:%M:%S%z').astimezone(cph).date()
price = item['pricing']['price']
amount = item['quantity']['size']['from']
measure = item['quantity']['unit']['symbol']
if measure == "g":
price_per_kilo = price/amount*1000
elif measure == "kg":
price_per_kilo = price/amount
number_of_days = int((valid_to - valid_from).days)
for day in range(number_of_days+1):
date = valid_from + timedelta(day)
offer = (skyr_type, store, date, price_per_kilo, now)
insert_in_database(connection, offer)
main()
print("Opdaterede skyrpriser")
I Django’s views.py henter jeg databasetabellens indhold og gør dem klar vha. nogle løkker, som formentlig er ret ineffektive, men virker OK:
from django.shortcuts import render
from .models import Offer
from django.db.models import Max, Min
from datetime import timedelta
# Main page
def skyrindex(request):
offers = Offer.objects.all().order_by('date')
context = {}
if offers:
date_min = Offer.objects.aggregate(Min('date'))['date__min']
date_max = Offer.objects.aggregate(Max('date'))['date__max']
number_of_days = (date_max - date_min).days
dates = []
for i in range(number_of_days + 1):
dates.append(date_min + timedelta(i))
structure = {}
for offer in offers:
if not offer.store in structure:
structure[offer.store] = {}
if not offer.skyr_type in structure[offer.store]:
structure[offer.store][offer.skyr_type] = []
structure[offer.store][offer.skyr_type].append({offer.date: round(offer.price_per_kilo, 1)})
new_structure = {}
for store, offer in structure.items():
new_structure[store] = {}
for skyr_type, prices in offer.items():
new_structure[store][skyr_type] = []
for date in dates:
have_price = False
for price in prices:
if date in price:
new_structure[store][skyr_type].append({date: price[date]})
have_price = True
if not have_price:
new_structure[store][skyr_type].append({date: ","})
context = {'dates': dates, 'structure': structure, 'new_structure': new_structure}
return render(request, 'skyrpriser/index.html', context)
Og til sidst har jeg så index.html, som også har nogle (for mig) ret komplicerede løkker for at strukturere data i et format som Javascript-bibliteket Chart.js kan forstå.
Jeg benytter mig af nogle, synes jeg, smarte features i Django’s løkke-funktioner:
cycle: Gør det muligt at løbe igennem en prædefineret række værdier hver gang løkken køres, her brugt til at få en ny farve per linje i diagrammet.
forloop.last: Den sidste gang en løkke kører, sættes variablen forloop.last. Det gør at jeg fx nemt kan sætte komma efter hver dato i diagrammets x-akse, undtagen efter den sidste dato på listen.
Her er index.html:
<h1>Skyrpriser</h1>
<canvas id="myChart"></canvas>
<script>
var ctx = document.getElementById('myChart');
var myChart = new Chart(ctx, {
type: 'line',
data: {
labels: [{% for date in dates %}'{{ date|date:"d. b" }}'{% if not forloop.last %}, {% endif %}{% endfor %}],
datasets: [{% for store, offer in new_structure.items %}
{% for skyr_type, prices in offer.items %}
{
fill: false,
backgroundColor: {% cycle "'#e9ecef'," "'#ffc9c9'," "'#fcc2d7'," "'#eebefa'," "'#d0bfff'," "'#bac8ff'," "'#a5d8ff'," "'#99e9f2'," "'#96f2d7'," "'#b2f2bb'," "'#d8f5a2'," "'#ffec99'," "'#ffd8a8'," %}
borderColor: {% cycle "'#e9ecef'," "'#ffc9c9'," "'#fcc2d7'," "'#eebefa'," "'#d0bfff'," "'#bac8ff'," "'#a5d8ff'," "'#99e9f2'," "'#96f2d7'," "'#b2f2bb'," "'#d8f5a2'," "'#ffec99'," "'#ffd8a8'," %}
label: '{{ store|safe }}, {{ skyr_type|safe }}',
data: [
{% for price in prices %}
{% for date, cost in price.items %}
{% if not cost == "," %}
{{ cost|unlocalize }}
{% endif %}
{% endfor %}
{% if not forloop.last %}
,
{% endif %}
{% endfor %}
]
}{% if not forloop.last %},{% endif %}
{% endfor %}
{% if not forloop.last %},{% endif %}
{% endfor %}]
},
options: {
responsive: true,
spanGaps: false,
title: {
display: true,
text: 'Tilbud på Skyr over tid'
},
tooltips: {
mode: 'index',
intersect: false,
},
hover: {
mode: 'nearest',
intersect: true
},
scales: {
xAxes: [{
display: true,
scaleLabel: {
display: true,
labelString: 'Dato'
}
}],
yAxes: [{
display: true,
scaleLabel: {
display: true,
labelString: 'Pris pr. kilo Skyr i kroner'
}
}]
}
}
});
</script>
Jeg har lavet endnu et Django-eksperiment med https://ugenr.dk som det store forbillede.
En digital kalender
På https://wallnot.dk/kalender kan du altid finde en Mayland-style-kalender med helligdage og ugenumre. Kalenderen understøtter år 1 til 9999.
Den er lavet med tre side-funktioner: En der altid viser nuværende halvår (kalindex), en der viser et hvilket som helst halvår (kalperiod) og en der kan vise et hvilket som helst år (kalyear). Alle tre funktioner kalder en fjerde funktion get-dates der returnerer datoer i kalenderen for det år og/eller halvår, der efterspørges.
Her er views.py:
from django.shortcuts import render
import datetime
from workalendar.europe import Denmark # Module containing most Danish holidays
from django.http import Http404
# Function to return all calendar dates and other context data
def get_dates(year, period, now):
now_isocalendar = now.isocalendar()
### HOLIDAY LIST FOR YEAR IS GENERATED ###
# Create dictionary with all holidays of the year
holidays = Denmark().holidays(year)
all_holidays = {}
all_holidays[datetime.date(year,5,1)] = ["Første maj", "Særlig dag"]
all_holidays[datetime.date(year,6,5)] = ["Grundlovsdag", "Særlig dag"]
all_holidays[datetime.date(year,12,31)] = ["Nytårsaften", "Særlig dag"]
holiday_lookup = {
"New year": ["Nytårsdag", "Helligdag"],
"Holy Thursday": ["Skærtorsdag", "Helligdag"],
"Good Friday": ["Langfredag", "Helligdag"],
"Easter Sunday": ["Påskedag", "Helligdag"],
"Easter Monday": ["2. påskedag", "Helligdag"],
"Store Bededag": ["Store bededag", "Helligdag"],
"Ascension Thursday": ["Kr. himmelfart", "Helligdag"],
"Pentecost Sunday": ["Pinsedag", "Helligdag"],
"Pentecost Monday": ["2. pinsedag", "Helligdag"],
"Christmas Eve": ["Juleaften", "Særlig dag"],
"Christmas Day": ["1. juledag", "Helligdag"],
"Second Day of Christmas": ["2. juledag", "Helligdag"],
}
for holiday in holidays:
# Check for two holidays on same day
if holiday[0] not in all_holidays:
all_holidays[holiday[0]] = (holiday_lookup[holiday[1]][0], holiday_lookup[holiday[1]][1])
# If two on the same day, names are concenated
else:
all_holidays[holiday[0]] = (holiday_lookup[holiday[1]][0] + "/" + all_holidays[holiday[0]][0] , holiday_lookup[holiday[1]][1])
### DATES FOR YEAR ARE GENERATED IN A DAY AND MONTH DIMENSION ###
# First dimension is maximum number of days in a month
dates_in_year = {}
for day in range(1,32):
dates_in_year[day] = []
# Second dimension is that date for each month
for day in range(1,32):
for month in period:
# If the generated day actually is a valid date, day is added to dates_in_year dictionary
try:
date_to_add = datetime.date(year,month,day)
date_isocalendar = date_to_add.isocalendar()
# HOLIDAY LOGIC #
# If day is special, get type of day and name of day
if date_to_add in all_holidays:
type_of_day = all_holidays[date_to_add][1]
name_of_day = all_holidays[date_to_add][0]
# If not, type of day is normal and no name
else:
type_of_day = "Normal dag"
name_of_day = "Intet navn"
# HTML BORDER CLASS LOGIC #
html_class = ""
# Year of date must be the same as year of current date
if date_isocalendar[0] == now_isocalendar[0]:
# Week number is the same as current week number
if date_isocalendar[1] == now_isocalendar[1]:
# All days get a red right and red left class
html_class = "redleft redright"
# Sunday also gets a red bottom class
if date_isocalendar[2] == 7:
html_class += " redbottom"
# Date is Sunday in the week before current
elif date_isocalendar[1] == now_isocalendar[1] - 1 and date_isocalendar[2] == 7:
html_class += " redbottom"
# Same date next month is in current week
try:
date_next_month = datetime.date(year,month + 1,day)
date_next_month_isocalendar = date_next_month.isocalendar()
# Week number is the same as current week number
if date_next_month_isocalendar[1] == now_isocalendar[1]:
html_class = "redright"
except ValueError:
pass
date_data = (date_to_add, type_of_day, name_of_day, html_class)
dates_in_year[day].append(date_data)
# Except when that dates does not exist, e.g. february 30
except ValueError:
dates_in_year[day].append("NON-EXISTING DATE")
context = {'year': str(year), 'next': year+1, 'previous': year-1, 'dates_in_year': dates_in_year, 'period': period, 'now': now}
return context
# Main page
def kalindex(request):
now = datetime.datetime.now()
year = now.year
month = now.month
if month < 7:
period = range(1,7)
else:
period = range(7,13)
# Run function to get calendar dates
context = get_dates(year, period, now)
return render(request, 'kalender/index.html', context)
# Earlier or future year page
def kalyear(request, year):
# If year is not an integer, a 404 error is thrown
try:
year = int(year)
except ValueError:
raise Http404
# If year is between 1 and 10000, a calendar is rendered
if year > 0 and year < 10000:
now = datetime.datetime.now()
period = range(1,13)
# Run function to get calendar dates
context = get_dates(year, period, now)
return render(request, 'kalender/index.html', context)
# If not, a 404 error is thrown
else:
raise Http404
# Earlier or future year page
def kalperiod(request, year, period):
# If year is not an integer, a 404 error is thrown
try:
year = int(year)
except ValueError:
raise Http404
# If year is between 1 and 10000, a calendar is rendered
if year > 0 and year < 10000 and (period == "1" or period == "2"):
if period == "1":
period = range(1,7)
elif period == "2":
period = range(7,13)
now = datetime.datetime.now()
# Run function to get calendar dates
context = get_dates(year, period, now)
return render(request, 'kalender/index.html', context)
# If not, a 404 error is thrown
else:
raise Http404
Sidens skabelon index.html ser en lille smule rodet ud (af hensyn til at minimere sidens størrelse). Skabelonen genererer en tabel ved at gennemgå alle dagene i kalenderen og tilføje særlige layout-regler for lørdage, søndage, helligdage, den nuværende uge, dag og ugenummer osv.
Her er den del af den, der benytter sig af Djangos skabelon-funktioner. (Resten af koden kan du finde ved at bruge “view source” på https://wallnot.dk/kalender):
{% if period|length == 12 %}
{% if not year == "1" %}<a href="{% url 'kal_year' previous %}" title="Se kalender for året før">« forrige</a>{% endif %}<h1> Kalender for år {{ year }} </h1>{% if not year == "9999" %}<a href="{% url 'kal_year' next %}" title="Se kalender for året efter">næste »</a>{% endif %} <a class="calendartype" href="{% if now|date:"n" == "7" or now|date:"n" == "8" or now|date:"n" == "9" or now|date:"n" == "9" or now|date:"n" == "10" or now|date:"n" == "11" or now|date:"n" == "12" and now|date:"Y" == year %}{% url 'kal_period' year 2 %}{% else %}{% url 'kal_period' year 1 %}{% endif %}" title="Gå til halvårskalender">Til halvårskalender</a>
{% elif period|last == 6 %}
{% if not year == "1" %}<a href="{% url 'kal_period' previous 2 %}" title="Se kalender for halvåret før">« forrige </a>{% endif %}<h1> Kalender for år {{ year }}, første halvår </h1><a href="{% url 'kal_period' year 2 %}" title="Se kalender for halvåret efter">næste »</a> <a class="calendartype" href="{% url 'kal_year' year %}" title="Gå til helårskalender">Til helårskalender</a>
{% else %}
<a href="{% url 'kal_period' year 1 %}" title="Se kalender for halvåret før">« forrige</a><h1> Kalender for år {{ year }}, andet halvår </h1>{% if not year == "9999" %}<a href="{% url 'kal_period' next 1 %}" title="Se kalender for halvåret efter">næste »</a>{% endif %} <a class="calendartype" href="{% url 'kal_year' year %}" title="Gå til helårskalender">Til helårskalender</a>
{% endif %}
<p>I dag er det {{ now|date:"l" }} den {{ now|date }} i uge {{ now|date:"W" }}</p>
<table>
<thead>
<tr>
{% if period|length == 12 %}
<th>Januar</th>
<th>Februar</th>
<th>Marts</th>
<th>April</th>
<th>Maj</th>
<th>Juni</th>
<th>Juli</th>
<th>August</th>
<th>September</th>
<th>Oktober</th>
<th>November</th>
<th>December</th>
{% elif period|last == 6 %}
<th>Januar</th>
<th>Februar</th>
<th>Marts</th>
<th>April</th>
<th>Maj</th>
<th>Juni</th>
{% else %}
<th>Juli</th>
<th>August</th>
<th>September</th>
<th>Oktober</th>
<th>November</th>
<th>December</th>
{% endif %}
</tr>
</thead>
<tbody>
{% for month, monthdays in dates_in_year.items %}
<tr>
{% for day in monthdays %}
<td{% if day.1 == "Helligdag" or day.0|date:"w" == "0" %} class="holy{% if day.3 %} {{ day.3 }}{% endif %}"{% elif day == "NON-EXISTING DATE" %} class="noborder"{% elif year == now|date:"Y" and day.3 %} class="{{ day.3 }}"{% endif %}>
<div title="{{ day.0|date:"l"|capfirst }}" class="weekday{% if day.0|date:"w" == "6" %} saturday{% endif %}{% if day.0|date == now|date %} red{% endif %}">{{ day.0|date:"D"|slice:":1"|upper }}</div>
<div class="datenum{% if day.0|date:"w" == "6" %} saturday{% endif %}{% if day.0|date == now|date %} red{% endif %}">{{ day.0|date:"j" }}</div>
{% if day.0|date:"w" == "1" %}<div title="Uge {{ day.0|date:"W" }}" class="weeknum{% if day.0|date:"Y W" == now|date:"Y W" %} red{% endif %}">{{ day.0|date:"W" }}</div>{% endif %}
{% if day.1 == "Helligdag" or day.1 == "Særlig dag" %}<div title="{{ day.2 }}" class="named{% if "/" in day.2 and period|length == 12 %} named-small{% endif %}{% if day.0|date == now|date %} red{% endif %}">{{ day.2 }}</div>{% endif %}
</td>
{% endfor %}
</tr>
{% endfor %}
</tbody>
</table>
Den nyeste besøgende ikke er den samme som den sidste besøgende
Datamodellen i models.py definerer en tæller, ip-adressen på sidste besøgende og tidspunkt for sidste opdatering af tælleren:
from django.db import models
from django.utils import timezone
class Counter(models.Model):
count = models.PositiveIntegerField('Besøgende nummer')
last_ip = models.GenericIPAddressField('Sidste besøgendes IP-adresse')
date = models.DateTimeField(default=timezone.now, editable=False)
I views.py definerer jeg logikken bag, hvornår der skal opdateres. Jeg bruger et modul til Django for at finde brugerens IP:
from django.shortcuts import render
from .models import Counter
from ipware import get_client_ip
def countindex(request):
# Get current count
try:
counter = Counter.objects.get(pk=1)
# If a count does not exist (first visit to site), one is created
except:
firstcount = Counter(count=0, last_ip='0.0.0.0'
)
firstcount.save()
counter = Counter.objects.get(pk=1)
# Get user IP
client_ip, is_routable = get_client_ip(request)
# If user IP exists, check whether user is identical to last user
# (If no user IP, nothing happens)
if client_ip is not None:
# Check whether user is identical to last user
try:
Counter.objects.get(last_ip=client_ip)
# If not, one is added to visitor count and IP is saved
except:
counter.count += 1
counter.last_ip = client_ip
counter.save()
context = {'ip': client_ip, 'counter': counter}
return render(request, 'vcounter/index.html', context)
Endelig har jeg min skabelon index.html som viser brugeren hvad nummer besøgende, hun er, og hendes IP-adresse:
<h1>Du er besøgende nummer<br>
<strong>{{ counter.count }}</strong></h1>
(Dit ip-nummer er: {{ ip }})
Derudover skal der bygges et view, der beskriver forespørgslen til databasen. Her i en forkortet udgave uden logikken bag brugerrapportering af links bag paywall:
from django.shortcuts import render
from django.core.paginator import Paginator
import requests
import json
from .models import Article
def index(request):
articles = Article.objects.order_by('-date')
searchterm = request.GET.get('q')
medium = request.GET.get('m')
ritzau = request.GET.get('r')
duplicates = request.GET.get('d')
newwindow = request.GET.get('w')
if searchterm:
firstsearchcharacter = searchterm[:1]
# Exclude queries by adding ! to searchterm
if firstsearchcharacter == "!":
searchterm = searchterm[1:]
articles = articles.exclude(title__iregex=searchterm)
searchterm = "!" + searchterm
# Perform normal regex-enabled search
else:
articles = articles.filter(title__iregex=searchterm)
if medium:
articles = articles.filter(medium=medium)
if ritzau:
articles = articles.exclude(ritzau=True)
if not duplicates and not medium:
articles = articles.exclude(duplicate=True)
paginator = Paginator(articles, 80)
page_number = request.GET.get('page')
page_obj = paginator.get_page(page_number)
context = {'request': request, 'page_obj': page_obj, 'medium': medium, 'searchterm': searchterm, 'ritzau': ritzau, 'newwindow': newwindow, 'duplicates': duplicates}
return render(request, 'wall/index.html', context)
Til sidst skrives en skabelon (template) der omsætter data til HTML. Her er fx den ganske korte bid kode, der spytter artikellinks ud på siden:
{% for article in page_obj %}
{% ifchanged article.date|date %}<h3>{{ article.date|date }}</h3>{% endifchanged %}
<p>{{ article.date|date:"H:i" }}: <a href="{{ article.url }}"{% if newwindow %} target="_blank"{% endif %}>{{ article.title }}</a> {% if article.ritzau %}<small><sup> ritzau </sup></small> {% endif %}{% if article.duplicate and not medium %}<small><sup> dublet </sup></small> {% endif %}<img title="Giv besked hvis artiklen er bag en paywall" id="{{ article.id }}" class="myBtnt" src="{% static "wall/alert.svg" %}"/></p>
{% endfor %}
Til Wallnot ville jeg gerne have fat i samtlige Zetland-historier, som Google har indekseret.
Til det formål skrev jeg et lille program, der gennemgår Googles søgeresultater. Programmet holder en lille pause mellem hver side med søgeresultater, der hentes. Det skyldes at Google åbenbart ikke selv er vild med robotter, paradoksalt nok.
import requests
from bs4 import BeautifulSoup
import time
import random
linkcollection = []
def google_results(url):
try:
result = requests.get(url)
soup = BeautifulSoup(result.text, "lxml")
links = soup.find_all('a')
for link in links:
if "zetland.dk/historie/" in link['href']:
full_link = link['href']
url = full_link[full_link.find("q=")+2:full_link.find("&")]
linkcollection.append(link['href'])
print(link['href'])
next_page = soup.find('a', attrs={'aria-label': 'Næste side'})
time_to_sleep = random.randrange(3,7)
print("Sleeping " + str(time_to_sleep) + " seconds")
time.sleep(time_to_sleep)
google_results('https://www.google.com'+next_page['href'])
except TypeError:
print("No more results it seems")
url = 'https://www.google.com/search?q=site:zetland.dk/historie'
google_results(url)
with open("./googlelist.txt", "wt", encoding="utf8") as fout:
fout.write(str(linkcollection))
Jeg syntes, det var ubehageligt at kunne se, hvordan Facebook lod forskellige virksomheder matche deres oplysninger om mig (e-mails, telefonnummer, den slags) med min Facebook-konto.
Det drejede sig både om store, grimme virksomheder:
Og små, søde, rettighedsorienterede NGO’er:
Min idé til en løsning var:
At slette mit telefonnummer fra min profil på Facebook
At oprette en e-mail særligt til min Facebook-profil (lad os sige: facebookholderojemed@helmstedt.dk)
…Og så håbede jeg ellers, at “matchene” ville ophøre.
Men: Det gjorde de ikke.
Hvordan kan det være?
Facebook beholder alle mailadresser, du nogensinde har haft tilknyttet din konto – også de, du selv sletter! Og de lader annoncører matche deres oplysninger om DIG med de oplysninger, du troede, du havde slettet.
(Du kan prøve at se selv, ved at bruge Facebook’s funktion til at downloade en kopi af dine data.)
Så begyndte mit rigtige eventyr:
Mit forsøg på at få slettet gamle mailadresser hos Facebook
Efter at have svaret på et hav af spørgsmål, fik jeg lov at udfylde en kontaktformular:
Select the product that you need help with : Facebook What can we help you with? : I want to manage my data Select one of the following options : I have a different objection to the use of my data Full name : Morten Helmstedt Please provide your best contact email address : facebookholderojemed@helmstedt.dk Where do you live? : Denmark
What data processing activity or activities are you objecting to? : I am objecting to Facebook matching my personal information with information uploaded by advertisers and do not consent to Facebook allowing advertisers to do this. Even though I have changed my e-mail address to an address only used for Facebook communication and have deleted my phone number and additional e-mail addresses from Facebook, Facebook still matches my information with lists from advertisers. See https://helmstedt.dk/Clipboard01.png for a screenshot. I would like to be informed in what way advertisers are able to match their lists with my Facebook profile, when no information from my Facebook profile could be in possession by these advertisers after I changed my Facebook profile e-mail and phone number.
If this matching is done by Facebook keeping deleted information from my profile, I do not consent to Facebook keeping this information and I request that this information be deleted, as Facebook no longer has any valid grounds or consent for keeping this information.
Please explain how this processing impacts you. : I have a right to control my personal data according to the EU GDPR regulations and have not consented to Facebook matching my personal data with personal data from advertisers.
By submitting this notice, you represent that all of the information you’ve provided is true and accurate. : I agree
Det var i første omgang ikke til så meget hjælp. Facebook bekræftede blot, deres praksisser:
Hi,
Thanks for contacting us.
To build a product that connects people across continents and cultures, we need to make sure that everyone can afford it. Advertising lets us keep Facebook free. You can’t opt out of ads altogether because ads are what keep Facebook free, but you do have different options to control how your personal data can and can’t be used to show you ads. They’re all found in ad preferences: https://www.facebook.com/ads/preferences/?ref=CR
Please note that we do not tell advertisers who you are or sell your information to anyone.
There are a few ways that advertisers can reach you with ads on Facebook:
Information from your use of Facebook
When you use Facebook, you can choose to share things about yourself, such as your age, gender, home town or friends. You can also click or like posts, Pages or articles. We use this information to understand what you might be interested in and hopefully show you ads that are relevant. If a bike shop comes to Facebook wanting to reach female cyclists in Liverpool, we can show their ad to women in Liverpool who liked a Page about bikes. But here’s what’s key: these businesses don’t know who you are. We provide advertisers with reports about the kinds of people seeing their ads and how their ads are performing, but we don’t share information that personally identifies you. You can always see the “interests” assigned to you in your ad preferences, and if you want, remove them.
Information that an advertiser shares with us
In this case, advertisers bring us their customer information so they can reach the same people on Facebook. These advertisers might have your email address from a purchase you made, or from some other data source. We find Facebook accounts that match that data, but we don’t tell the advertiser which accounts were matched. In ad preferences (https://www.facebook.com/ads/preferences/) you can see which advertisers with your contact information are currently running campaigns – and you can click the top right-hand corner of any ad to hide all ads from that business.
Information that websites and apps send to Facebook
Some of the websites and apps you visit may use Facebook tools to make their content and ads more relevant and better understand the results of their ad campaigns. For example, if an online retailer is using Facebook pixel, they can ask Facebook to show ads to people who looked at a certain style of shoe or put a pair of shoes into their shopping basket. If you don’t want this data used to show you ads, you can turn it off in ad preferences.
You can learn more about Facebook pixel and how it works here: https://www.facebook.com/business/learn/facebook-ads-pixel/?ref=CR
You can decide which parts of your profile you want to be used for ad targeting in the Information section under “About you”. You can remove yourself from interests under “Interests” and categories under “Your categories”. You can also turn off ads that use data from apps or websites that you visit in the Ads settings section under “Ads based on use of websites and apps”.
The “How is this information shared?” section of our Data Policy also discusses in more detail how ads work on Facebook: https://www.facebook.com/about/privacy/?ref=CR
The form that you submitted allows EU residents to report objections to certain types of processing of their personal data under the EU General Data Protection Regulation (GDPR). If you want to object to a specific type of data processing listed in our Data Policy, please visit the Help Centre to learn more about making an objection under GDPR and in what circumstances an objection may be successful: https://www.facebook.com/help/2069235856423257/?ref=CR
Before you submit another objection, you may want to learn more about our legal bases for processing data, including the instances where the processing is necessary for our legitimate interests (or that of a third party) or for a task carried out in the public interest: https://www.facebook.com/about/privacy/legal_bases/?ref=CR
We hope this helps, but please let us know if you have any other questions.
Thanks, Ryan, Privacy Operations Facebook
Jeg bad så specifikt Facebook om at slette mine gamle e-mailadresser, da jeg havde svært ved at se noget som helst gyldigt formål ved at opbevare disse data. Her er svaret, jeg fik:
Hi Morten,
Thanks for following up with us.
From your report it appears you would like to delete information from your Facebook account.
Deleting your information from Facebook You can delete specific data points from your Facebook account via your Activity Log. You can access your Activity Log and to choose to delete certain data points by accessing your Settings > Your Facebook Information > Activity Log. It appears from your report you are already aware of this, but please note you can choose to permanently delete your profile, photos, posts, videos, and everything else you’ve added at any time by deleting your Facebook account. You can follow the steps outlined in the following Help Center article to understand how to permanently delete your account: https://www.facebook.com/help/224562897555674
Deleting previous email addresses From your report it appears you would like us to delete the email addresses previously associated with your account. As explained in our Data Policy (https://www.facebook.com/policy.php (https://www.facebook.com/about/privacy/update#legal-requests-prevent-harm)), we need to process certain information in order to detect and prevent spam and other bad experiences on Facebook, maintain the integrity of our Products, and promote safety and security on and off the Facebook Products. In relation to your specific request, the information you have asked to be deleted is necessary for us to maintain the integrity of our Products, and promote safety and security on and off the Facebook Products.
[…]
Under Article 17 of the GDPR there are limited grounds on which the erasure of personal data can be obtained. We have reviewed your request in light of the information you have provided to us, and we have found that your request does not meet one of the grounds listed in Article17 of the GDPR. We are therefore unable to take further action on your request to have this data point deleted.
Please note that you have a right to contact the Irish Data Protection Commission, which is Facebook’s lead supervisory authority (please see www.dataprotection.ie (http://www.dataprotection.ie/))
You also have the right to contact your local data protection authority and to bring a claim before the courts.
We trust this addresses your query but please let us know if you have any further questions.
Thanks, Elsa Privacy Operations Facebook
Så Facebook mener, at:
In relation to your specific request, the information you have asked to be deleted is necessary for us to maintain the integrity of our Products, and promote safety and security on and off the Facebook Products
Aha!
Jeg forsøgte mig med det (næst)sidste kort, jeg havde på hånden:
Dear Elsa Under GDPR I have a right to rectify incorrect data. As my previous e-mail addresses are no longer my e-mail addresses, they should be deleted. You have no valid use for e-mail addresses that I no longer use. Please delete those e-mail addresses and confirm. Best regards, Morten
Den logik kunne Elsa fra Facebook ikke følge:
Hi Morten,
Thanks for following up with us and for your patience.
As explained in our Data Policy (https://www.facebook.com/policy.php), we need to process certain information in order to detect and prevent spam and other bad experiences on Facebook, maintain the integrity of our Products, and promote safety and security on and off the Facebook Products. Please note that all these measures are taken to make the platform safer for our users.
If your personal data is inaccurate, you have the right to have the data rectified by Facebook. In this case, there is no suggestion that we are processing inaccurate data, but rather retaining your previous email address for the reasons explained above.
We won’t be able to take any further action on this request, but please note that you have a right to contact the Irish Data Protection Commission, which is Facebook’s lead supervisory authority (please see www.dataprotection.ie (http://www.dataprotection.ie/))
Best regards, Elsa Privacy Operations Facebook
For Facebook handler ukorrekte persondata ikke om data, der ikke længere/nogensinde beskriver personen korrekt. For alt data, der er tilgået Facebook, er per definition korrekt råmateriale for Facebooks overvågning.
Moralen?
Nu har jeg slettet min Facebookkonto. Jeg opfordrer dig til at gøre det samme.
