1. Pay attention to the first 2-3 columns, the ones the user immediately sees. E.g. short or hidden id, short but readable name, useful next column (e.g. sales or views or whatever is the most useful data).
2. Put columns that need to be evaluated together close to each other. On desktop it's easy to see 2 numbers even if there's a column in the middle, on mobile it may require scrolling horizontally.
In summary, just focus on what people want to see at a glance and make it easier for them.
I'm just a user suffering the pain, this is an example of a table I need/want to monitor and it's very poorly done, I need total revenue = sum of column 5 + 7, on mobile it's a very bad experience due to column 6 in the middle, unnecessary width of some columns with repeated text, etc.
https://app.vx.tools/income/BfgMdL4FaNHp5zZpD7WMYG5sZUrCWQPE...
There’s a picture at the bottom. I think the text there is a bit more clear (maybe?): you have a cubic surface and want to see if there’s any “straight line” that lives/lies on the surface. It turns out there’s 27 lol.
> To fund development for this critical next stage, we will launch a crowdfunding campaign on a platform such as Indiegogo or Kickstarter.
Great point. I highly recommend crowdsupply for this type of project (extremely technical target customers), especially if this is the first campaign you run, as their team is helping much more on the nuances of running a successful campaign.
(I know this is not the place for ads, and I’m not affiliated though I run crowdfunding campaigns on all the platforms mentioned.)
- bandwidth will be high, say 20-25 TB/mo outgoing
- ram you might be tight, if you have the chance to grow to 384-512 it'd prob be better
- you'll need at least 2 boxes, one for mainnet and one for testnet. Testnet will be "less important" so you can still run a lot of other things on that machine
If I were you, assuming you find this interesting, I'd start a testnet node on your current machine, get practice with it, as I was mentioning keep running your other services. And then if you're convinced you just rent a 2nd machine on any of existing providers/your favorite location to run mainnet.
The whole point about passkeys is to replicate the exact UX of passwords (registration, reset…) but offer protection against phishing, by using public key crypto.
If you want a different UX, use a hardware security key. But these failed to reach consumer adoption.
And of course the FIDO2 standard didn’t specify (yet) a way to move passkeys around, so each implementation chose their own way to do vendor lock in. But this will be fixed in a few iterations.
Author here. My sentiment is mixed. I like the anti-phishing protection of passkeys. I don't like getting locked in to one password manager.
I think passkeys are worth it for ordinary sites/apps that support resetting your password with a simple email, because if you lose your passkey, you can just reset your passkey with a simple email.
The main point of the article is to demystify passkeys, especially passkey resets. Lots of people (especially on HN, even here on this thread) are in the habit of saying that if you lose your passkey, you're going to get permanently locked out of your account.
That's no more true (and no less true) of passkeys than passwords. If you lose your password, you'll have to reset your password. If you lose your passkey, you'll have to reset your passkey, via the exact same process as resetting your password, however easy/hard that may be.
Logging into Google with a passkey feels more perilous to me, especially if Google is your password manager. Losing your Google password is bad, but you can see your Google password. You can write it down and keep it somewhere secure in your house.
If you're using a passkey to login to Google, you've really gotta go to https://myaccount.google.com/security and set up backup codes, and then keep those in a secure vault in your home.
(But, if you can trust yourself to keep a secure backup code, and not give it away to a phisher, then you're not getting much benefit from passkeys, are you?)
> Author here. My sentiment is mixed. I like the anti-phishing protection of passkeys. I don't like getting locked in to one password manager
Most sites that support passkeys let you make more than one passkey. For all sites I've made passkeys for except one I've simply made two passkeys, one using 1Password and one using Apple's Password.
The one site I have not done this with is Premera. They only let you have one passkey as far as I can tell.
We try to sell it for a fair price while still making money. Actually I think there will be comparably priced humanoids coming out from other companies soon
Sorry maybe I should have been more specific. I had Unitree in mind, last time I checked the humanoid with no hands was $20k and each hand was an extra $20k. Yours seems to ship with 2 hands for extra $1k (surprisingly cheap, which is great of course!). I was curious to read more about what the hands are capable of doing.
Oh I see. Yes, we're currently exploring a few different five finger hand options - we will choose whichever option provides the best value. I actually quite like the Inspire hands and we might be able to get a volume discount
I’m getting downvoted!? The author wants a low code system that’s not that expensive and cites hubspot & salesforce. There’s no mention to what he wants to do with it.
Shopify lets you build sites to sell pretty much anything (physical or digital), with a variety of models including recurring subscriptions. There’s a ton you can learn just with Shopify itself.
Then there’s the whole apps ecosystem where you can build connectors for sites to pretty much anything, from digital services to logistic.
And it’s all very cheap. I think it fits the request?
reply