Hacker Newsnew | past | comments | ask | show | jobs | submit | raingrove's commentslogin

In Korea, shame often serves as the primary motivator behind high-profile suicides. It's rooted in the cultural concept of "chemyeon (체면)", which imposes immense pressure to maintain a dignified public image.


Do you have any example of these high profile suicides that can't be better explained as "taking one for the team" for lack of a better idiom.

Shame is a powerful social force throughout the society, but we're talking about systematic screwings more often than not backed by political corruption (letting incompetent entities deal with gov contract on basis of political money and other favors) or straight fraud.


Pretty cool! It's kinda amusing that we've gone from TUI (VisiCalc/Lotus 1-2-3) to GUI (Excel), and back to TUI though.


cursor-addressing uis likely have a higher barrier to entry (both for developers and users), so they are not suffering from the regression to the mean that has made modern guis absolutely unusable.

that, and there aren't any "ui/ux designers" specialising in cursor-addressing uis.


> and there aren't any "ui/ux designers" specialising in cursor-addressing uis.

Depends where you look.

https://davideellis.wordpress.com/2012/08/31/ibm-tivoli-moni...


I take it you haven't heard about: https://charm.sh/


Interesting that Website reliably crashes mobile Firefox (nightly and release) and brave for me.


Works fine on my Pixel 7a using the release version of Firefox (I won't dare touch Brave), fwiw.


What do you mean precisely by "character addressing UI"? I can infer approximately what you mean, but I had never heard that phrase before and could not Google it, so was wondering how precisely you define that as presumably slightly distinct from other more common terms for text mode applications.


thanks! i meant 'cursor-addressing', to avoid the ambiguous term 'tui', which usually (and per https://en.wikipedia.org/wiki/Text-based_user_interface) means cursor-addressing, but nominally also includes actual text-based user interfaces, as seen in e.g. the traditional unix utilities.


I've always seen CLI used for unix style utilities and TUI used for cursor-addressing/ncurses style interfaces fwiw.


You still didnt define what "cursor addressing" means. Its not a common term to use for these UIs and doesnt seem to get to the crux of what separates a typical GUI from these.

For me, the crucial difference is that they're usable over ssh and tmux, not the type of cursor they have (if any).


Not really. There is an ancient curses-based spreadsheet program called "sc" (spreadsheet calculator).

It sounds like "scim" is to "sc" vaguely like "vim" is to "vi": new program with more features cloning/imitating ancient program.

"vi" was written by Bill Joy in 1979.

"sc" by James Gosling in 1981.

sc-im claims to be based on "sc".

It's a direct lineage unrelated to GUI spreadsheets.


Gosling wrote sc? I had no idea. I was an scim user before moving to visidata like another poster mentioned, so I kinda-sorta feel like an sc user.

For those who don't know, James Gosling invented a popular VM-based "write once, test everywhere" programming language named after a tree. Then named after a coffee.


Gosling also invented a structural macro processor for C, in 1989.

Ace: a syntax-driven C preprocessor: https://swtch.com/gosling89ace.pdf

In 1981, Gosling Emacs: https://en.wikipedia.org/wiki/Gosling_Emacs

Richard Stallman used Gosling Emacs as the starting code for GNU Emacs.


For those who don't know, and don't want to have to go off and search to understand the cryptic comment... He's talking about Java. Which in an earlier iteration was known as Oak.


It reminded me of The Twin spreadsheet from the late 1980s. I worked at a plastics plant that used it in their color lab until at least 2013 when I left. There were thousands of color recipes and no one wanted to try and convert all of that to a newer spreadsheet.

https://forum.winworldpc.com/discussion/7590/software-spotli...


No one has gone back for real spreadsheet work tho


The great drawback of TUI app is that are quite unusable from touch devices, or generally devices without a keyboard). If you find a way to make them usable on mobile I think they can get a great comeback


If you can find a way to make touch-friendly interfaces useful on desktop devices with a large screen and a keyboard maybe then they'll take off.

Better yet, make all user interfaces the same as a toaster. Everyone can use a toaster. Bread goes in, push the lever. One universal way of thinking for everyone and everything. No domination by the tyranny of choice.


You might have not seen different kind of tosters.


> If you find a way to make them usable on mobile

And if that requires any tradeoffs like it did for GUIs (no hover, no small elements) it'll end up getting dumbed down for mobile like GUIs did.


Not at all. The shares in a C-corp are securities because they will definitely pass the Howey Test. Also, stocks are considered securities by a statute. It is unclear whether XRP tokens themselves pass the Howey test. (I believe the Howey Test is extremely outdated and needs to be revamped, but that's a different topic.)


1. The signature was created using a private key that corresponds to the address "1Q2TWHE3GMdB6BZKafqwxXtWAWgFt5Jvm3".

2. 1Q2TWHE3GMdB6BZKafqwxXtWAWgFt5Jvm3 is Hal Finney's (Not Satoshi's) address.

3. Hal Finney passed away in 2014.

4. Some coins that belonged to that address were spent in 2017. [1]

It appears that someone else (definitely not Hal) has the private key to that address.

[1] https://www.blockchain.com/btc/tx/70ec308460a38f6de25f89c6ed...


I see. Are you implying whoever has access to Hal's wallet could have produced this signature after his death?


exactly. this has nothing to do with proving it is Santoshi, nor is it a hash collision.

All it means is multiple people have Hal's private key and somehow either Martin is one of them, or he was told to post this message.


That's correct.


Wouldn’t it be likely that his wife or a close friend has the private key?


> It appears that someone else (definitely not Hal) has the private key to that address.

So Paul le Roux, by the message?

> 1Q2TWHE3GMdB6BZKafqwxXtWAWgFt5Jvm3 is Hal Finney's (Not Satoshi's) address.

