@ripper Ich glaub bei vielen menschen auf willhaben ist das so eine kognitive unvereinbarkeit zwischen "ich habe (un)definierte ängste meine adresse einem fremden menschen preiszugeben" und "ich muss meine adresse preisgeben, sonst werde ich $objekt nicht loswerden", die sich dann in so zögerlichem, widersprüchlichem handeln manifestiert. (Und dann gibts natürlich auch die menschen auf willhaben die einfach komplett verpeilt sind, ohne jegliche kognitive besonderheiten haha :))

Simon Repp boosted

Hi all! 🌊 Recently moved to @dcwalk from @dcwalk@mstdn.io so doing a here.

I am a researcher and designer interested in how to build lasting and transformational alternatives to existing infrastructures, in the past this has included data stewardship, networks, and movement organizing. Now I am focused on the practices and language of low carbon networking.

Currently packing up my life and moving across the country, hoping to camp and spend some time offline along the way ⛺

A fork of the rust borrow checker that grants three extra mutable borrows in addition to the single one you normally get, so it's not so hard on the dev :thinkhappy:

Simon Repp boosted

@EU_Commission These claims go entirely against the consensus in the field.

The projected growth in AI, blockchain, IoT will lead to a massive rise in emissions, not a reduction. And contrary to your claim, none of these technologies is essential in reducing emissions.

Quantum Computing is unlikely to be mainstream by 2050 and has currently no promise of energy efficiency. There are much more promising compute technologies. Space-based services cause emissions in the upper atmosphere which leads to additional warming of those layers, making global warming worse.

Please check with experts before posting things like this.(fwiw, I am an expert in low-carbon and sustainable computing so green & digital transition is my area)

Simon Repp boosted

In the summer of 2009, The Swimming Cities of Serenissima sailed from Slovenia to Italy and made its way up the Grand Canal in Venice.

Brooklyn artist Swoon (a.k.a. Caledonia Curry) conceived the Swimming Cities' shanty boats, built from salvaged junk as a collective artwork.

Her work was included in Radical Seafaring at The Parrish Museum of Art, in 2016, which likened work created on the water by contemporary artists to the Land Art movement of the '60s/'70s;

Photos by Todd Seelie.

@ccohanlon I saw this featured some ten years ago in the essayistic documentary "Empire me" (youtu.be/Wd1ElpVV300). There's that part where they float into Venice and Dark Dark Dark perform "Something for myself", their singer sitting at the bow of the boat on a piano ... goosebump material. Such a beautiful endeavour!

@apparentlymart Hey thanks those are some great insights! The time one needs to dedicate (especially in an open source project) to look at contributions is an interesting additional factor. It's also somewhat exemplary of our entire dilemma: We're all so short on (human) time to dedicate to projects and tasks that we really care about because most of us are struggling to make ends meet in the daily capitalist treadmill (although we'd be so many minds eager to work on the relevant stuff), while on the other hand machine labor and services are thrown around at dumping prices with all the externalized damage wreaking havoc on the environment. Either way, good to hear you and your colleagues are putting thought and action into this in your projects, keep it up! \o/

@jens Ah yes that makes sense thanks! I've recently observed that part of this piecemeal commiting approach is also encouraged through review workflows that platforms implicitly dictate, e.g. using the review feature on github and then a process comes out of it where single review comments are adressed in single commits and so on, and of course each one-line fix triggers the ci pipeline anew, etc. ... oof ^^

@jens Do you mean the part about squash merges in the sense that people don't want to bother to manually structure their commit history for PRs (interactive rebase etc.), or in some other way?

Simon Repp boosted

Du arbeitest in der Werbebranche aber hast Bedenken, wass du da überhaupt machst?
@peng sagt dir, wie du dein Potenzial besser nützen kannst:

@giffengrabber No objections there that this needs to be fixed at the root as well eventually, we've been playing sustainability whack-a-mole for long enough now ... :(

@underlap Also a good point, although the road of fighting complexity with complexity is a slippery one of course :), probably depends a bit on the language and technology how feasible it is to determine a reliable dependency graph for conditional testing.

@underlap Flakeyness and maintenance cost is an *excellent* point! Come to think of it I've seen multiple environments in which e.g. the UI tests for a web service were just officially known to be broken (over months!), yet they would be run on every single change in every PR throughout that entire time - and even re-run multiple times as it was configured to just reattempt failing tests a number of times. So besides the environmental cost, this whole stuff might even have had a detrimental effect on productivity, given that it completely ruins your confidence in code quality and sends you off chasing CI issues on a regular basis instead of working on your actual codebase. /o\

@cinebox Good to hear! Having CI in general is not the issue really. It's foremost about how we can employ it in less wasteful and more thoughtful ways. (which is also not to say that some people are not already doing this :))

hot take 

@forever I agree that being able to build and test everything locally etc. is always the gold standard to seek, there are instances though of course where this is hard or impossible, e.g. multi platform releases, supporting obscure platforms, etc., there a CI does make sense to me.

