(I'm sure many have said this, but since we also don't have a good system for organizing discussion like this just another pass thru)
theres a nonzero relationship between implicit labor in science like mentorship and other forms of uncredited labor. if we are rooting out forms of inequity like hierarchy and class from science, reconsidering what labor is worthy of authorship seems like low hanging fruit.
ideally we would have a subtler means of attributing work than authorship, but until we do, genuinely asking "why not?"
I have grown a lot from others taking time out of their day to help me learn from them, and if I am honest I would not be writing what I'm writing without their extra work teaching me, so why shouldn't they be coauthors?
as I'm finding out, it's Very Normal to ask if people want to be cited for a small contribution. more active communication about re-presentation of work at many scales seems healthy, particularly when that work is traditionally excluded from scientific credit systems.
especially with contribution statements or contributor schemas, this seems like a no-lose step to take towards better credit assignment.
this seems really good, feel bad I'm just hearing about it recently.
literally no reason to not just gitter into matrix instead of starting a slack now??? implementation was the hardest problem???
I don't know. Maybe it's time to make this public.
If you are trying to learn audio programming and DSP from scratch (like, *really* from scratch), these notes might be the place to start:
They were lecture notes for a student-led 1-credit audio programming course that I taught in the spring this year, but it's now a course for everyone. Some sections are still in revision, but the main contents are mostly complete.
It's probably more low level and UNIX-centric than most of the audio programming tutorials you can find, so don't expect to learn how to make an audio plugin using JUCE or how to make fancy GUIs etc. But maybe this can be a good thing.
1. you need to know basic C and UNIX shell utilities
2. it contains math, but at most calculus level
less than three
oh em gee
love computer fantasy
meet me here on irc
el oh el oh el
sorry tbc these are "scare quotes" and not "actual quotes"
managed to make it a whole thread without talking about "what if we could also communicate about the papers instead of just publish them" but that too for later.
if i'm dreaming, i want an app where i can swap fluidly between continuous identities in different clients, be able to go talk to my funkwhale ppl and swap back over here. app feels like right level of abstraction for that so individual clients don't need to implement a bunch of xss-vulnerable mush
it feels weird being on team "desire for app not bad" but it's truly an ok thing to want to just one-tap into some conversations you were having recently with a prefetched context.
i feel like i would blow something up if i asked about fediverse/activitypub and mobile apps. i can see the browser-only crew coming a mile away but i also think something like a generic browser that represented different clients fully but also had basic hooks for activitystream/identity management/etc. could be cool. multilevel interface between protocol and client, yno.
anyway it deserves more space than a twitter thread. part of an ongoing thought spiral on engineered helplessness eg. https://twitter.com/json_dirs/status/1434974928940400640?s=20
systems/neuro & digital infrastructure, new here b kind! they/them
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!