#git

[cubbihue]

When you said that the unluckiest person is most hopeful, it reminded me of Nagito Komaeda. If the universe were combined, do you think he would fair well having Anti Cosmo as his anti fairy?

Funnily enough, I feel like it would be Hajime who would have an anti-fairy companion. I mean, he’s surrounded by extremely skilled people! That would attract bad luck in some way for him. Nagito wouldn’t be good food for anti-fairies. Or Fairies. Or Pixies.

...Honestly, Fairies aren’t quite sure what food he produces. It’s like a weird amalgamation of luck, desire, greed, and all sorts of emotions they can’t disentangle. Like a crockpot gone horribly horribly wrong. Eating any bit of that would make any fairy sick.

Eugh. The hell is wrong with that one.

Bitties Series: [Start] > [Previous] > [Next]

[sexy-dance-fighting]

My copy of the Danny Phantom graphic novel hasn't arrived yet, but based on isolated images I've seen without context, this is basically what happens right ???

I know they obtain cowboy hats and trauma

[essential-randomness]

I can't believe this is real and I'm physically holding it

(digital preview of @fujowebdev Issue 1 is shipping soon to our Kickstarter supporters 👀 )

[kernelbroken]

[animentality]

I've been learning to code at my new job and I work with a senior software engineer, who's a genius at this sort of thing.

But like an hour ago, he was in my office angrily murmuring, "what?! what?! what the hell?" over and over again as he furiously typed on my keyboard, trying to fix something in git.

and it's honestly very reassuring to know.

that whether you're a novice or an expert at coding... sometimes you just find yourself angrily swearing at the program for showing you the same error message a dozen times, asking why are you doing that, almost begging, really.

it was actually kinda funny, he sounded like he was about to start crying, which was literally me, two hours ago, when I initially asked him for help.

it's part of the human condition, I think, wrestling with computer programs and furiously typing in commands, only to be met with defiance.

[ogrepoppenangleaksofficial]

GIUTIGITIG IT HAND HANNDD WARNING DONT HADNN!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

[mostlysignssomeportents]

Cloudburst

Enshittification isn’t inevitable: under different conditions and constraints, the old, good internet could have given way to a new, good internet. Enshittification is the result of specific policy choices: encouraging monopolies; enabling high-speed, digital shell games; and blocking interoperability.

First we allowed companies to buy up their competitors. Google is the shining example here: having made one good product (search), they then fielded an essentially unbroken string of in-house flops, but it didn’t matter, because they were able to buy their way to glory: video, mobile, ad-tech, server management, docs, navigation…They’re not Willy Wonka’s idea factory, they’re Rich Uncle Pennybags, making up for their lack of invention by buying out everyone else:

https://locusmag.com/2022/03/cory-doctorow-vertically-challenged/

But this acquisition-fueled growth isn’t unique to tech. Every administration since Reagan (but not Biden! more on this later) has chipped away at antitrust enforcement, so that every sector has undergone an orgy of mergers, from athletic shoes to sea freight, eyeglasses to pro wrestling:

https://www.whitehouse.gov/cea/written-materials/2021/07/09/the-importance-of-competition-for-the-american-economy/

But tech is different, because digital is flexible in a way that analog can never be. Tech companies can “twiddle” the back-ends of their clouds to change the rules of the business from moment to moment, in a high-speed shell-game that can make it impossible to know what kind of deal you’re getting:

https://pluralistic.net/2023/02/27/knob-jockeys/#bros-be-twiddlin

To make things worse, users are banned from twiddling. The thicket of rules we call IP ensure that twiddling is only done against users, never for them. Reverse-engineering, scraping, bots — these can all be blocked with legal threats and suits and even criminal sanctions, even if they’re being done for legitimate purposes:

https://locusmag.com/2020/09/cory-doctorow-ip/

Enhittification isn’t inevitable but if we let companies buy all their competitors, if we let them twiddle us with every hour that God sends, if we make it illegal to twiddle back in self-defense, we will get twiddled to death. When a company can operate without the discipline of competition, nor of privacy law, nor of labor law, nor of fair trading law, with the US government standing by to punish any rival who alters the logic of their service, then enshittification is the utterly foreseeable outcome.