@maddiefuzz I've unfortunately seen it being used indiscriminately and without measure to a significant degree by now. Thumbs up if you're putting more thought into it and I hope there's more that follow your practice!

@iitalics That's a very valid point and I agree (I've seen this too, exactly like that, in practice). I think that in parallel to that, the fetishization also exists though, as in for instance thousands of utility libraries in the npm ecosystem that boast a README with 20 CI-powered badges, where the codebase is a mere 100-something lines of trivial, side-effect free javascript (but there's a spectrum of examples on all scales of course). One of the main signs why I think this has gotten out of hand on a cultural level is a (at least perceived) lack of open controversy about it, hence my nuding this. :)

@jens Thumbs up and fully agree on «it's complicated». There's a spectrum of solutions we will have to look into and combine, some of which I believe will have to hurt us too, as in needing to sacrifice some amenities here and there if we are to keep things reasonable on a global scale. Whatever the answers are, "compute first, think later" (or even "never" as I see just as frequently) is not a luxury we should grant ourselves anymore.

I think contemporary development culture has a CI-fetishization problem and this should be talked about a lot more.

I don't know if this is an unpopular opinion or just not interesting to a lot of people (at least I don't see it pop up much in my feeds for whatever reasons), but the rising amount of commit-triggered senseless cloud computation I see in recent years is really worrisome to me. I can appreciate the utility of a thoughtful automated process that thoroughly checks an entire release before it rolls out on big critical infrastructure, but what I see around me is so often overblown pseudo-testing that provisions entire serverfarms to crunch numbers for half an hour everytime any dev at an org commits as a much as a fix for a typo on some random work-in-progress branch. In the face of our existential climate emergency I can only consider this practice completely mindless, and complete madness. We can not keep doing this.

Show older

We are an instance for discussions around cultural freedom, experimental, new media art, net and computational culture, and things like that.

<svg xmlns="http://www.w3.org/2000/svg" id="hometownlogo" x="0px" y="0px" viewBox="25 40 50 20" width="100%" height="100%"><g><path d="M55.9,53.9H35.3c-0.7,0-1.3,0.6-1.3,1.3s0.6,1.3,1.3,1.3h20.6c0.7,0,1.3-0.6,1.3-1.3S56.6,53.9,55.9,53.9z"/><path d="M55.9,58.2H35.3c-0.7,0-1.3,0.6-1.3,1.3s0.6,1.3,1.3,1.3h20.6c0.7,0,1.3-0.6,1.3-1.3S56.6,58.2,55.9,58.2z"/><path d="M55.9,62.6H35.3c-0.7,0-1.3,0.6-1.3,1.3s0.6,1.3,1.3,1.3h20.6c0.7,0,1.3-0.6,1.3-1.3S56.6,62.6,55.9,62.6z"/><path d="M64.8,53.9c-0.7,0-1.3,0.6-1.3,1.3v8.8c0,0.7,0.6,1.3,1.3,1.3s1.3-0.6,1.3-1.3v-8.8C66,54.4,65.4,53.9,64.8,53.9z"/><path d="M60.4,53.9c-0.7,0-1.3,0.6-1.3,1.3v8.8c0,0.7,0.6,1.3,1.3,1.3s1.3-0.6,1.3-1.3v-8.8C61.6,54.4,61.1,53.9,60.4,53.9z"/><path d="M63.7,48.3c1.3-0.7,2-2.5,2-5.6c0-3.6-0.9-7.8-3.3-7.8s-3.3,4.2-3.3,7.8c0,3.1,0.7,4.9,2,5.6v2.4c0,0.7,0.6,1.3,1.3,1.3 s1.3-0.6,1.3-1.3V48.3z M62.4,37.8c0.4,0.8,0.8,2.5,0.8,4.9c0,2.5-0.5,3.4-0.8,3.4s-0.8-0.9-0.8-3.4C61.7,40.3,62.1,38.6,62.4,37.8 z"/><path d="M57,42.7c0-0.1-0.1-0.1-0.1-0.2l-3.2-4.1c-0.2-0.3-0.6-0.5-1-0.5h-1.6v-1.9c0-0.7-0.6-1.3-1.3-1.3s-1.3,0.6-1.3,1.3V38 h-3.9h-1.1h-5.2c-0.4,0-0.7,0.2-1,0.5l-3.2,4.1c0,0.1-0.1,0.1-0.1,0.2c0,0-0.1,0.1-0.1,0.1C34,43,34,43.2,34,43.3v7.4 c0,0.7,0.6,1.3,1.3,1.3h5.2h7.4h8c0.7,0,1.3-0.6,1.3-1.3v-7.4c0-0.2,0-0.3-0.1-0.4C57,42.8,57,42.8,57,42.7z M41.7,49.5h-5.2v-4.9 h10.2v4.9H41.7z M48.5,42.1l-1.2-1.6h4.8l1.2,1.6H48.5z M44.1,40.5l1.2,1.6h-7.5l1.2-1.6H44.1z M49.2,44.6h5.5v4.9h-5.5V44.6z"/></g></svg>