throwaway92394

Don't get me wrong I do too. I'd prefer it if everything just used USB C.

I just wanted to point out that it's not universally superior to micro USB or lightning, and there are places it could be improved.

You run into the same issue you do with 2FA -

I cannot remember my own SSN. What happens if I lose my license, SSN, and master password manager password in a fire? What happens if someone has a stroke and forgets a recent pin code, etc.

Do I go to my state and request new IDs? How do they authenticate me?

So in the US you can do "credit freezes" which prevent people from taking out new loans/new cards in your name.

HOWEVER - you can't do anything about the fact they can call up your bank, say "I forgot my password" and then give them your SSN. Your bank will happily reset the password for them. If someone has your SSN they essentially have everything they need to get access to any of your financial, medical, or utility accounts, and can also use it for KYC/AML to open say a crypto account in your name. You cannot do anything to prevent this option.

But more importantly - can we embed ID3v2 inside ID3v2?

> For the sake of simplicity 2-of-2 multisig that downgrades to 1-of-2 multisig over time should capture the essence of how these notes work. > Users can always claim funds after the expiration date of January 3rd 2029 using the user key stored on the note.

Interesting, thank you. That does seem more reasonable to me. Best of luck with your project.

I'm not defending github specifically, I have no experience with the customer service and have no reason to beleive they are or aren't garbage. I'll assume they are garbage.

To be fair, what do you expect the first representative to do/say? They responded in 3 hours, and it's unlikely they can do much beyond escalate this issue internally. We can't expect them to say "We're going to do sweeping changes" at this point.

Github in the past has done sweeping changes for things such as youtube-dl. They created a large blog post about it, including having both programmers and laywers review every DMCA request, and allowing the most minimal amount of changes to comply, etc. That type of response takes time and coordination.

Even cloudflare with their CEO/CTO can't offer sweeping changes in a HN comment. There's layers to this. You can only really expect damage control from a HN comment.

> We will have a security overview doc up soon, we ran out of time to have it ready today.

I mean this respectfully - why would you release a cryptographic method of transferring money - without going into detail of how it actually works? That's kinda the entire point of cryptocurrency, that we have a way to be mathematically confident the money is safe - but you didn't tell us the math. Especially on HN were a lot of the audience is technical enough to want to and be able to verify it to some degree.

I see you have patent US10896412B2, which honestly I have to ask how this is any different from any other hardware wallet?

> A physical cryptocurrency may comprise a physical medium and an attached processor.

I read some of the details (admittedly not all) and I'm still unsure how this is different from any other hardware wallet. AFAIK this is just a hardware wallet that exposes it's public key, then exposes it's private key when you cut the wire? Then we still need your signature to transfer the crypto, which is so double spend is prevented?

Also, if your servers go down or you're hacked or rm -rf dir/ * happens, will all the notes become unusable? Are we relying on you to maintain servers indefinitely?

> Innovation is overrated. And standardising is not blocking.

Hard disagree? Both lightning and USB C were massive improvements in durability compared to Micro USB - I'd argue lightning is still better in that regard, because there's no thin piece inside the phone that can break (did phone repair, and 99% of the time a "broken" iphone port was just stuck lint).

USB C is not universally better then then Micro, namely it has a much larger footprint both on the connector side and the PCB.

> Will EU block innovation?

So my question is - if there's a new USB standard connector that's smaller, or is inside-out for better durability - is it now prevented from being used?

Or apple's iCloud (see their passkey thing also currently on the front page)

EDIT: Yes you don't need to use a syncing service. But it will be important for it to be portable between syncing services, as that is what most consumers will be using.

Does anyone know how this/FIDO/Webauthn affect privacy? How well supported are alt accounts? Are they easy to tell they're from the same signer?

I figure privacy is fine as long as the implementations allow you to select which account to login with. Is this currently a thing? From everything I read it seems like the current implementations are only meant to support one identity?

EDIT: These are great responses, also curious if anyone is aware if Apple's current implementation supports multiple identities?

