tripu @tripu@qoto.org

@gasull

> _GitHub: Maybe it's around a 100 columns_

Nope. [This](https://github.com/tripu/superscript/blob/master/server.js#L55) is > 140 chars long, and doesn't truncate or wrap.

> _I once or twice did code reviews on the phone before boarding a plane. There are apps for GitHub and GitLab. People use them._

C'mon… You said it: “once or twice”. I feel your pain. 99% of people shouldn't compromise 99% of the time because of those rare use cases. People try all kinds of crazy devices and clients.

> _I want my screen to see the code and the browser side by side_

Personal preference/need. I sometimes want to see the console underneath — for that, fewer longer lines preferred. (And again: [local solutions](https://en.wikipedia.org/wiki/Line_wrap_and_word_wrap) are easy.)

> _“If you need more than 3 levels of indentation, you’re screwed anyway, and should fix your program”_

That's wrong (breaking news: Linus has been known to be wrong before):

1. _“Tabs are 8 characters, and thus indentations are also 8 characters.”_ That's half of the problem, right there. 8 chars? No wonder they want < 4 levels. 4 levels × 8 chars = 32 chars = 40% of your very conservative line length budget!
1. A class → a method → an `if` = 3 levels. No room for a loop, for a literal object with properties, for chained calls split into different lines for legibility? I seriously doubt Torvalds himself follows that rule.
1. I looked for popular projects on GH with files with more than 3 levels of indentation to prove my point. There aren't many: it's ALL of them.

@admitsWrongIfProven

👍

@admitsWrongIfProven

With PoW, past a certain point in the growth of the network, it's prohibitive for most bad actors to spend enough money in hardware and energy to become > 50% of the network and thus gain control.

With PoS, it's exactly the same, just replace “spend enough money in hardware and energy” with “buy enough tokens”.

In any case, if someone/something has the means and the determination to grow past half of the whole network, they will control the consensus and therefore the money.

both PoW and PoS are vulnerable to concentration of power — but both are less vulnerable than centralised systems, eg central banks or credit card companies.

@admitsWrongIfProven

Not sure I get your question.

If you're asking what advantages #crypto provides, I'd recommend from a number of good sources.

One example:

https://www.commonsense.news/p/is-bitcoin-anarchy-or-civilization

@admitsWrongIfProven

With the shift to #ProofOfStake, energy consumption is no longer an issue in #crypto. #Ethereum is almost there, and future blockchains won't waste energy like #Bitcoin does.

/cc @shadowsonawall

@cnx

Very cool! Thank you.

I knew very little about #Pleroma (and nothing about #Akkoma).

(Still, I find “nested” or “indented” views only a bit better than “flat” ones — what I'd really love to find is a tree-like visualisation, with nodes [posts] and edges connecting them.)

@freemo

/cc @torgo

@torgo

Where is that? mastodon.social?

@freemo, I CAN HAZ?

I can be a #vegan for life as long as there is _nachos con guacamole_

@gasull

Somewhat trollish but mostly honest answer:

80-char-limit-lines is SO outdated and inefficient as general advice.

> _GitHub forces you to scroll horizontally for long lines_

Whut? Definitely not over 80 chars ([eg](https://github.com/tripu/superscript/blob/master/server.js#L55), [eg](https://github.com/tripu/glypher/blob/master/js/glyphs.js#L27)).

> _Some people do code reviews on their cell phones_

That sounds horrible to me. And in any case, it's not my fault. What if some people do code reviews on their smartwatches?

> _Who are you to claim all my screen real state?_

Shorter lines take exactly the same real estate (just distributed differently). And in any case, I'm not claiming anything: you can enable line wrapping (and scroll).

> _Long lines aren't very readable anyway_

Perhaps. But over 80 chars isn't always “long”. In certain languages there are typically long identifiers and long chained properties (eg, Java). Add four or five levels of indentation, and you're well over 80 before you realise it. Splitting that one line into two or three shorter lines may well make that _less_ readable, not more.

@admitsWrongIfProven

Yes, but consequences of the #FTX fiasco are even broader: people stop trusting #EA, and politicians seize the opportunity to meddle with blockchains for their own gain.

I think "people stop trusting crypto" is a bad thing. But that's debatable.

You are right in that ripples of bad actions are also consequences and thus should be considered by consequentialists. But then, someone secretly committing a crime or deception for the greater good, and never being caught, is a good thing? That's the riddle for hard-core consequentialists.

/cc @shadowsonawall

@shadowsonawall

“There’s no way of escaping the fallibility of a moral system, no matter which one you pick”

≠
“All moral systems are equally fallible”

The impossibility to achieve perfection is no excuse not to try to get as close as we can.

Besides, it's just impossible not to have a “moral system”. Who doesn't have one? You have to be a rock or an automaton not to.

So, let's keep refining them.

@fidel

I'm focusing on the #EA reputation angle here because that's the angle I care most about — more than the future of #crypto regulation, political corruption, or the specific shape of the fraud.

But those are very important too, no doubt.

@ImperfectIdea

> _Anyway, as you say, we don't even know exactly what he's done_

Yeah. That was more true a few days ago. It's starting to be clearer by the day, by SBF's own words 😞

> _There are reasonable and unreasonable risks and no one would be outraged for a reasonable risk that goes wrong_

If only! Embedded in my larger point was the idea that unfortunately society tends to judge people and institutions based on _actual outcomes_ and not on _probable outcomes_. For good, and for bad.

eg: when a nuclear accident happens, the media, politicians, etc all rush to attack nuclear power and to find who to blame for deciding to build and keep running the nuclear station. That happens even when that was a very rare, unfortunate accident, and when the right answer would be: “ah, the plant was OK, we just were unlucky! Still nuclear is the best alternative.”

And the opposite is true, also: a politician who cuts funding for epidemic preparedness, or issues a lot of additional debt, or does a similarly risky thing, will rarely be criticised (let alone impeached or prosecuted) if he simply gets lucky and the (unwise) gamble turns out favourably for the country.

I hate that.

wrt #FTX, it seems to me we're judging according to what happened, not to what was most likely to happen (getting way with it in the end, with no victims?). I think both should count, somehow — not sure exactly how, though.

I think this 💩 confirms my interpretation of what happened with #SBF / #FTX:

https://www.vox.com/future-perfect/23462333/sam-bankman-fried-ftx-cryptocurrency-effective-altruism-crypto-bahamas-philanthropy

So shocking, sad and disappointing.

(I meant @ourmaninjapan)

@privacyfirstjobs

* [Fastmail (called Masked Email)](https://www.fastmail.help/hc/en-us/articles/4406536368911-Masked-Email)

/cc @ourmaninjapan