HNHacker News
TopNewBestAskShowJobs

unixbane

32 karma · joined September 18, 2021

submissionscomments
unixbane··on Web3 Domain Name Service Could Lose Web Address-Owner Who Can Renew Is in Prison
> what in the world are you talking about

rebuking the implicit, "ergo this method is bad" part of your post, given its context. more specifically, the idea that its worse than current methods with DNS and X.509

unixbane··on Web3 Domain Name Service Could Lose Web Address-Owner Who Can Renew Is in Prison
What the actual hell is with blockchainers and using centralized CRAP like Discord, Google, Amazon, and a decentralized naming system that nobody actually uses the decentralized way because they are not aware of the concept of running code on your own machine.
unixbane··on Web3 Domain Name Service Could Lose Web Address-Owner Who Can Renew Is in Prison
That's not a grounded argument.
unixbane··on They're trying to get me kidnapped and tortured, but Twitter doesn't care
Also, this title is the most hyperbolic "wah company bad" bullshit ever written.
unixbane··on They're trying to get me kidnapped and tortured, but Twitter doesn't care
Yes and requiring moderation on internet forums is not one of them. It will stop 0.00001% of cases, while growing malpolicing (especially non useful police who demand more mircrojustice to keep their comfy pay coming in) proportionally with it.

This reminds me of HN. You get banned if you say a bad word. You get banned eventually no matter what unless you're a white collar self censored silicon valley drone with ultra-safe opinions like "the C language should be deprecated after a mere 70 years". You get rate limited if you get too many downvotes in the given time slot. Random IPs are blocked for no reason and the login screen is just a blank page. You get shadowbanned so you don't even know you're banned. All for basically nothing, as HN is basically like 2000s forums but with slightly better discourse and consistency of moderation (and worse in other ways).

This idea that we should have some sort of epidemiologically correct moderation policy on the internet is also bullshit. Moderation on the internet started off as, annoying, childish, 40 year old sysadmins who ban anyone they don't like, SJWs who ban anyone who is "the enemy", right wing equivalent of SJWs who do the same thing, rule fetishists (people in the UK who think insulting the queen or showing the middle finger should be illegal), etc. The idea started off with these selfish / idiotic reasons. Once questioned, they are forced into a corner where they can only rationalize moderation as an epidemiological tool. "Yeah, if we just delete these 1 million posts it's a net gain".

The only reason lack of moderation on big copmany's websites even come up is because they're big companies and they have egg on their face for any slight mishap (or what public perceives as a mishap). It's the most stupid fucking shit.

unixbane··on They're trying to get me kidnapped and tortured, but Twitter doesn't care
Yes yes, we're all gonna die because people are allowed to post on the internet. Decentralized messaging platforms should be illegal because they can't be moderated. You should only be able to host an internet service with a license and yearly federal inspections to make sure you're properly storing and backing up accountability logs of all users.

> blah blah blah there are insane people in my country who will kill people based on tweets

This is a problem of people and not Twitter. Those are in the west too and growing especially in America. The problem is dumbed down people who believe stuff on the internet. And idiots who react to things, like a white/black shooting a black/white. There is a solution to this: going to jail for murder. Even boomers in the 90s knew not to believe anything online. Twitter has about a million problems with it and lack of moderation certainly is not one of them.

You cannot reasonably ask Twitter to moderate for your locale's social and violent reactionary issues. That implies they need to hire a huge amount of people for every locale in every country and just gives Twitter more monopoly as another company would have to invest a billion dollars to do that before they can even get off the ground. You have just created this idea that storing 100 bytes of text on a server is now a thing that requires billions of dollars of up front investment to do. This is another issue: People are fucking stupid and expect companies to have some "responsibility" now (despite the fact that product quality is at an all time low and they somehow have no issue with that). This is also just conceding that companies are some kind of god (they really aren't. Twitter is a dog shit website that can't go more than one second without showing the text "undefined" in an important field on the page).

Ironically, the people who demand so called justice by moderating more and more shit online (Unreal Engine now has voice analytics to report you to the police or whatever the fuck built right in), are just as bad as the people who foster misinformation against people. We are heading into an era of micro justice which just means the amount of malpolicing will grow in proportion. The end result of constantly trying to solve micro injustices is AI making sure humans don't do anything "bad" and you will literally be unable to involuntarily move your arm a certain way without being punished. There is not even a philosophically correct definition of justice in law. It's literally a bunch of dudes amending a global ruleset to solve the latest problem, based on wildly varying rationales from people each with entirely different value systems.