> Unfortunately only mobile OSes are on the forefront of this.

I'm not sure why the OS would have to manage this. For example when using electron you can use node's vm and run js in a seperate context. Its a seperate process but doesn't require anything special from the os for it.

mobile OSes do sandbox the entire program usually by default though.

Ubuntu sorta tried to with snapd. Windows tried to with UWP.

Yeah my impression is they're all marketing and care relatively little about privacy. How you can claim to care about privacy but still require an email is beyond me.

> In fact, they get paid well to do it. Your typical family law attorney should be arrested, tried and convicted, and they've destroyed countless families, harmed countless children.

I was with you up until this. While I understand the view that what many attorneys do is immoral or wrong - generally speaking to my knowledge there isn't widespread illegal behavior?

I understand but don't fully agree with the view that laywers are "evil" - but the way I see it is they are skilled at playing by the rules of the law. This makes them incredibly powerful (for both sides of people that can afford it), but if they are generally playing by the law - thus not arrestable. Tearing a family apart because the mother is an A hole and lies about things the father does might be immoral - but it's not illegal for an attorney to represent them.

Add no degree. Many especially in CS might even be highly skilled but have no degree to show for it.

EDIT: And only speak e̶n̶g̶l̶i̶s̶h̶ a single language.

> Personally I'd like to see the fairness doctrine reinstated

That's not going to help at all with online media as that's only broadcast licenses which to my knowledge only affects operators of a broadcast TV, Audio Radio (as in AM/FM/SSB/etc), or other radio station - meaning the internet, cable, and satellite (not sure how satellite broadcast licensing works) are unaffected by this. Also it only affects the holder - ie DishTV - not the channels themselves that DishTV is transmitting

And I have no idea how you adapt this for the internet - broadcast licenses were relatively hard to get, relatively expensive to operate, and generally unavailable to most people, edit: and had limited availability. With the internet anyone can make a blog for free in 5 minutes.

EDIT: I think you'll have a lot of 1st amendment problems here. To be honest I'm not sure how the FCC was allowed to do it. To my knowledge the FCC cannot enforce this for cable/internet - I think that would have to be the FTC. But I really doubt this be found to not violate the 1st amendment with the internet.

EDIT 2: > The courts reasoned that the scarcity of the broadcast spectrum, which limited the opportunity for access to the airwaves, created a need for the doctrine.

It looks like the supreme court at the time ruled that because of the limited number of broadcast stations it made sense for the FCC to regulate it in this manor. Because of the lack of scarcity of resources for the internet, I highly doubt the FTC would be allowed to do the same.

Mullvad isn't small, and I'm not sure how Nord specifically compares, but its probaubly worth noting they mostly use 100TB, Tzulo, Quadranet, M247, and 31173. They use a bunch of others but not much.

Mullvad for obvious reasons is used for less... wonderful usecases. It's not uncommon for websites to block you due to abuse from that exit. ASN blocking is rather common with mullvad too though that's less avoidable.

I have less info on Nord, although I can see it has about 4x the ip's. No idea if they are more diverse network wise. Their accepted payment methods suck though.

> CLI programs tend to be FOSS

I think this is more likely because they're often made (or at least started) by individuals as a hobby or side project, not as a commercial venture. CLI is generally easier to develop then GUIs especially cross-platform.

> GUI programs tend to be proprietary and non-gratis.

GUIs require so much more work, especially for cross platform. If engineers are paid for their time then this is worth it.

Granted electron has made it far easier - you still need to be essentially a full stack developer to make a GUI with it.

That's not a good solution because it makes the law ambiguous as to where it should be enforced.

The better solution is to treat it like alcohol - legalize it but make being a nuisance still be a violation (ie Disorderly Conduct and Public Intoxication). This makes it clear it shouldn't be enforced say in a night club or likely a homeless camp - but still allows police to intervene with people causing problems.

That's a setting you can configure. You can also choose whether it shows the sender's name.