To understand how our technology gets distorted by these policy choices, consider “The Cloud.” Once, “the cloud” was just a white-board glyph, a way to show that some part of a software’s logic would touch some commodified, fungible, interchangeable appendage of the internet. Today, “The Cloud” is a flashing warning sign, the harbinger of enshittification.

When your image-editing tools live on your computer, your files are yours. But once Adobe moves your software to The Cloud, your critical, labor-intensive, unrecreatable images are purely contingent. At at time, without notice, Adobe can twiddle the back end and literally steal the colors out of your own files:

https://pluralistic.net/2022/10/28/fade-to-black/#trust-the-process

The finance sector loves The Cloud. Add “The Cloud” to a product and profits (money you get for selling something) can turn into rents (money you get for owning something). Profits can be eroded by competition, but rents are evergreen:

https://pluralistic.net/2023/07/24/rent-to-pwn/#kitt-is-a-demon

No wonder The Cloud has seeped into every corner of our lives. Remember your first iPod? Adding music to it was trivial: double click any music file to import it into iTunes, then plug in your iPod and presto, synched! Today, even sophisticated technology users struggle to “side load” files onto their mobile devices. Instead, the mobile duopoly — Apple and Google, who bought their way to mobile glory and have converged on the same rent-seeking business practices, down to the percentages they charge — want you to get your files from The Cloud, via their apps. This isn’t for technological reasons, it’s a business imperative: 30% of every transaction that involves an app gets creamed off by either Apple or Google in pure rents:

https://www.kickstarter.com/projects/doctorow/red-team-blues-another-audiobook-that-amazon-wont-sell/posts/3788112

And yet, The Cloud is undeniably useful. Having your files synch across multiple devices, including your collaborators’ devices, with built-in tools for resolving conflicting changes, is amazing. Indeed, this feat is the holy grail of networked tools, because it’s how programmers write all the software we use, including software in The Cloud.

If you want to know how good a tool can be, just look at the tools that toolsmiths use. With “source control” — the software programmers use to collaboratively write software — we get a very different vision of how The Cloud could operate. Indeed, modern source control doesn’t use The Cloud at all. Programmers’ workflow doesn’t break if they can’t access the internet, and if the company that provides their source control servers goes away, it’s simplicity itself to move onto another server provider.

This isn’t The Cloud, it’s just “the cloud” — that whiteboard glyph from the days of the old, good internet — freely interchangeable, eminently fungible, disposable and replaceable. For a tool like git, Github is just one possible synchronization point among many, all of which have a workflow whereby programmers’ computers automatically make local copies of all relevant data and periodically lob it back up to one or more servers, resolving conflicting edits through a process that is also largely automated.

There’s a name for this model: it’s called “Local First” computing, which is computing that starts from the presumption that the user and their device is the most important element of the system. Networked servers are dumb pipes and dumb storage, a nice-to-have that fails gracefully when it’s not available.

The data structures of source-code are among the most complicated formats we have; if we can do this for code, we can do it for spreadsheets, word-processing files, slide-decks, even edit-decision-lists for video and audio projects. If local-first computing can work for programmers writing code, it can work for the programs those programmers write.

Local-first computing is experiencing a renaissance. Writing for Wired, Gregory Barber traces the history of the movement, starting with the French computer scientist Marc Shapiro, who helped develop the theory of “Conflict-Free Replicated Data” — a way to synchronize data after multiple people edit it — two decades ago:

https://www.wired.com/story/the-cloud-is-a-prison-can-the-local-first-software-movement-set-us-free/

Shapiro and his co-author Nuno Preguiça envisioned CFRD as the building block of a new generation of P2P collaboration tools that weren’t exactly serverless, but which also didn’t rely on servers as the lynchpin of their operation. They published a technical paper that, while exiting, was largely drowned out by the release of GoogleDocs (based on technology built by a company that Google bought, not something Google made in-house).

Shapiro and Preguiça’s work got fresh interest with the 2019 publication of “Local-First Software: You Own Your Data, in spite of the Cloud,” a viral whitepaper-cum-manifesto from a quartet of computer scientists associated with Cambridge University and Ink and Switch, a self-described “industrial research lab”:

