this post was submitted on 11 Aug 2025
187 points (99.5% liked)

196

4228 readers
2040 users here now

Community Rules

You must post before you leave

Be nice. Assume others have good intent (within reason).

Block or ignore posts, comments, and users that irritate you in some way rather than engaging. Report if they are actually breaking community rules.

Use content warnings and/or mark as NSFW when appropriate. Most posts with content warnings likely need to be marked NSFW.

Most 196 posts are memes, shitposts, cute images, or even just recent things that happened, etc. There is no real theme, but try to avoid posts that are very inflammatory, offensive, very low quality, or very "off topic".

Bigotry is not allowed, this includes (but is not limited to): Homophobia, Transphobia, Racism, Sexism, Abelism, Classism, or discrimination based on things like Ethnicity, Nationality, Language, or Religion.

Avoid shilling for corporations, posting advertisements, or promoting exploitation of workers.

Proselytization, support, or defense of authoritarianism is not welcome. This includes but is not limited to: imperialism, nationalism, genocide denial, ethnic or racial supremacy, fascism, Nazism, Marxism-Leninism, Maoism, etc.

Avoid AI generated content.

Avoid misinformation.

Avoid incomprehensible posts.

No threats or personal attacks.

No spam.

Moderator Guidelines

Moderator Guidelines

  • Don’t be mean to users. Be gentle or neutral.
  • Most moderator actions which have a modlog message should include your username.
  • When in doubt about whether or not a user is problematic, send them a DM.
  • Don’t waste time debating/arguing with problematic users.
  • Assume the best, but don’t tolerate sealioning/just asking questions/concern trolling.
  • Ask another mod to take over cases you struggle with, if you get tired, or when things get personal.
  • Ask the other mods for advice when things get complicated.
  • Share everything you do in the mod matrix, both so several mods aren't unknowingly handling the same issues, but also so you can receive feedback on what you intend to do.
  • Don't rush mod actions. If a case doesn't need to be handled right away, consider taking a short break before getting to it. This is to say, cool down and make room for feedback.
  • Don’t perform too much moderation in the comments, except if you want a verdict to be public or to ask people to dial a convo down/stop. Single comment warnings are okay.
  • Send users concise DMs about verdicts about them, such as bans etc, except in cases where it is clear we don’t want them at all, such as obvious transphobes. No need to notify someone they haven’t been banned of course.
  • Explain to a user why their behavior is problematic and how it is distressing others rather than engage with whatever they are saying. Ask them to avoid this in the future and send them packing if they do not comply.
  • First warn users, then temp ban them, then finally perma ban them when they break the rules or act inappropriately. Skip steps if necessary.
  • Use neutral statements like “this statement can be considered transphobic” rather than “you are being transphobic”.
  • No large decisions or actions without community input (polls or meta posts f.ex.).
  • Large internal decisions (such as ousting a mod) might require a vote, needing more than 50% of the votes to pass. Also consider asking the community for feedback.
  • Remember you are a voluntary moderator. You don’t get paid. Take a break when you need one. Perhaps ask another moderator to step in if necessary.

founded 7 months ago
MODERATORS
 

Affirmations to Computer

@onehundredninetysix

you are viewing a single comment's thread
view the rest of the comments
[–] drosophila@lemmy.blahaj.zone 6 points 1 week ago (5 children)

Does anyone here have any ideas about how computer interfaces should work? Or, in other words what sort of features would you want in an 'ideal' (for you) computer system?

I've been thinking about this for awhile, and I have some wishes:

  • A scrolling/tiling window manager like Niri.
  • A rich / hypertext format that's more powerful than markup but less powerful than HTML + CSS.
  • A terminal that's capable of outputting and rendering the above format: tables, collapsible sections, links, etc.
  • Some sort of unified UI that combines a file explorer, document viewer / editor, and terminal.
  • A terminal / scripting language that's more discoverable than what we have. Perhaps by using a noun verb format instead of a verb noun format. Combine that with a ZSH-like (or IDE-like) autocomplete for command options, but add a small text description to each option and allow the user to do an incremental search of this text (with synonyms) by pressing a hotkey. These two things make interacting with files a little bit like right clicking (by listing valid operations for a given type of object) and a little like doing a text search on a settings menu, respectively. This could be accomplished without giving up the power of linguistic composition.
  • A terminal / scripting language that's better than bash (not a high bar), straightforward and simple, and somewhat fast to evaluate (as far as interpreted languages can be fast), but not super complicated under the hood like Python is.
  • A series of linked wiki articles written in the above mentioned markup language, stored locally, that tells you how the OS works and how to use it. Instead of having to go to an external website to find out the steps your init process takes to start your computer, you read a plain english document describing them, with hyperlinks to the corresponding articles for the processes it interacts with. Like man pages but answers "how is it configured, and why that way", rather than just "how do I configure it". Some of these pages, or portions of them, might need to be dynamically generated depending on what packages you have installed. The pages should be organized such that the top level (or home page) give the most generalized and basic descriptions, with links to FAQs and how-tos, and the deeper you drill down the more specific and technical the articles get.
  • A NixOS-like declarative configuration system that uses config files written in the above mentioned markup language. The various config files should link to the corresponding wiki articles and vice versa.
  • An indexed full text search for the above mentioned documents (and any user generated documents).
  • A BeOs-like database file system, with tags and attributes.
  • File system level snapshots integrated into version control and the declarative configuration system mentioned earlier.
  • A plan9-like 'everything is a file' philosophy, as well as plan9's hierarchical namespaces.
  • Containerized applications and permissions using the above mentioned namespaces.

A lot of the above already exists, but only in pieces instead of in a fully unified system. Or else in a unified system that does some of these things, but not all of them.

[–] Swedneck@discuss.tchncs.de 2 points 1 week ago

honestly basically the only thing i'm missing is the ability to control things with gestures, i just want to point at the computer and turn my hand to raise and lower volume when i'm on the other side of the room..

load more comments (4 replies)