@Seirdy I think a lot of it was authors being given customization options that are impossible or near-impossible to use tastefully: blink, marquee, background images, that sort of thing.

(Not entirely what you're asking, but I just had a flashback to "myspace code", giant piles of CSS people would copypaste into their myspace profiles. Sometimes, they even knew to remove the old stuff when changing it instead of just appending more after it to override it.)

I suspect the answer is no, because asking every host to implement both USB and PCIe seems more reasonable than asking every card to implement them.

Show thread

Why are specs hidden behind paywalls D: I just want the answer to one silly question, I don't want to form a corporation and join the PCI-SIG because that sounds both expensive and exhausting.

Anyway, M.2 has a bunch of unrelated protocols stuffed into one connector. Is the host required to implement all of them, or can it just say "nope, I'm a tiny microcontroller pretending to be a computer, I speak USB and I will ignore anything on the PCIe lanes"?

@dawning_sun See, the problem is that I send so few DMs that I will have lost that habit by the time I send another one :p

okay, yeah, the thing where you send a DM and it shows up on your home timeline is *extremely weird and panic-inducing*

@Seirdy @winduptoy (fwiw you did get me all self-conscious about my inline link text, I just cleaned up all the particularly bad ones that didn't take significant rewriting, and will do some more later when I'm not trying to edit HTML on a phone)

@Seirdy @winduptoy Okay, yeah, I agree with all of those changes. I just don't extend that to "people can't be trusted with inline links at all".

@Seirdy @winduptoy I assume you meant to link to gemini://seirdy.one/2020/11/23 there; the linkification seems to have gotten lost. The irony is not lost on me.

I honestly think the web version reads better for having the links inlined. The separate-line links break up the flow of the Gemini version too much.

On WCAG: are you referring to w3.org/WAI/WCAG22/Techniques/f? I certainly agree that "read more" and "click here" are bad link text. I don't see "[Seirdy's site] is pretty cool" as bad link text, and that's probably how I would write your example.

I don't think I understand why Wikipedia-style inline links are bad, and I think most of my argument here hinges on them being good. Can you expand on the problems with them?

@Seirdy @winduptoy but... links *aren't* context-free. This link is here for a reason, it's related to the surrounding text in some way, and taking it out of that context just means you have to restate the context so the reader can do the work of connecting it back to that.

Sampling some inline links from my own site (mostly handwritten HTML with some minor preprocessing for tedious things; heavily inspired by Gemini design principles and I did try to use Gemtext for a while before settling on this):

Links that could trivially become whole-line links:
> Fediverse: [@emily]
> [Source.] Requires Python but no additional dependencies.
I do have a lot of whole-line links or links that could be trivially changed to that. I prefer this style, but it is a stylistic choice and I don't think either is objectively better. Given medium limitations, I'd conform and get over it.

Links to context, not necessary for comprehension:
> So [an internet person] said something about making tarballs executable
This link points off to a thread on a Misskey instance and *ugh* I had not been to a Misskey page in a while and had forgotten how slow it was.
But at the same time, I don't want to copy the linked thread here, at best it's a tangential distraction. I certainly don't think the link deserves its own line; in Gemtext I probably would've omitted it entirely. But I can see value in this sort of thing for e.g. replies to other people's blog posts.
One could argue these don't really need to be here at all. Is it bad to include links that aren't necessary but may be of interest? I don't know, I had not considered that before now.

Links to context that may be necessary for comprehension:
> in the same way as e.g. [AppImages]
> So I picked up a [Solo Hacker]
> it should suspect a [replay attack]
These links are here because these are things you'll probably need to know about to understand the surrounding text. They're the same sort of philosophy as Wikipedia inter-article links: "describing this is out of scope for this article, and if you're reading this there is a good chance you know what it is already, but if not, see here". The link text *is* the link description; if I started describing the contents of the linked page, I'd be adding a bunch of extra stuff the reader may already know, and not doing that was the reason I included a link in the first place.
One could argue that these could be footnotes. They could. They're not because of the usability concerns I expressed earlier.