It's actually hilarious how short sighted and oblivious statements like "it should be illegal to post misinformation online" are. You aren't a mature responsible adult or whatever you think you are. You are just reacting to something in the most straight forward way with no thought about the consequences. It's doubly hilarious for insinuating that posting things online is a big issue that we should focus law on. It's actually pretty fucking obnoxious actually, I'm sick of every thing I do online for the last 20 years being policed by hall monitors tunnel visioned on whatever social injustice issue of the day.

unixbane··on Chrome allows websites to write to the clipboard without the user’s permission
Pasting anything what so ever in the shell is a vuln if you are on a system where untrusted programs can set the clipboard. Even typing "echo <ctrl+shift+v>". And no, it's not detectable either.
unixbane··on Chrome allows websites to write to the clipboard without the user’s permission
This is why you don't break abstractions. If I'm a user I expect the clipboard to only change when I press ctrl+c or right click -> copy. These should be authoritatively controlled mechanisms that untrusted programs cannot override.

Going further, I want whatever I copy to be whatever I see when I hit copy. Which of course isn't possible in the interactive web.

But unfortunately devs for the last few decades think they can just leave everything undefined and change its meaning for their ad-hoc purposes every minute then claim computing is hard.

unixbane··on Chrome allows websites to write to the clipboard without the user’s permission
The whitespace thing is a bug, too.
unixbane··on Mainnet Merge Announcement
This. The wikipedia page for years seemed (not looking at it again, lol) to be written by people of the same ilk, who introduce a bunch of terminology without explaining what any of it means. When I read the wiki in 2020 it was literally impossible to understand, knowing already at the time how Bitcoin and a few other alt coins worked, as well as someone being into smart contracts well before even Bitcoin was created. And Ethereum is literally just a Bitcoin + smart contracts. There is no other core, fundamental concept to understand in it (until now: PoS). Also yes, as someone who has used hundreds of cryptocurrency products, this applies to basically anything related to cryptocurrency like you said.

One absolutely obnoxious practice is how they all make their own fancy names for millicoins microcoins, etc.

unixbane··on Why do arrays start at 0?
On a cursory look, I'd say one based is more intuitive, for the sole fact that the a[len(a)] is the last element. Actually I remember there was a small time when I started programming in assembly it took me a while to get used to reasoning about the end of the array.
unixbane··on Why do arrays start at 0?
So what's the actual reason you'd want to have zero based arrays and such in your language (In 2020, not 1970)? In a language from scratch that doesn't care about being like previous ones, and doesn't care about micro optimization.

I've been annoyed recently by this obnoxious neckbeard behavior when they make things zero based for no reason (other than to conform to their supposedly existent philosophy), like Ratpoison and Screen selecting windows by a zero based index, which means you have to move your hand to the far right of the keyboard to select the first window with the 0 key, the far left to select the second window, with the 1 key, and one to the right to select the third window, with the 2 key.

I so happen to have been trying to work out a tangible explanation on paper of which system is better on trips a few weeks ago, and could not come up with one (and none are given in the article nor the top comments in this thread).

On a side note, the moment you say, "zeroeth", you can no longer be sure anyone knows what you're talking about because at any moment you may count in English or this pretentious UN*Xtard dialect of English. Seems like another pedagogical stumbling block held on to boomers and boomer-wannabes who just want to have their little counter counter counter culture or whatever.

unixbane··on Programming breakthroughs we need
Just switch back and forth between box representation and graph. It's still far better than text. Text fails far faster. Have you ever used IDA? It shows a graph view of assembly based on jump flow instead of a linear assembly listing. Of course you can't magically understand all programs just with a simple algorithm to format them a certain way, but it's still immediately obvious that this is better. Most code is immediately understandable just using a C#/Java decompiler or gofmt without the programmer needing to format it. I just see variable names and formatting as spam and red herrings. Anyway you can't audit code by taking the programmer's word that he formatted it a certain way, so this whole "text for writing a poem of comprehension" idea is moot and outdated at least 30 years ago anyway.
unixbane··on Programming breakthroughs we need
Woah there, it appears as if you are implying that text is demonstrably the best way to convey computer programs. Surely that's not what you're saying?
unixbane··on The Shell Hater's Handbook (2010) [video]
The `hostname` part is wrong, it needs to be quoted. If we want to talk about actually hating the shell, just use this one weird trick where merely comparing an integer to untrusted input constitutes an RCE vuln:

$ X='a[$(touch pwned1)]'; [[ $X -eq 0 ]]

Oddly, quoting doesn't fix it:

$ X='a[$(touch pwned2)]'; [[ "$X" -eq 0 ]]

