Website and blog: https://seirdy.one

Full bio

Gemini: gemini://seirdy.one

Main fedi: @seirdy@pleroma.envs.net

PGP: see website

  • 11 Posts
  • 16 Comments
Joined 4M ago
cake
Cake day: Jan 28, 2021

help-circle
rss

My enterprise-grade notes setup:

mkdir ~/Documents/Notes
cd ~/Documents/Notes
$EDITOR name_of_note.txt

For lecture notes, I do this:

$EDITOR "$(date +'%Y-%m-%dT%H:%M:%S%:z').md"

I don’t actually type out commands like these; I have alises for them. I sync my notes with git, so I don’t have to learn another tool just for notes.



I updated the “What explicitly opting out actually entails” section to further elaborate on why adding this header might not really improve user privacy.


Server side categorization for sites with ads is where this Permissions action is aimed at. What this is saying is that if an ad tries to get a cohort id from an opted-out site, it will receive a meaningless default value. This knowledge is for the benefit of advertisers, not webmasters.

The solution is not to include trackers on your page in the first place, such as third-party ads. Permissions-Policy applies to the page requested and its contents.

As for cohort calculation, things are messy. If one site is opted out and another consequently has a greater weight, the implications wrt. fingerprinting are vague. Opting out doesn’t necessarily reduce a user’s fingerprint. FLOSS is one aspect of a user’s interests, but there are countless others. There is/was no legal or technical obligation to obey either the DNT header or this permissions-policy header (strictly for the purposes of cohort calculation), since the latter isn’t standard usage of the permissions-policy header and the former isn’t even a standard header in the first place.

A coordinated effort is better spent getting users off Chrome than getting upstream software and webmasters to add this band-aid to their sites.


I updated the article to explicitly address this; check the “What explicitly opting out actually entails” section.


Lots of people have been spreading the often-unnecessary advice to add a Permissions-Policy response header to their sites to opt-out of Google’s FLoC, and some have been going so far as to ask FLOSS maintainers to patch their software to make this the default. When discussions got heated to the poi…


I wrote about both issues, and why Matrix isn’t a perfect solution, previously: part 1, part 2. Starring WhatsApp, Firefox, Signal, XMPP, Email, and Matrix.

Also discussed on Lemmy: part 1, part 2.

Signal’s problem is being a closed platform; Matrix suffers primarily from complexity. Both enable dependence on a single small group, and therefore enable user domestication. That being said, Matrix is considerably less bad than Signal.

For large public rooms, IRC continues to be the best option. All its issues are client-side; IRCv3 supports history, multiple devices, authentication without NickServ, and even typing notifications. All these features are supported on Oragono. For small, private E2EE rooms, all existing solutions have major trade-offs.


Qt Flatpak apps running outside of a KDE session (I run Sway) can’t even use Breeze-Dark. The only dark theme they have available is Adwaita-Dark, and you can only use that if you add a commandline parameter to override the theme with an envvar.


Wiby - Search Engine for the Classic Web

A search engine that’s optimized for surfing/discovery rather than finding specific information. Focuses on simple, non-commercial, hobbyist sites reminicent of the “old web” without much CSS/JS…


I’m not really sure if Lemmy is a good fit for Wiby, since it does use a lot of “CSS for cosmetic effect” (which is advised against on the submission page) and it only looks good in modern browsers. It’s a complex piece of software, not a simple webpage reminiscent of the “classic web”. Wiby is better for discovering really simple “Web 1.0” sites I can open in Dillo or edbrowse. Click “surprise me…” a few times and you’ll get the overall vibe.

Then again, I didn’t make Wiby so I don’t know this for sure.


Thanks! Glad people found it useful.


I love Wiby! Runarroo also features a random hit from Wiby every now and then, which I think is the perfect use-case; Wiby is better for surfing than searching.



I follow peoples’ gemlogs, browse geddit, and host my own Gemini capsule which has pretty much the same content as my Web site.

I love the information flow; one line has exactly one meaning (heading, link, bullet, blockquote, or preformatted-text toggle), and that meaning doesn’t change halfway through the line. Different clients can render pages with wildly different appearances; presentation is up to the user agent, not the author.

All it’s missing IMO is optional compression and some sort of hint to give screenreaders around preformatted blocks to let them know whether or not to skip them. The former could help in low-bandwidth settings and the latter would improve accessibility.


Most “alternative” search engines to the big three (Google, Bing, Yandex aka GBY) just proxy their results from GBY. I took a look at 30 non-meta search engines with their own crawlers/indexers to find actual alternatives. …


Most “alternative” search engines to the big three (Google, Bing, Yandex aka GBY) just proxy their results from GBY. I took a look at 30 non-meta search engines with their own crawlers/indexers to find actual alternatives. …


  • Official docs might mention them
  • Static analyzers/linters typically have docs in which they describe rationales for their rules
  • Crack open a book or two
  • Subscribe to RSS feeds for blogs from reputable people involved in the language’s development

I’ve been using a self-hosted webmentiond on my own site for about a month and a half, and I’ve loved the experience so I thought I’d share. Deploying is easy; it’s just a single statically-linked binary and an assets directory for the web UI…



Reddit’s search result RSS feeds and Lobsters have a similar feature, FFIW.


I wrote a follow-up to a previous post, “Whatsapp and the domestication of users” (previous discussion)…

13

I wrote a follow-up to a previous post, “Whatsapp and the domestication of users” (previous discussion)…

6

I wrote an article in a similar vein a month ago: Becoming physically immune to brute-force attacks.

Stuffing the planet into a 100%-efficient furnace isn’t enough to crack a 256-bit key.

I’m building off those ideas in what will be a little collection of programs that measures and generates passwords given physical constraints of a brute-force attacker (energy, power, mass, etc). The collection isn’t really a collection yet; it currently contains almost one complete program: https://sr.ht/~seirdy/MOAC

Edit: URL typo


In addition to LanguageTool, you can also check out RedPen. Be warned; it has a lot of false positives, and isn’t very intelligent.



FWIW, this is also a feature in Signal, another closed platform I covered.


Author here; thanks for the feedback. I just updated that section to address this. Diff.

I can’t believe I forgot about free calls; my parents and extended family depended on that for international calls. VOIP services were already a thing, but I’m not sure how many of them were both gratis and better for user freedom than WA.

Ping @copacetic@lemmy.ml

(F1rst P0st!)