Links that are there to show the thing in wider context, but I duplicate the relevant part in the article:
> The [tar file format] has no archive-wide header, only per-file headers
> that has the side effect of [being skipped during extraction without causing an error].
> Conveniently, [it's already there]. It's just totally undocumented outside of a comment in this one file.
I do this a lot for referencing code from other people's projects: "here's the part we care about, here's where I got this from". I always duplicate the code immediately afterward. There is no reasonable place to put these links except adjacent to that code. One could probably argue for it being its own line, more visually attached to the code below than to the text above. I'm not convinced but I am more convinced than for the other types of links.

So clearly we disagree on something in here, but I'm not really sure exactly what, because your thing is just "it's always more readable" and my thing is just "no it's not". How would you write these links - particularly the second and third types - in a Gemtext-like format, and in what ways do you feel they're an improvement?

@winduptoy Footnotes[1] do[2] interrupt the text[3] though, and have objectively worse usability than correctly-used links with tasteful formatting[4]: if I do want to go read more about the thing that's been referenced, I have to jump to the footnotes section and *then* click the link I want, hopefully having remembered its number and not losing it in the pile of adjacent links.

Inline links were a *brilliant* invention: a realization that there are suboptimal things we did due to limitations of paper, and we don't have to repeat the same choices in a new medium if they don't make sense there.

[1] like this one
[2] and this one
[3] hi
[4] Yes, many HTML pages get that horribly wrong. It's possible to do gemtext poorly too. This doesn't matter if you're the one *writing* the content, just don't do it wrong.

amazon being bad 

> your thing will arrive Sunday
> your thing will arrive by 8pm today
> your thing will arrive by 10pm today
> your thing hasn't actually shipped yet, but no worries, we won't charge you until it does (but we already did when we claimed we shipped it)

a bunch of people were talking about the antikythera mechanism today but as far as I can tell kythera did nothing to deserve this

@flamingspork I explicitly *unfollowed* a bunch of people recently for spamming my timeline with undirected queer rage. I continued following you, because I've enjoyed everything you've written for exactly these reasons. It's fun and adorable and it makes my brain do the dopamine thing. I'm not reading them for a reminder of all the things that are wrong with the world. If I wanted that, I *would* read something else.

Is it privilege to be able to not experience problems that other people experience? Absolutely. But it's the kind of privilege where exercising it doesn't hurt the people who don't have it - the same category as healthcare, for instance. Nobody ever says "I broke my arm but I'm not going to the hospital in solidarity with the people who can't go to the hospital", because that's ridiculous, and helps nobody.

It's ridiculous, in the same way, to suggest that the mere existence of happy fiction is somehow detrimental to people who can't relate to the happy parts.

@Jessasaurus nah, they do not make it obvious at all, in fact the docker-compose.yml they provide explicitly points at the wrong .env.production :D

mentions of bigotry and sex, abstractly 

@flamingspork going back to that particular tweet, I think the fallacy they're committing is that portraying something positively is not the same thing as portraying it as more positive than everything else. It totally can be written that way, even accidentally, but it isn't automatically that way.

A portrayal of a happy straight couple is not inherently homophobia; a portrayal of a happy gay couple is not inherently heterophobia. The only people who do see it that way are bigots who are offended by the existence of people who aren't like them.

Similarly, a portrayal of a couple doing non-sexy things is not a condemnation of sex, and a lack of distinct queer rage is not an implication that people who are expressing that rage are wrong.

@flamingspork as a fellow trans lesbian, I hereby give you permission to rage exactly as much as you see fit.

Seriously though, even in rageworthy worlds like ours, it is okay to write things that are not rage. Your story does not need to be a Statement on something unless you want it to be.

@Jessasaurus (or add a separate user in postgres if you want, I didn't bother because it's the only thing on that postgres instance)

@Jessasaurus did you notice that the .env.production.sample in that repo is completely wrong for that docker-compose.yml? Because it is :)

I just tried doing one from scratch and got it to work, with:

docker-compose exec -u postgres db psql -c 'create database mastodon_production;'

and in .env.production:

-REDIS_HOST=localhost
+REDIS_HOST=redis

-DB_HOST=/var/run/postgresql
-DB_USER=mastodon
+DB_HOST=db
+DB_USER=postgres

and from there you should be able to do the normal setup thing:

docker-compose run web bash
RAILS_ENV=production bundle exec rake mastodon:setup

nerd confusing herself 

@steffo helping~

Curious, in what situation does it break? I assume it's just something I don't do.

Show older
Mastodon

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!