https://www.inkandswitch.com/local-first/static/local-first.pdf

The paper describes how its authors — Martin Kleppmann, Adam Wiggins, Peter van Hardenberg and Mark McGranaghan — prototyped and tested a bunch of simple local-first collaboration tools built on CFRD algorithms, with the goal of “network optional…seamless collaboration.” The results are impressive, if nascent. Conflicting edits were simpler to resolve than the authors anticipated, and users found URLs to be a good, intuitive way of sharing documents. The biggest hurdles are relatively minor, like managing large amounts of change-data associated with shared files.

Just as importantly, the paper makes the case for why you’d want to switch to local-first computing. The Cloud is not reliable. Companies like Evernote don’t last forever — they can disappear in an eyeblink, and take your data with them:

https://www.theverge.com/2023/7/9/23789012/evernote-layoff-us-staff-bending-spoons-note-taking-app

Google isn’t likely to disappear any time soon, but Google is a graduate of the Darth Vader MBA program (“I have altered the deal, pray I don’t alter it any further”) and notorious for shuttering its products, even beloved ones like Google Reader:

https://www.theverge.com/23778253/google-reader-death-2013-rss-social

And while the authors don’t mention it, Google is also prone to simply kicking people off all its services, costing them their phone numbers, email addresses, photos, document archives and more:

https://pluralistic.net/2022/08/22/allopathic-risk/#snitches-get-stitches

There is enormous enthusiasm among developers for local-first application design, which is only natural. After all, companies that use The Cloud go to great lengths to make it just “the cloud,” using containerization to simplify hopping from one cloud provider to another in a bid to stave off lock-in from their cloud providers and the enshittification that inevitably follows.

The nimbleness of containerization acts as a disciplining force on cloud providers when they deal with their business customers: disciplined by the threat of losing money, cloud companies are incentivized to treat those customers better. The companies we deal with as end-users know exactly how bad it gets when a tech company can impose high switching costs on you and then turn the screws until things are almost-but-not-quite so bad that you bolt for the doors. They devote fantastic effort to making sure that never happens to them — and that they can always do that to you.

Interoperability — the ability to leave one service for another — is technology’s secret weapon, the thing that ensures that users can turn The Cloud into “the cloud,” a humble whiteboard glyph that you can erase and redraw whenever it suits you. It’s the greatest hedge we have against enshittification, so small wonder that Big Tech has spent decades using interop to clobber their competitors, and lobbying to make it illegal to use interop against them:

https://locusmag.com/2019/01/cory-doctorow-disruption-for-thee-but-not-for-me/

Getting interop back is a hard slog, but it’s also our best shot at creating a new, good internet that lives up the promise of the old, good internet. In my next book, The Internet Con: How to Seize the Means of Computation (Verso Books, Sept 5), I set out a program fro disenshittifying the internet:

https://www.versobooks.com/products/3035-the-internet-con

The book is up for pre-order on Kickstarter now, along with an independent, DRM-free audiobooks (DRM-free media is the content-layer equivalent of containerized services — you can move them into or out of any app you want):

http://seizethemeansofcomputation.org

Meanwhile, Lina Khan, the FTC and the DoJ Antitrust Division are taking steps to halt the economic side of enshittification, publishing new merger guidelines that will ban the kind of anticompetitive merger that let Big Tech buy its way to glory:

https://www.theatlantic.com/ideas/archive/2023/07/biden-administration-corporate-merger-antitrust-guidelines/674779/

The internet doesn’t have to be enshittified, and it’s not too late to disenshittify it. Indeed — the same forces that enshittified the internet — monopoly mergers, a privacy and labor free-for-all, prohibitions on user-side twiddling — have enshittified everything from cars to powered wheelchairs. Not only should we fight enshittification — we must.

Back my anti-enshittification Kickstarter here!

If you’d like an essay-formatted version of this post to read or share, here’s a link to it on pluralistic.net, my surveillance-free, ad- free, tracker-free blog:

https://pluralistic.net/2023/08/03/there-is-no-cloud/#only-other-peoples-computers

Image: Drahtlos (modified) https://commons.wikimedia.org/wiki/File:Motherboard_Intel_386.jpg

CC BY-SA 4.0 https://creativecommons.org/licenses/by-sa/4.0/deed.en