Where do you get this?

EDIT: I am proposing not that Paul LeRoux is Satoshi, but that he is in possession of Hal's key, and produced that signature as a troll.


No, that particular message could be created by anyone (including people who are not Paul le Roux), who has the key to the 1Q2 address, at any time, past or present.

All we have to go on right now is that someone knows the private key that corresponds to the 1Q2 address and used it sometime before the last hour to generate a hash of a message that says that Paul le Roux sent bitcoin to Hal Finney.


How do we know the message was signed during the last hour and not in 2017 or 2014 or whatever? Does it include the hash of a Bitcoin block created in the last hour?


Your parent didn't write "during the last hour", they wrote "before the last hour"


I would believe it if the signature came from one of Satoshi's addresses, but this is not it.


Maybe the key was inherited by someone? I don't intend to take my cryptos with me to the grave, or redistribute my wealth between holders, however you prefer to see it.


I thought Discord is mostly webview-powered, is it not? If so, this change will make very little difference to the user.


react native =/= electron (and similar frameworks like CEF). The former uses native widgets. The latter uses HTML/CSS rendered by a browser layout engine.


I know that. I am saying that if the app is mostly webviews anyway instead of building the views natively, there would not be much difference between being a fully native app with WebViews or being an RN app with <WebView> components.


It's mostly React Native for the UI, but there's a lot of native code for crypto/secure enclave operations.



If that's really what I wanted, there are many much easier ways than making a full app, such as writing a lame whitepaper and doing a scam ICO. You will see a lot of open-source code from Cipher soon, hopefully that puts your mind at ease.


This is just a trusted RPC connection right? You're not embedding any sort of light (or otherwise) client? Are you running the nodes on the backend, as opposed to outsourcing to someone like infura? What are you running if so (geth, parity, something else) and how (single node or multiple nodes load-balanced)? Curious to hear the setup.


The app uses Infura, just like MetaMask, but future version will allow you to specify your own RPC. Geth/Parity light clients are not quite usable on mobile yet, but they are improving rapidly, so hopefully in the future.


Yes, use the same recovery phrase. I wouldn't recommend making transactions simultaneously on multiple devices though.


Why? They would be separate transactions on Blockchain


Ethereum is different from Bitcoin in that it uses simple account balances, which are easier to deal with in smart contracts. To prevent replay attacks, each account has a nonce, which is included in the transaction.

You can check the blockchain for the current nonce of an account, but if you sent from the same account simultaneously from two devices, both transactions would get the same nonce and one would fail.


That is correct! Thanks for explaining!


You can tap on skip button in the corner but do copy it down as soon as you are able (it can be viewed again in settings screen).

Cipher uses features like the Secure Enclave chip to make things more secure, but obviously the best practice is to treat it as a hot spending wallet and use a hardware wallet to store large amounts.


Is there a way to copy the recovery password as text? I want to store it in my password manager, but typing in 20 words (correctly) passes my threshold for trying out new apps.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: