cancel @cancel@merveilles.town
┌┐┌┐·┌┐┌┐
└┘└┘·└┘└┘ ᴬᴹ
Joined Dec 2018
cancel
boosted
@neauoire ah ok, I think you meant to restore the file to its previous state, but you somehow pasted an earlier version back in
Another full-featured third-party client for Slack has appeared: https://shrugs.app/
Looks good, too! (Mac only)
@neauoire why did you overwrite readme.md in the sr hut version with a bad old version of the readme file? what happened?
@neauoire And it means you have to leave the GitHub 'master' branch as stale forever... not good
@neauoire Deleting and recreating the readme file is kind of gross, it permanently ruined the git blame history on that file :/
@neauoire the GitHub repo for orca-c is out of date... if you want to direct people to another site but keep the GitHub repo working, just disable the issues and wiki, create a new branch (like notice-moved), modify the readme in that branch, and set that branch as the default when visiting the repo in a web browser.
Then the real 'master' can be left alone with the real repo contents, to avoid breaking other people's guides etc. on the internet.
Version 0.4.25 of Ripcord, the Slack and Discord client, released: https://cancel.fm/ripcord/
Updated support for Slack username & password sign-in to work again. Opening accounts tab on launch now optional. And it got smaller and faster. Changelog: https://dev.cancel.fm/changelog
Posted Ripcord preview test builds for the upcoming 0.4.25 version: https://dev.cancel.fm/wiki?name=UpcomingChanges
Ripcord is being passed around social circles for young children today, because I'm being harassed multiple times per hour on the internet by 10-14 year old American children, with all of the things you would expect that entails.
cancel
boosted
LMMS Dev Rant
Here is the wet/dry knob in 2008 (12 years ago now!) using the correct 0-1 range, being changed inexplicably to -1,1 in a huge unrelated commit: https://github.com/LMMS/lmms/commit/f39c9641abd9f223f16084d41c70a7445b008a22#diff-4707ec0d66434cc27ae2716b4a33c04fL46
cancel
boosted
LMMS Dev Rant
The wet/dry problem still persists!
https://github.com/LMMS/lmms/blob/a1b355828e347b8e7fca8118873fc834953c1d67/src/core/Effect.cpp#L47
All my controversial PR did was change that -1 to a 0.
cancel
boosted
LMMS Dev Rant
It's been 3 years, and I'm still bitter about my development experience with LMMS.
I was looking at their DSP code, and found that most plugins were not handling wet/dry value knob properly. I realized it was a longstanding bug. The wet/dry knob should have been writing a 0-1 value, but it was writing a bipolar -1,1 ranged value like a pan knob. I even looked at the git history and found at one point it was set to be 0,1, but was mysteriously changed to -1,1 in a massive commit with sweeping changes. It was definitely a bug. I could see plugins mishandling it and I could hear it too.
It was a simple PR (I changed like one line of code), and I made my case. What ensued was a huge chaotic discussion. Apparently, the bug was there too long and changing it would "break workflow", and also "sometimes it sounds cool".
I understand the concern about backwards compatibility, but come on! How can you expect to compete with anything commercial when your wet/dry knob can mess with phase + gain staging in unpredictable ways? Like, what?
My PR was closed but not merged, and AFAIK the bug still persists after all this time.
Don't let the eye candy fool you: LMMS objectively sounds like crap.
Forgot to add non-visual caption to this one. It's a screenshot of a Mac OS 9 folder with a readme file in it titled "Discipline has been Obsoleted"
cancel
boosted
MNT Reform (open hardware laptop) campaign is live: https://crowdsupply.com/mnt/reform
And here's the Launch Announcement:
https://crowdsupply.com/mnt/reform/updates/the-campaign-is-live
Thanks to everyone who helped and supported us to make this happen.
My thoughts on Zoom acquiring Keybase?
Here's a screenshot of the Keybase client in March 2020, the last time I tried to use it. It had turned itself into a black rectangle after an auto-update in October 2019. It stayed that way across multiple updates. Its memory usage rose with each update. There isn't a way to quit it from the UI.
Ripcord users: some changes to Slack in the last day or two have made the username & password sign-in process stop at the validation step. Until it's fixed in the next update, if you need to re-authenticate or add a new Slack account, use the Import from Browser option instead.
┌┐┌┐·┌┐┌┐
└┘└┘·└┘└┘ ᴬᴹ
Joined Dec 2018
