@ajuvo good n8
@amolith Maybe DnsFriends? What exactly is the purpose, something like the free part of OpenDNS or to provide alternatives to 18.104.22.168 and 22.214.171.124?
That's still unfinished though, why do I always need bleeding edge features?
Time for bed I guess, maybe the edge looks less bleeding tomorrow... ;-)
@federicomena for two selectors that have the same specificity, the latter one should be selected. So that either needs to be included in your specificity calculations, or the selectors should be picked by reverse order of definition, instead of a randomized iterator (which is a nice feat by rust btw)
Last Tuesday #Beast 0.15.0 was released.
This is most probably the last release that supports the #Gtk+ Beast UI. We have most of the bits and pieces together to move towards the new EBeast UI and a new synthesis core in the upcoming months and will get rid of a lot of legacy code along the way...
@nobru Thanks for the link! That was a long but very eye opening reading.
I kept checking back all the things Clay talks about really already existed in 2003, incredible insights given this was 16 years ago.
@openmastering thx, great!
Beast version 0.15.0 is released.
#Beast is an LGPLv2+ music synthesizer and composer (#DAW), for #Linux.
This release supports Jack as PCM driver and the experimental Ebeast frontened got many style updates, play position pointers and supports the Space key.
Here's a suggestion I've picked up from the Podcaster scene. Create a public Amazon wishlist, that you link to from your Website or Mastodon profile. At $10, it's possible that some community member browses the list, steps up and buys it for you and then it gets removed and shipped to you...
@kepstin does libsndfile handle those 4G+ files?
@ebarrett I'm guessing you could force things like this:
* Delete the GitHub repo (but keep a full local copy)
* Fork the upstream repo into your account. If needed, rename into your deleted repo.
* Force push your local repo into the new repo in your account.
@federicomena In case this is not in one of your tabs yet ;-)
Great read: https://alexgaynor.net/2019/aug/12/introduction-to-memory-unsafety-for-vps-of-engineering/
Firefox becomes unresponsive for several seconds, burning CPU. Yesterday I decided to watch FF in gdb and saw that it's accessing thousands of font files , each causing a "SIGSYS, Bad system call".
Can anyone guess why FF gets SIGSYS, failing to access a world-readable file? Bug report: https://bugzilla.mozilla.org/show_bug.cgi?id=1566053
DSP + UI developer on the Beast DAW, Free Software author + advocate, contributor to ALSA/GNOME/procps/LibreOffice/Mediawiki.
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!