There's reasons unrelated to this for why you want to not show the message/sender - namely devices like a desktop you might be screensharing from or if you're concerned about someone seeing it over your shoulder.

I almost leaked a message just taking a screenshot because I didn't notice the notification immediately so I keep it disabled.

To put it mildly - this is unrealistic in the US except for major cities. Even then, depending on the city and where in the city, its going to be very difficult to convince and implement methods of cutting cars.

While I think it's a good idea I just don't see this happening in the majority of the US other then major cities. In my state I just don't see how it would be possible given people commute 30+ miles regularly.

Forgive me if this is a dumb question -

Assuming you're an employee with a relatively small number of shares (in terms of company control) - what's the point of shares if you can't sell them? Just _in case_ you can sell them later? Some type of dividend/profit sharing (which seems unlikely for a startup)?

The original comment was

> iPhone push notifications could only be sent with a signing key tied to the same developer account as used to publish the client application.

> That meant it was impossible to send push notifications from your own XMPP server to a generic XMPP client written by someone else.

and you were replying to

> This restriction that push notifications must only come from the developer’s server is a restriction imposed by Apple and their App Store.

So I'm confused as to what you mean.

> An __off device__ request that is processed server to server.

> ... They are portable (very smart) terminals ...

How does this relate to methods of reliably pushing notifications to an iPhone?

I apologize I'm not sure what you mean by mothership, I'll assume you mean the core API's the OS presents. I mean that's how requests already work? You ask the system to handle the network for you and it passes the app data?

In the context of notifications this isn't an issue for when the app is in the foreground. But when it's in the background the app's event loop isn't ran consistently, so you might not get the notification for hours. To my knowledge the ONLY way to consistently push notifications for apps in the background is through apple's push gateways.

What happens if they waive the loan? Does it count as LTCG + the income tax on the loan amount?

> should trigger background actions

Because of the way iOS works nowadays, you cannot reliably do this for notifications because you can't run apps in the background reliably for this purpose.

> allow that community's chosen point of contact to have push notification capabilities

This is what push notifications are?

Well I mean this article is demoing a 28% improvement (if I did my math right) for json parsing.

Sure AVX-512 is only applicable to specific workloads, and even many of those workloads the cost/opportunity of optimizing for AVX-512 might not be worth it. But there clearly ARE usecases that would benefit, and it might be worth it for more consumer applications to optimize for AVX-512 - but only if it can be used.

The way I see it is that the benefit of optimizing for AVX-512 is far higher if it becomes normal for consumer CPUs to have it. A 28% improvement is pretty decent, but it's only worth implementing if enough people can utilize it.

I'm more familiar with traditional retail options, but I'm confused.

I understand why the employees would want a loan - they need money to buy the shares required to exercise the loan - and I guess they can't do it through a normal broker?

If the employees Exercise-to-sell-to-cover or Exercise-to-sell they should be fine right because they would have closed the loan? This would explain why so many took the loan but so few of the layoffs were affected.

Is the only issue the ones that didn't Exercise-to-sell? I understand that tax will need to be paid but I'm not sure what benefit they'd have would be?

Unless, its because the capital gains + loan rate < income tax?

I mentioned it in another comment, but while that does lower the bandwidth of a single frame, its not actually an issue. There's several DRM techniques that can survive a crappy camera recording in a theater.

"compression resistant watermark" turns up some good resources for it. QR codes are another good example of noise tolerant data transmission (fun fact - having logos in a QR code isn't part of the spec, you're literally covering the QR code but the error-correction can handle it).

The best way I can describe it is that humans can still read text in compressed videos. The worse the compression/noise the larger the text needs to be, but we can still read it.

Compression will limit the bandwidth of a given frame but you can work around it.

Some forms of DRM are already essentially this, compression - and even crappy camera recording from a theater - resistant DRM that is essentially stegonagraphy (you can't visually tell its there) exist.

EDIT: "compression resistant watermark" is a good search phrase if anyone is curious

Just gotta add some good 'ol steganography