Shells are not good for what they do. Literally half of any *sh script is just reading somedata.somefield but implemented with (poorly defined and poorly written) regex to compensate for some genius UN*X utility's output which is totally not meant to be parsed but we're still gonna parse it anyway because we didn't have the most simple foresight of how data will be delivered to other programs. Then there's stuff like working around crap to be able to do something like -c -arbitrary_input, such as -- which may or may not exist or be applicable. It's hilariously BAD. They are not fast to use as opposed to general purpose languages, because you are just adding a bunch of bugs to your system each time you take any RAD affordance it purports to offer.

*sh fits into the category of C for extremely poorly designed languages. In this case, instead of having bugs like duff's device and UB flying all over the place even where there's no rationale for it, we have a similarly poorly defined language where parts of the language itself may or may not exist (including the minimal set of commands you need in practice to get anything done, despite them being not part of the shell) depending on which implementation you use, and POSIX has to step in and try to post-hoc tell people what's portable and steer future direction, and you have random cargo cult like x -eq x$var (or whatever that was, yeah I've spent a week of my life learning *sh and hope to never spend another minute more).

The example where he shows editing a command is hilariously bad. It requires knowing some obscure shortcut in a bizarre unreadable manual, knowing how escape sequences work (if you want to change the key binding), having $EDITOR set. Basically you need a few years of UN*X indoctrination to understand all these mechanics, and you will still get them wrong, for example how $PS1 is always wrong (no not just me, in the big distros they are buggy). And as the command grows your shell is spammed and you quickly lose everything off scrollback, as opposed to simply assigning a name to the code you're working on or having an abbreviated form be displayed. Whatever your $EDITOR is set to will also be a thing that takes a year to become efficient in. Formatting with each bar on one line is also just another work around for text based languages. This is why all REPLs (which are just that: a quick hack) suck, despite being the fundamental core of an OS. It's just a poor approximation of what can much more easily and efficiently be done with a raster scan monitor as opposed to a terminal from the 70s.

Using the shell doesn't make you a hacker. It makes you a quack. 10 years ago I remember trying to do stuff on a UN*X system with only terminal, that involved merely printing some untrusted input, and I piped it through a small program I made to strip out anything outside [0x20, 0x7F]. 10 years later I had time to audit it and found out I was indeed correct. You literally can't do ANYTHING in the shell and be secure. It's a nightmare. What's RVM? I'm gonna go audit that. Zsh actually seems to be a bunch of security footguns. Even their security features are broken (such as bracketed paste, which is always broken anyway).

There is not even anything valuable in the shell that makes it worth preserving. It's entire job is to be compatible with a bunch of bad decisions made 50 years ago (yes, some of then were justified due to the paradigm being different back then). All your doing by using *sh is trying to be compatible with all these garbage tools. All these utilities like grep sed awk are moot (on top of being microcosms of the same issues of *sh) because you shouldn't be parsing things anyway. Imagine using this rube golberg shit in your mission critical embedded devices like vehicles.

unixbane··on Programming breakthroughs we need
Standard boomer rant.

> There's a reason why the status quo exists

Yes, it's called the status quo.

> text is universal

Which one, ASCII, code page 9000, or UTF-8? Are you saying just restrict to ASCII? Then we need custom solutions every time someone wants to talk a different language.

> lock in

I am locked into using retarded insecure terminal emulators because all my tools depend on it to render what you people call "text" which is supposdedely "simple" or "universal". Even vim breaks from unicode already. The primitive language of the OS should not be some poorly defined idea of "text", but algebraic data types.

> reading important

Which is better done by graphics that text. Just the fact that with a structural editor - an if statement spans the amount it appears to span, instead of having to trust someone to format it correctly - is already enough reason to ditch text.

unixbane··on Programming breakthroughs we need
Programming is an exercise in manipulating semantic objects which is why stuff like blueprints in unreal engine are so easy to use. It will just get better and text will become an obsolete vestige, regardless of whatever idea you have of this being "harmful". I really don't think a character encoding with 30 ways to control the terminal (and now extended to encode emojis) is the be all end all way of writing and editing programs.

Consider that if text had an advantage, it would be that you could cut some string in half as some sort of manipulation that saves time. What do I cut in half? Change >= to = ? There's basically no advantage of text. I don't want half of an if statement, that's what text allows me to do, it's a pointless feature that makes inputting programs harder. The basic element on the screen should be the if statement itself.

There is no advantage to a 1D language. Text is a 1D language. If you have

  if (x) {
    if (y) {
    }
  }
You are just reading it as a 2D language, but it's not. It could be

  if (x) {
    if (y) {
    }}
  }
