I think we can fix it, but I think we have to start thinking of scientific infrastructure as something to be immediately invested in because it impacts the lives of all the people that do science with us, something that we invest resources in & organize with our colleagues about.
constantly asking the question "why is it like this" and then fishtailing around an ever-elusive conclusion that makes you believe it is impossible to fix, rather than making cumulative progress on a communications problem is -- precisely -- an infrastructural problem
time spent plinkoing a paper down a journal hierarchy is an infrastructural cost.
reinventing rigs is an infrastructural cost.
asking questions into the Twitter void is an infrastructural cost.
losing data is an infrastructural cost.
I wish ppl started seeing this^ - getting derailed from whatever anyone "wanted" to study by the ethical immediacy of scientific infrastructural deficits - as a cost of being deinfrastructured. maybe one step towards framing the journal system et al as everyone's responsibility
in the event of my death, I am hereby specifying my file format https://twitter.com/json_dirs/status/1386060560333111296?t=s0C3ivH0IAQlF_5ZKu95vw&s=19
i, for one, would not trust ppl trying to upload me onto the internet if they had a wordpress homepage.
if they missed it, might be useful ethical grounding for neuroscientists
My latest short story is called "Lena". https://qntm.org/mmacevedo
presenting longRpipes, autobanned from CRAN
@GriffinEvo@twitter.com @email@example.com who is going to write the `longRpipes` package that lets you chain a bunch of them together for emphasis
iris %>%>%>%>%>%>%>%>% prcomp
Key to this vision is to move some currently app-specific parts to the core communication layers of the stack.
Besides Identity, Community, a set of common Relationship types this would include a discovery mechanism for Modules, their Capabilities and compliance levels, plus ways to integrate/invoke them into your message-oriented service/app design. Something like that.
Imho if we had a bit more of this the fedi could make big strides forward
This is roughly the outline of what I call "Community has no Boundary" paradigm. Social networking reimagined.
In this vision it is not needed to make 3yr programming all-or-nothing gambles on a full-blown social platform and growth-hack until the network effects start to work in your favor.
In fact the entire idea of "packed present" feature-complete walled gardens starts to make less sense, when you can have tailored unique experiences.
This web has both Identity and Community embedded in its fabric, not tied to any app/platform.
Communities as they exist IRL are intricate social structures. They intertwine, overlap, interconnect, nest etc. They have common relationships between them, and personal relationships that differ per individual. These relationships have semantics, they are meaningful and determine the role a group or individual has to other 'actors.
classic pirate instinct to just fork the shit out of something on sight so there are more seeds
that is to say I am gonna tread carefully before I try and PR into anyone's delicate ux space, it's just polite
and as much as it sucks stuff like vue and material UI do make shit easier to make, but all that ux tech is built by $$$ for their purposes. would love to hear of a healthy ux element framework tho, have looked but am always reminded of the limit of my view
there is this fascinating history of interface improvement aversion that runs through even some of the more radical internet freedom communities I know. syntax purism, "you shouldn't want this," etc. but the symptomatic problems then take up most of the discussion space
the thought "what if we made fedi better than Twitter," I think, on a very practical level to me amounts to "can we make the ux better and do stuff that twitter can't that is easy and also useful." like technically AP definitely can, but how available is it to someone looking for a dang app
idk if a protocol for interfaces for controlling interfaces that control protocols makes sense but I look around at a lot of the wasteland of cool LD And semweb projects that make the internet look like magic but never made it out of a poorly coded iframe implementation in the mid 2000s and get 2 wonder what was missing
if I am gonna learn anything abt the way code and society work I'd probs pick social media and dating apps as two examples of how we are thinkin right abt protocols n all that for technical right to fork, but we might b missing the important of making interfaces easy to fork. ig that's what being the literal point of interaction is all about
systems/neuro & digital infrastructure, new here b kind!
crossposting to/from @firstname.lastname@example.org , except for toots containing !/
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!