unixbane

17 ms·

91.
by unixbane 4y ago
WhateverBB style PHP forums were never good. They were always regressive technology. Don't pretend something is good just because what we have now is even worse. The user interface was terrible. I don't miss clicking a tiny 10 pix
92.
by unixbane 4y ago
a decentralized alternative supporting user concerns instead of corpo crap is trivial to implement
93.
by unixbane 4y ago
...or just don't use some fisher price app designed for children, for military communications?
94.
by unixbane 4y ago
JSON isn't the be all and end all data format. It's full of ambiguities and has pointless, misleading cruft like filtering "unprintable characters". Plain text is also a dead end and misconception contra UN*X hippies.
95.
by unixbane 4y ago
The first few paragraphs sum up a lot of stuff I was thinking for the last years or decade. Microsoft and Google are still scummy corporations and operate on bad faith and abuse their legal power to prosecute people for no reason other than
96.
by unixbane 4y ago
Well, UX is bullshit (otherwise there would exist software made after 2000 that has at least a decent GUI instead of complete nightmares) so you'll need to fix that first.
97.
by unixbane 4y ago
Wow we should all use only Google because they are the only good and trustworthy email provider. Why do we even need email at all? There should just be a simplified protocol or webapp that stores everything on Google and manages all your au
98.
by unixbane 4y ago
Content modification usually leads to vulns (e.g, XSS filters, possible bitsquatting enabled here if they change URLs or breaking array bounds checks in programs). Classic 90s security. Too bad 90s security never went away.
99.
by unixbane 5y ago
I was lucky enough to realize early that all UN*X software is bad and no distro will overcome this bottleneck. For instance, even if you use the only few GUI toolkits that work reasonably fast, like Motif, these programs will still be broke
100.
by unixbane 5y ago
It was as content free as one would expect.
101.
by unixbane 5y ago
Why are you talking about hardware? Just get rid of these weird snakeoil auth flows and make user / password the be all end all way to authenticate. If there's a problem with that, well there isn't. No company on earth has ev
102.
by unixbane 5y ago
Yes, 50 people ITT have already pointed out this one weird trick. If anyone actually thinks this fixes the general problem, no it doesn't.
103.
by unixbane 5y ago
Until you play with 15 different companies each which have slightly different variants of how they do their authentication security theater, as well as them throwing odd balls at you every month until you really have no idea how anything is
104.
by unixbane 5y ago
HTTPS is when you ask 200 companies if either of them know the key for your bank. And they are all run by charlatan boomers who think buying more firewalls and cool security products is equivalent to securing their private cert signing keys
105.
by unixbane 5y ago
There are no experts in information security. It's just random people with in depth knowledge of some tiny subsystem they happened to feel like studying. They are literally all LARPers who will fall for every single thing aside from wh
106.
by unixbane 5y ago
> it seems like almost no one else does Nope, I do basic stuff like this too. And it's basic stuff. As in, can be defeated by simple wiretaps in infrastructure outside your control.
107.
by unixbane 5y ago
> When discussing scams and social engineering attacks, it's easy for security researchers and experts to present information in a way that implies the victims of these attacks should have known better. Uhhh, when I see any SE I ass
108.
by unixbane 5y ago
Off topic but I wonder how many "self hosting" efforts have been halted in the last 40 years when the unsuspecting developer tried to use API to create a socket and was met with all kinds of weird AF_ PF_ terminology and possibly
109.
by unixbane 5y ago
Having dependencies not change is literally trivial. Just link to them by hash. Async/await is a pragmatist garbage hack, and does not fit in the archetype you are trying to name.
110.
by unixbane 5y ago
Dependencies being immutable and identified by hash was such an obvious thing 20 years ago. The problem was fitting that into the flow of these crappy UN*X based build systems where to do any mundane task you need to fiddle with files and e
111.
by unixbane 5y ago
the _immiedate_ consequence of a document format having scripts in it is this. there is no far thinking required to realize this. it was obvious at the time.
112.
by unixbane 5y ago
it seems you are the asshole here.
113.
by unixbane 5y ago
UN*X is a shithole and just talking about one of the problems with it causes one to pull in the other problems that are inextricably intertwined with each other.
114.
by unixbane 5y ago
A tangile explanation. Metamask is centralized. That part is true. Metamask should be removed along with anything else that remotely resembles a web browser, especially stuff that relies on a web browser which is the complete antithesis of
115.
by unixbane 5y ago
> The problem is that engineers and cybersecurity people all think that everyone else thinks like they do, when in actuality the complete opposite is true. In theory yes. In practice, nobody has made this supposedely good for the hacker
116.
by unixbane 5y ago
This article doesn't even explain how web3 is centralized (it is in many ways). All I see is some stupid non-technical blog trying to orient blockchain as part of the enemy along with "wh*te", "0.1%", and "bro&
117.
by unixbane 5y ago
No, I was purely focused on public web. As for your corporate services, those are all insecure as hell despite whaever tech they use. Anything that's remotely hidden from public in any way historically was uncovered to have non stop, g
118.
by unixbane 5y ago
also info nobody knows enough from reading manuals for UN*X because it is too hard. everyone I talk to who says they have done it are still missing fundamental info, like for instance any one i talk to will probably not undersand that sudo
119.
by unixbane 5y ago
Standards are good. > How do you prevent it from being sent to the wrong domain and enabling MITM phishing? TOFU. Petnames. > it would have to be parsed in some way Encoding a key is trivial, even with an ad-hoc serialization format.
120.
by unixbane 5y ago
> It's hard to see it as a non-practical, academic idea when it's out there, deeply embedded in the internet, everywhere. It is non-practical, has no application in reality, and the direct consequence of using such a tool is ma

More ›