io.ByteReader and io.EOFIn: c’t 13/2025, S. 144—146.
Siehe auch: c’t 9/2025, S. 150—151
/Icon files.zfs/rsync invocationrsync invocationgit/*rsync invocationrsync invocation.eml datesqpdfdefer and panic gotcha:/” und Text “Temporal einseitige Anomalien ; Der zukunftsbesessene Lichtraub”.gnome-disksvalidator.w3.org buggit’s operationsbt on Debianlscaseansiclrdig using aptvim stylingpacman keysvalidator.w3.org’s hottest tipstar invocationscurl invocationsvim settingsbrew’s diagnosticsWriteup: 2019-10-28_jonathan-frech_extending-a056154.pdf
See also: https://blog.jfrech.com/221/
b-file: 2019-09-10_Jonathan-Frech_b325902.txt.
See also: https://blog.jfrech.com/220/
See also: https://blog.jfrech.com/171/
See also: https://blog.jfrech.com/162/
In: c’t 23/2015, S. 48.
Siehe auch: https://blog.jfrech.com/74/ und https://blog.jfrech.com/87/.
Jonathan Frech operates the domains jfrech.com, jfrech.blog, jfrech.de, jonathan-frech.de, jfre.ch, jfrech.net, jfrech.org, knotm.de, f0u.de and spamspam.de together with all their subdomains in accordance to German and European law. See also Privacy above. For (e-)mail inquiries, please refer to Contact below.
https://codegolf.stackexchange.com/users/73111/jonathan-frech (PPCG) https://stackexchange.com/users/11472647/jonathan-frech https://sr.ht/~jfrech https://gitlab.com/jfrech https://github.com/jfrech (with despisal) https://wiki.freebsd.org/JonathanFrech https://wiki.archlinux.org/title/User:Jonathan_Frech https://wiki.filezilla-project.org/User:Jonathan_Frech https://wiki.gentoo.org/wiki/User:Jonathan_Frech https://oeis.org/wiki/User:Jonathan_Frech https://en.wikipedia.org/wiki/User:Jonathan_Frech https://fr.wikipedia.org/wiki/Utilisateur:Jonathan_Frech https://de.wikipedia.org/wiki/Benutzer:Jonathan_Frech
Jonathan Frech <info@jfrech.com>
Postal Address: reveal
GDPR’s basic tenet of minimising information is fully implemented in the entirety of my tech stack: TLS 1.3 is relentlessly required, cookies are not used by any of my web services as do they log sparsely with a maximum log retainment of a few months.
Due to the Internet’s routing behaviour, Internet Protocol (IP) metadata (cf. [RFC791, 3.1]) and Domain Name System metadata (cf. [RFC1035, 3.2.1]) as well as their access times are let known to third parties, uncontrollable by me.
Should you request my websites using unsecured http://, your request is visible to the world. My web services redirect to a https:// resource as quickly as possible but leaked data before communication with my web services is established I cannot prevent.
Since I do not operate my own physical server, the unencrypted entirety of all my web services’ interactions with the world is known to netcup GmbH with whom I hold an Auftragsverarbeitungsvereinbarung.
Due to employing certificates from Let’s Encrypt, they both gain diluted metadata when a seldom viewed page of mine is accessed (certificate renewal) as well as clients are forced to retrieve their root certificates which may incur additional metadata.