—

cdsessums (modified) https://commons.wikimedia.org/wiki/File:Monsoon_Season_Flagstaff_AZ_clouds_storm.jpg

CC BY-SA 2.0 https://creativecommons.org/licenses/by-sa/2.0/deed.en

[moose-mousse]

Honestly... my advice when people ask how to learn git is:

1 Open a console.

2 Write "git"

3 press enter.

Now read and follow instructions.

Git is OLDSCHOOL.

Meaning it is a self documenting program

[selin-n]

💙💙

Şarkı sözleri

( Cemal Safi 'nin muhteşem şiiri)

Madem ki benli hayat sana kafes kadar dar

Uzaklaş ellerimden uçabildiğin kadar

Hadi git benden sana dilediğince izin

Öyle bir uzaklaş ki karda kalmasın izin

🍂🍁💙🍂🍁💙🍂🍁💙🍂🍁💙

Sanırlar ki sen beni biricik yâr saymıştın

Oysaki hep yedekte, hep elde var saymıştın

Hadi git ne bir adres ne bir hatıra bırak

Zannetme ki pişmanlık mutluluk kadar ırak

🍁🍂💙🍁🍂💙🍁🍂💙🍁🍂💙

Ne vedaya gerek var, ne de mektuba hacet

Git de Allah aşkına bir selama muhtaç et

Güllere de aşk olsun gene sen kokacaksan

Fallara da aşk olsun gene sen çıkacaksan

🍁🍂💙🍁🍂💙🍁🍂💙🍁🍂💙

Kopsun nerden inceyse artık bu bağ, bu düğüm

Her gece daha berbat, daha vahim gördüğüm

Korkulu düşlerimi yorumdan kaçıyorum

Sırf sana üzülüyor, sırf sana acıyorum

🍁🍂💙🍁🍂💙🍁🍂💙🍁🍂💙

Git, iş işten geçmeden git

Çok geç olmadan vakit

Günahıma girmeden

Katilim olmadan git

Günahıma girmeden

Katilim olmadan git

Beste: Candan Erçetin

[nixcraft]

best 12 bucks ever spent 👇

[crystalclearmist]

Just finished rereading Danny Phantom : "A glitch in time" and I'm absolutely vibrating in my seat about the new lore

Spoilers under the cut:

1. Vlad has continued his cloning experiments, even after Dani and her melted brothers :

This is also the only reason Dan Phantom is able to get a stable body at the end of the book.

Also, he designed almost functional clones with high science but really shitty technology skills. If he had help he probably would have succeeded ages ago (see point 5)

2. The staff that Clockwork always uses? Really f*ing important. It would be a tragedy if something happened to it

3. Ghosts are manifestations of human emotions

4. Tucker had a two day stint as the mayor of Amity Park and lost the job because he accidentally dropped a baby. He was also listed as married to Ember. Do with that as you will

5. When Tucker is in class he is so bored he keeps designing A - grade tech :

6. The Fentons RV, the Ghost Assault Vehicle, has 3 funny little buttons (big ghost, bigger ghost and unwanted guest)

It also has cup holders

7. Amity Park has its own version of Instagram called "Spectergram" and it has a livestreaming option

[kernelbroken]

[fujowebdev]

Itty Bitty Kitty(boy) Commit...Preview!

Hello everyone, For those who really want a tasty preview of our Git Zine (with maybe even some feedback 🥺), we've just released a time-limited Itty Bitty Preview on our Patreon! This is a 60ish page version of our larger zine, including the first big chunk of "Git learning" and some of the extra lore at the end.

If you want to wait, or Git is still too advanced for you, remember we've also released a learning website to get you up to speed with terminal and the filesystem!

Regardless, come celebrate with us on today's "treat Ms Boba" stream: creating an Astro plugin to fetch fanfiction data with AO3.js for use on your personal websites! See you in less than 2 hours on Twitch!

[ogrepoppenangleaksofficial]

#COFNRIEMD

actual leakage of height chart? Seems so!

[civcivwq]

"Git diyorsun da olmuyor git demekle, her şeye rağmen gidemiyor insan. Ben de sana 'sev' diyorum mesela sevebiliyor musun? "