this post was submitted on 05 Sep 2026
410 points (99.5% liked)

196

6806 readers
1766 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 2 years ago
MODERATORS
 

alt textScreenshot of a Twitter post by @sirocyl: "what's a good hex editor - preferably for windows - for annotating structs and stuff? I'd normally use audacity but I figure there's gotta be something better for this." Attached to the post is a screenshot of Audacity showing two tracks, one of a binary file being interpreted as audio, zoomed-in at the sample level where individual bits can be edited, and a label track with labels such as "IMGDATA_MAGIC", "IMGDATA_FILE_NAME (1)", "Width (1)" and "Height (1)".

you are viewing a single comment's thread
view the rest of the comments
[–] AI_toothbrush@lemmy.zip 3 points 1 day ago (2 children)

Yeah but the problem is from i understand it lacks exactly the features that would make it a daw. If it had midi and automation i think i could actually use it as a daw. I might check it out one day but they only had version 4 as an appimage last time i checked.

[–] RedSnt@feddit.dk 2 points 19 hours ago

I was of course joking. One of the main guys at Cockos that develops Reaper is Justin Frankel the man behind Gnutella, Winamp and Shoutcast and a few other fun projects, so I'd expect them to still be ahead for a little while.

[–] Paulemeister@feddit.org 4 points 1 day ago (1 children)

Check out the videos of their lead tentacrul. He also did the Muse score redesign. As I understood, they are moving slowly as the codebase is a mess. First they cleaned up the toolbars, changed to non destructive clip editing then switching to qt improved it to the state it is now in. As I understood it, the audio engine is shit so they plan to rip it out and redo it. Midi support is a highly requested feature and I think it will definitely come, but only after everything that's Audacity is used for is the best it can be. Then the DAW features will be build (they already include tempo, time signaturea etc)

[–] AI_toothbrush@lemmy.zip 1 points 1 day ago

Oh wow i will watch it and that sounds very good. To be honest even if they only add midi i would already use it for some tasks over other daws but i understand that its a lot of work to fix up such an old codebase. Still, maybe in the next few years we will get a linux daw that isnt a chore to use.