@sir Every country is but an abstraction.

Patrick boosted
Patrick boosted

git push -o skip-ci

^ now supported on git.sr.ht

You can specify any other push options and they'll be forwarded to any webhooks you have configured, where you can use them for arbitrary behaviors

Patrick boosted

So got #postmarketOS booting on the #pinebookpro

Only from SD for now since u-boot is the most annoying part.

Patrick boosted

I ought to make a similar alias/script for my terminal 😳

@traubenuss @sir I don't know, some part of me still believe it's Jasper doing all the hard work, employing his pet human as proxy. 🤔

Patrick boosted

So, SourceHut is not hosted in anyone's cloud. I own all of the hardware outright and colocate most of it in a local datacenter.

I just built a new server for git.sr.ht, and boy is she a beat. It cost me about $5.5K as a one-time upfront cost, and now I just pay for power, bandwidth, and space, which runs about $650/mo for *all* of my servers (10+).

Ran back of the napkin numbers with AWS's price estimator for a server of equivalent specs, and without even considering bandwidth usage it'd cost me almost TEN GRAND PER MONTH to host JUST that server alone on AWS.

AWS is how techbro startups pile up and BURN their investor money.

Patrick boosted

@sir never really thought of it in terms of a single control flow section. And then it makes sense to me to be thinking of the case directives more as labels, which aren't further indented.
Thank you for the clarification.

Speaking of labels, the guide doesn't state indention rules for labels. I believe it's pretty standard to have them unindented. But I have seen cases where they were. Perhaps the guide should spell it out?

@sir Very nice guide! But could you expand on the reasoning behind this rule?
> MUST align case branches with the switch statement.
I'm assuming it has got to do with the 80 cols limit. I normally indent the case statements too, as it's visually easier to jump pass the entire switch statement.

Patrick boosted
Patrick boosted
Patrick boosted
Patrick boosted

Big picture, in the next decade, I would like to see:

1. Federated free software services become the dominant platform for social media and messaging.

2. A more privacy-oriented and cryptographically-literate public, and simple, standard free software tools anyone can leverage for this purpose.

3. Open hardware, especially RISC-V, becoming the dominant approach for new hardware development.

4. Recapturing the mobile market from proprietary walled gardens, instead favoring models which put the user in control of their devices (e.g. pmOS).

5. Average (read: non-SV CEO) technologists becoming more politically engaged, including running for and winning offices, and using political will to reinforce the above and start making a difference outside of tech

@tomleb @sir I'm doing this as well. Together with Drew's multi host, multi arch, single repo.

In addition to the alias for one's public dotfiles, I have another repo/alias for private stuff too, so the two basically just overlay my $HOME.

Having these two aliases is quite advantageous, I think. It also avoids undesirable habitual commits to my dotfiles, when I think I'm in an "actual" git directory.

@sir your hacking buddy looks quite friendly, and has a nice shirt too...

@sir sane. I'd love to make a program in sane. 😏

Show more
Librem Social

Librem Social is an opt-in public network. Messages are shared under Creative Commons BY-SA 4.0 license terms. Policy.

Stay safe. Please abide by our code of conduct.

(Source code)

image/svg+xml Librem Chat image/svg+xml