~b @torresjrjr@qoto.org

The current state of printers, man... I just want to print one fxxxxxx sheet of paper.

I can't find the printer on my network.
The printer is offline.
The printer's driver is outdated.
The printer "requires" an unholy amount of bloatware, 5+ separate applications, 3 of which occupy my taskbar.
I need to sign into a HP account to see my current printer jobs.
The printer software shows no jobs in progress.
On and on and on.

@dcz
For GUI apps, sure, good UX removes the need for documentation. But you're expecting a cli utility to be as intuitive? This is why we have man pages and wikis for even basic commands.

As for invalid emails, fair point. Though the email format is not that hard to grasp. If you're to uncomfortable with editing emails directly, perhaps you're too used to using GUI apps and HTML forms with validation. I don't want to presume too much. If you get hands on, you also have to know what you're doing, and it's generally better to aquire that skill than always using safe frontends.

@dcz
I do recognise that git send-email could be improved here and there. But I think the documentation is there and sufficient enough for most people coming from most backgrounds.

@dcz
For the record:

https://git-send-email.io/

I don't know if you've seen this. My first experience with git send-email was with this website, which explain things well enough for me that I've never had the problems you described with git send-email.

As with drafts, I've always assumed you just save your text as you would in any other text editor. In vim, I usually do something like `:w /tmp/email`, then later `:r /tmp/email`. There a probably people with mappings for this.

What you said about email patches being less than a commit, I'd say that's what `git request-pull` is for.

And for context, I use the aerc email client, which integrates nicely with all of this.

https://aerc-mail.org/

And Sourcehut too, which as you've said provides great continuity with git and email.

@mariusor
Firstly, what is the motivation behind "democratic moderation" as you describe it? Specifically, why would you want "mod courts"? It may be obvious to you, but I want to think critically in the open to allows us to see its implications.

Also, expanding the ActivityStreams vocabulary might be a good idea, before rushing and trying to shove new semantics onto existing vocab. Just some thoughts.

https://www.w3.org/TR/activitystreams-vocabulary/#dfn-flag

@lightone
Found another one via the same engine. I like the intro, better than my one.

https://www.vegard.net/welcome-to-the-fediverse/

@Seirdy
Makes me laugh how youtube-dl is probably the most cloned project in existance, at least up there with Linux.

@sotolf@fosstodon.org @vim
Read @vim's description. It's a Fediverse group. I'm trying to encourage people to use it :)

@sotolf@fosstodon.org
Nice. Care to send this to @vim ?

@Gargron
No.

That should be given a different word. "Censor" seems more appropriate, because you are locally censoring a person's existance from your timeline, not just the their posts.

Muting should strictly refer to the ignoring of one and only one's activities (primarily notes).

@namark
Behold, ropes & cords
https://en.wikipedia.org/wiki/Rope_%28data_structure%29