You’d pretty much never see someone’s keyboard on a video call.
You’d pretty much never see someone’s keyboard on a video call.
I think that’s what it is, except my use of the term “block” was mostly wrong. This seems to accept them but keep them isolated, defeating their effectiveness as a way to track users across sites.
That’s great, but what’s the update? The Lemmy cross-posts from two years ago have the same title.
update: I read the post and the last paragraph talks about the full blocking of third-party cookies as a thing that’s “starting in 2024” (future tense). So my best guess is it’s that, but whatever the August 28th update was could have cleared all this up.
I think we’re focusing on different aspects. My comment was limited to the way main menus worked — “Play feature” or whatever would just about always be the pre-selected option. I was replying to this:
Those old DVD menus that wanted me to mess with extras sucked.
99% of DVD menus would have the “Play movie” pre-selected, letting you activate it with a single press of the Play or Select button.
Possibly my light/dark mode scripts. They change my Plasma theme, which is honestly most of the job, but also set the matching GTK theme, set the new theme in running Konsole sessions, do a bunch of manual sed
edits on conf files for applications that don’t follow system theming, finally restarting plasmashell
to clean up the occasional edge case where a tray icon is supposed to follow the theme but doesn’t.
It’s not for everyone, but if “collection of perl scripts” sounds like your jam, GnuPod still works for a CLI option.
I don’t think these things are universal across software, but you can often put -f
on its own, separate from other flags, or get in the habit of using the long --force
flag.
Too many options to remember and look up every time
This is a good use case for shell aliases. If you can identify a few of your use cases, you can give each bundle of options its own command.
Ctrl+F’d for this.
I agree with this, but in open source there’s an extra layer of complexity: the “I don’t care about market share” dev attitude that’s sometimes admirable and sometimes frustrating.
Agreed, it’s such a poor summary of the article that I can’t tell if it’s an intentional strawman argument.
Good point, they’d never see another nag screen.
Be so bold.
I’m not sure if you can show/hide like that, but as a workaround you can toggle auto-hiding with a qdbus command, and set a keyboard shortcut to run that.
I think OP said
if a window is fullscreen
as opposed to simply being maximized.
Oh, I’m well aware. But the criticism I’m describing is that Joplin doesn’t write and read the notes as plain .md files on-disk as its storage backend. As I said, the lock-in component to the criticism is overblown (due to, yes, the ease of export), but people also tout the Obsidian approach to storage as allowing more flexibility to also access and edit your notes collection outside of the application, not to mention the flexibility to roll your own two-way syncing solution to other devices that don’t run Joplin, edit notes there and have changed synced back to notes in the application. I use and enjoy Joplin, and wish they would add something like that.
I brought this up because of what OP mentioned re: “view and modify” notes in something like jq
. I’m sure they’d want their external changes synced back to their notes.
Whose entire life was in a… what?