and mean something else. (Yes I'm sure you can catch this one, but not all in general). The only way to be sure is read it from start until end, which nobody does. This is a security issue too, which I discovered when I was 12 years old reading perl scripts from milworm. By formatting text you are already conceding that 2D is better.
unixbane··on Petnames: A humane approach to secure, decentralized naming (2018)
The proper way to connect to a service on the internet after the 70s when crypto was invented, is to connect by public key or hash thereof. Instead of a bloated insecure HTTPS stack, your code just connects and checks against the public key which was used as the address (actual implementation details like finding the IP address or routing over an overlay network is done automatically with something like a DHT).

The second piece to this is how the GUI works. Instead of showing long bit strings or hex encoding them in some pointless way, it allows you to assign names to these addresses as you come across them. When you see the address in some other page it will show up with the name you assigned and so you will recognize it.

A key point to this is that HTTPS does not actually cause you to know you are using the right domain name. Aside from the fact that HTTPS is untrustworthy due to the CA model, mybrand.com or mybrand.net or one of the other infinite number of legitimate sounding things could all be the correct domain for some brand, you would never know unless someone previously introduced you to the right domain name. Since you had to get it from somewhere, you may as well have received the public key at that point, which could be encoded in a QR code, or, on the internet, which is the main use case of petnames, trivially included as a link in some web 8.0[1] page or chat where you first heard of the brand.

1. I guess it will take them 6 more tries to get this right.

unixbane··on Petnames: A humane approach to secure, decentralized naming (2018)
The replacement for the web will have secure identifiers instead of "URLs", and the GUI will simply replace them with whatever nickname you gave, and all programs on your OS will share the same registry. Or I guess we'll just have another 40 years of misconceived ideas first, it's hard to predict.
unixbane··on Petnames: A humane approach to secure, decentralized naming (2018)
This version of petnames is too complicated. You can't get a good petname system without getting rid of broken crap first. Scanning a QR code on a flyer should be the sole introduction point and just lead to a secure communication from then on. Why do I want petnames for phone numbers or other insecure things?

To put it differently, no petname system built on top of unix / web crap will ever be good. Everyone (like posters here) will not understand what they're doing and just write code that breaks it on all layers of the OS and GUIs. Guaranteed if Android starts using petnames more there will just be issues like it copies someone's petnames all over yours, shares the ones you didn't want to share, etc.

unixbane··on The Decommoditization of Protocols (1998)
> I argue that decommoditized protocols are a very effective weapon against free software in the short term, but in the long term will help free software become more fulfilling to users.

It's not even about free software. Having proprietary standards just produces shit software. See: word, zoom. Proprietary formats are not even a thing (the idea of making some simple text documents that need a certain OS to read and write is absurd) but forced cancer that only exists because the company tries hard enough to maintain their crapware.

unixbane··on Declining quality of consumer-grade products – 2009 fridge compressor autopsy
but electronics are literally shit. perhaps they always were, but there are things that are new since the early 2000s that automatically make them shit, like those buttons on a microwave, digital controls, and having javascript inside the product. i cant think of a single piece of hardware i bought after 2005 that i was happy about. i buy a scale (the most expensive one in the store this time) and it automatically shuts off after a minute and i have to re-tare it. i buy a thermostat and it has a vuln that lets people remotely control it. i buy a keyboard and it has LEDs and when you turn them off (lucky it has the feature), you cant see the key labels because they are just holes for the LED. i buy another "gaming" keyboard and it has 2KRO (i.e, worse than $5 generic keyboard). the last decent product i can remember was a CRT in 2005. LCDs starting with HDMI or so take longer to turn on that a CRT, they are THAT bad. (LCDs did not compete with CRT until 2015 or so, btw).

i cant even imagine why you would downvote this. are you the one agreeing with OP's "no evidence" claim, or are you just some frothing idiot consumer who is upset that your little purchases arent being extolled as they usually are?

unixbane··on VLC media player banned in India
it starts up in less than a year and seeks decently fast
unixbane··on Rob Pike's simple C regex matcher in Go
okay now post the standard academic version of elegant simple regex in algol, lisp, ml whatever and see how many upvotes it gets
unixbane··on The hacking of Starlink terminals has begun
I have quit the software industry and now get paid what people _should_ get paid for software which is a small fraction of what I was being paid before. By choosing to work on actual real problems, instead of partaking in the pseudo-intellectual clout chasing contest that is the tech industry, I have discovered the real value of software which was never much to begin with as I assumed it was when I was a kid.

tl;dr yep, he could have been shoveling CRUD shit and making more money, or implementing high end algorithms within broken operating systems, or implementing high end algorithms with insufficient education or time to prove them, while getting dumber

scratch that he got a bug bounty for his work so his net gain is equal. check mate

unixbane··on The hacking of Starlink terminals has begun
Yeah this is a typical article where the author gets all excited and explains the technical details of the "hack", because it can be called a "hack". But it seems nothing was done here other than some reverse engineering and bypassing tamper proofing to gain access to his own OS.
unixbane··on Dotfiles being hidden is a UNIXv2 mistake (2012)
no, it just doesn't fit into your two categories of posters here on HN
unixbane··on Ask HN: Why do you consider the web a thing?
You are both too normal so the product works as intended for you. Unfortunately however, real engineering means making it work in all likely cases. Anyone outside of upper-middle class suburbia has an absolutely terrible experience with computers. The browser takes a minute or more to start. Button clicks take 10 seconds. You wouldn't know this because they are not your target market. But don't get confused and think I'm appealing to feelings. I'm saying software should be acceptably performant, when currently most is not, especially not websites. I'm saying that 99% of people get a terrible experience with software, once you step outside your bubble world. Real software should work on only 1000Mhz when performing trivial tasks like displaying text and forms (to say the least). Real software should not break down because of certain attributes about your IP address, user agent, etc.

I can't tell where you're coming from without getting to know you, but all these "works for me" forum posts are invalid for the simple fact that if I have a real conversation with someone in person, 99 times out of 100 it will just turn out they are acclimatized to slow half working bullshit. On forums the only reason they get away with spouting this nonsense is due to the upvote system and their cliques. Like if I complained about battlefield 2 taking 20 seconds to load the menu mid game back in 2004, a group of stupid forum posters will all either have a $2000 rig (in current dollars) that was able to bypass this bottleneck, or they're just some casual who played the game for 10 minutes in their life so they haven't had to open the menu a lot yet.

In the case of a signup form, it could and should have a standard solution that doesn't require amateurs to code it themselves, 20 years ago. Like a standard authentication protocol. And of course it should not rely on flaky communications like a verification email. All these things work for you because you're too normal, despite being terrible misconceived ideas. Since the web as a platform is a misconception, you could not make an application that uses a standard authentication protocol because the web introduces all kinds of problems due to its weird way of operating like the fact that you're vulnerable to CSRF by default and asinine nonsense like JSONP, and the fact that web applications aren't really a real mode of software but a bunch of hacks like embedding a script tag, setting the doc type, and fiddling with strange headers, and you can't really have libraries without all these fixes from 5 minutes ago like pinning hashes of resources and building some giant half working external dependency management system. Then at the end of the day it's still each website pulling the authentication code with whatever implementation of their choosing so you still can't trust it as well. Your "working" system is built out of a compatible stack of misconception-compatible software. The moment you misstep, for example if you want some privacy and put on a proxy, you will be severely punished since that breaks half of the web and leaves you with the overhead of doing workarounds for every single interaction.

unixbane··on Ask HN: Why do you consider the web a thing?
If you buy a machine for less than $600, it will not smoothly browse the web. Perhaps it will have hardware acceleration for a few use cases, but in general most pages will be slow. 4 years is insane for that price, would you buy a new dishwasher every 4 years? What if I want 2 machines?
unixbane··on Dotfiles being hidden is a UNIXv2 mistake (2012)
this post is a good example of how un*x hippies with their fried brains from too much drugs* realize one unit of common sense after aeons of contemplation. just like with generics in go. in fact, go itself is just decades of C users very slowly conceding to the idea of basic hygiene. it took them decades to come up with something which is essentially just what was already available in the 90s (pascal, fortran, ada, basic, later java 1.2 or so which also had green threads), but with stuff done a certain way so the boomers can be like "oh see, we did this minor syntactic change THIS way, checkmate, pascal"), in other words they want to have their say in everything

* im not joking, this is what un*x culture appears to essentially boil down to. boomers were all hippies in the 70s despite presenting themselves as "austere" and "mature" "wise" individuals now, which had the unfortunate side effect of too much drugs. further research is needed to clarify whether brain damage is caused by drugs or un*x

any encoding in file names at all is a mistake. this includes character encodings too, which may sound like a non-sequitur but its not. in fact, files should only have unique identities, not names. names should be metadata. folder hierarchy should just be a user defined data structure that can reference these said "files". anyone who tries developing their own OS without copying extremely idiosyncratic un*x ideas and without being bogged down by the overhead of assembly language or C quickly learns this. an example of youngins discovering this is IPFS (and subsequently implementing it on top of broken un*x)

← PreviousPage 2 of 6Next →