I think this is a misevaluation of the trust involved. NFT's are using the blockchain to whitewash trust, the blockchain contains a smart contract and a URL. It provides no assurance that the URL contains the same contents as when the NFT was first minted.
With how most NFTs are implemented you need to have trust in the blockchain it self, in the implementation of the smart contract, in the server hosting the referenced metadata URL, and the server hosting the actual digital asset the NFT represents. If trust in any one of these is misplaced it can undermine the trust placed in the others.
The blockchain can not provide more trust than the least trustworthy part of the rest of the NFT chain. Since the URL referenced in the blockchain is likely stored in some single organization's SQL database, the maximum trustworthiness of an NFT is never going to be larger than the trustworthiness of that SQL database.
That is complicated, but also not related to the 5th amendment. Warrants are a part of 4th amendment rights.
The 4th amendment is intended to ensure (among other things) that the government can't search some locations for evidence without first proving they have a good cause for that search.
The 5th amendment is intended to ensure (among other things) that the government can't use force or threats to make you admit to a crime, regardless of if you committed or didn't commit that crime.
The distinction is that a court could grant the right to force someone to put their thumb on a phone, or look at a phone's camera, but they (in some but not all cases) cannot force you to type in your passcode.
The argument is that your fingerprint or face is not "testimony" but a fact of who you are, but your passcode is a testimony, a declaration that you have some specific knowledge.
A phone unlocking is equivalent to it saying "Yes that is my owner/user", and that is not that person testifying, it is the device testifying against that person. Similarly it would be as if someone kept a picture of them committing a crime that was found with a valid warrant, they could not claim that having taken the picture it is their own testimony and can't be used against them. Taking the picture is a past event and requires no compelling of testimony to be used as evidence.
Getting biometrics without a warrant is a contentious issue. There are situations where a warrant is not needed, and these have also been abused to gather biometrics in situations that should have required a warrant but it was denied.
> That is not the same thing. The movie studios don't own the theatre.
They did at one time, courts end it, but isn't even relevant to my point. You said "There is literally no business that allows companies using their property to advertise their competitors." My point is that that is exactly not true.
I am rebutting your incorrect assertion.
It seems like your playing at moving goal posts, make one argument, then when it's shown to be wrong demand that the it has to meet some unrelated criteria to be valid. You never said "There is literally no monopoly that allows companies using their property to advertise their competitors." You said no *business*. You didn't say they had to own all the property, just that it is there property, and to a movie studio, the movie, even as it's being shown in a theater, is there's. They own it and can dictate how it's shown. Except that courts have limited how far those contracts can go. The theater may be the platform to show movies, but the movies are the platform for previews/trailers, no one goes to a theater for the previews. (I mean some of them are cool, but I'm not paying $20 to watch 10 minutes of trailers)
I provided multiple examples, but for some reason you tried to find some wiggle room in one example to try and ignore the rest.
> No, the judge wasn't wrong but you're misframing the decision to make it fit a situation it doesn't. The judge did not rule that Apple's position on App Store payments was illegal. They ruled that Apple was being anti-competitive for "digital mobile gaming transactions"
Have you read the injunction? The one I linked before? It's really really short, it won't take long to read honest.
Ok read it now? How often does it mention games? Once? Exactly one use of the word games? What is the word before games? "Epic"? The word after? "Inc"? So the only mention of games is in the name of one of the parties to the litigation "Epic Games, Inc." There aren't even any phrases that could be considered synonyms. No "entertainment software" no "interactive media", nothing of the sort.
I'm sorry to be so condescending, but as you accuse me of "misframing" this, you yourself are not understanding what the judge ruled. His injunction has no limitations for what kind of applications this applies to. The injection says "Apple Inc. ... are hereby permanently restrained and enjoined from
prohibiting developers from ...". Not "digital mobile gaming" developers, not "mobile gaming" developers not even just "gaming" developers, all developers, all of them, for all types of apps.
But what if I just conceded that point, the judge did only rule on games. Ok, then what is the difference between Epic Games' Fortnight and Amazon's Kindle?
You said:
> because the transactions happen within the game and not simply within the App Store.
How is Kindle different?
- Fortnight existed as a standalone game before it was an iOS app. Kindle existed as a standalone app before it was an iOS app.
- Fortnight had a way to purchase content in game before it was an iOS app. Kindle had a way to purchase content in app before it was an iOS app.
- Fortnight users when logged in see purchased items across devices. Kindle user when logged in see purchased items across devices.
What is it that makes games different? How is Kindle only inside iOS, despite being a service for about 8 months before the Apple App Store can into existence, but Fortnight is not only inside iOS? Are the Fortnight games servers run by Epic Games the magic difference? But Kindle books are delivered by Amazon not Apple, why are Amazon's servers not as magic as Epic's?
> The rules aren't in place to protect shitty business decisions. They're there to prevent monopolization and Apple doesn't have a monopoly.
This is a common misconception, but antitrust is not anti-monopoly, monopoly is not a requirement to violate anti-trust laws. One portion of antitrust is about regulating existing monopolies, another is about preventing new monopolies, but other parts cover other practices like price fixing, collusion, one of these is called vertical restraints. Apply requiring that all apps on their OS use their payment system could be viewed as a vertical restraints.
> No, it's not. Amazon's App Store application doesn't exist without the Apple ecosystem and Apple's customers.
When did I talk about Amazon's App Store? This is about Amazon's Apps on Apple's App store and on iOS.
> Amazon is allowed to advertise anything they want outside of the Apple App Store
True, I mentioned that and rebutted it in my last post.
> The rule is only about advertising for other services within the platform that Apple runs
False, at least in the respect that the Kindle Store is not a platform Apple runs, Apple runs the installations system on iOS, they use that to extend their reach into what other companies run.
> They absolutely can communicate with their customers ...
Amazon can, to use the Kindle app you must have an Amazon account created outside the app, they have the right to communicate outside the app because that point of contact originated outside the app.
Any one not already the size of Amazon that starts as an app on iOS is not allowed to try to extend that relationship outside of iOS. That is why a federal judge felt it necessary to rule that Apple's behavior was against California law.
> There is literally no business that allows companies using their property to advertise their competitors.
Except news papers, TV stations, movie studios, ISPs, phone companies, etc. All of these allow competitors to buy add space on their platforms, or use their platforms to communicate competing offers.
Did you know movie studios once refused to let theaters run their movies if the previews/trailers were for any movies not from the same studio? Courts put a stop to that, now at most a studio can require that some but not all of the previews/trailers be for their films.
Back when long distance phone companies were a thing people cared about in the US, AT&T tried to block their competitors from cold calling companies to get them to switch, they also lost that case.
Yes, none of these companies want to allow their competitors to use their platform, but none of them are allowed by law to stop it.
> Your example about a direct ordering phone number is not analogous at all.
It's not analogous to Apple preventing Amazon from providing links in the app to Amazon's own web site? How?
This is the point of the similarity, you use the Doordash app or website (you use the Apple App Store), you order food (you download an app), when you get your food there is a menu inside that suggests you order direct, maybe even including coupons that give a discount on pickup orders (you open the app and when you pick something to buy you are provided a link to their site instead of an App Store button).
Can you explain where I'm going wrong on that analogy? I know it's not 100% the same, it's an analogy, they are never exactly the same.
> Your whole argument is based on an incorrect understanding of the agreements made to use the App Store and an inaccurate understanding of the limits imposed by apps.
Right back at you. It's curious to me that you seem so adamant to defend a behavior was just ruled illegal. Was the judge wrong? How?
Thought experiment, if Microsoft tomorrow said they own the Windows platform, and they have the right to a cut of all transactions done inside apps on the Windows platform, would you be ok with applications like say Steam or Epic Games Store being required to use the Windows Store to process payments and give some percent to Microsoft? If this is not ok how is it different from Apple's policy for iOS?
One of the rules in Apples App Store policy is that developers are not allowed to communicate with customers out side the app, even if they asked for permission in the app. (They were enjoined against doing this in the recent Epic Games v. Apple ruling [1])
Apple also forbit apps from directly telling people about other purchasing options in the app.
If a customer did download an app, and set up an account, and that app's creator wanted to say hey you have other options to pay us how would they do that? Yes they could do a generic advertising campaign and reach mostly non-customers, but they could not by Apple's rules directedly talk to their own customer base. To use the Doordash analogy this is like saying you can't include a menu with direct ordering phone number with a delivery. I do think this qualifies as "forbid people from telling people they could pay for a purchase outside the app."
The difference is between Apples actual rules and the hypothetical Doordash behaving badly is more about degrees of control and likely hood of working that actual intent. Your own examples don't fit to Apple's behavior any better, DoorDash saying you can't advertise Uber Eats on your menu is nothing like Apple saying Amazon can't advertise Amazon in Amazons own Amazon app. Your using the example of a competitor advertising in the competitions app, that is an apples to oranges comparison, Apple owns the platform, you could argue that Apple can say that Amazon can't advertise their Android tablets in the Kindle app, maybe that would be like your example, but that was never what the issue was.
The opposite question is also important. Should the mobile network my phone is on get a share of all transactions made from my phone? Should my home ISP get a share from purchases made on my home computer? Or the hardware vendor? Or the OS vendor?
The reason Apple gets to ask for a cut of all transactions made on my phone is because they are in a position to control those transactions, not because it's right for them to ask for that cut. They can remove any app that tries to bypass their cut, as was recently ruled in their case against Epic Games.
Like wise Doordash has control, if you want them to pay a driver to carry your food from the restaurant to your home, then they get a cut.
The difference between Doordash and Apple is that Apple forbade anyone with an app in the app store from even telling people that they could pay for a purchase outside the app. For a time the Kindle app would send you to a checkout page in Safari, but Apple forced them to remove that. The comparison would be that any restaurant that worked with Doordash being forced to remove mention that they do pickup orders, if you don't want dine in then you must order with Doordash, even if that technically isnt't true.
To me there is no magic percent where these behaviors should or should not be allowed or regulated. To me it's more about the pattern of 'soft' extortion. "You get value from our platform so we deserve a cut of what you make", sounds a bit too much like "You sure do have a nice app there with some dedicated users, it sure would be bad if something happened to it..."
I don't know that I would pay for and read a tenth as many books as I do if I didn't always have the Kindle app in my pocket. On the other hand if Apple ever removed the Kindle app I'd have a strong reason to switch to Android. Both gain value from the other. Apple insentience to always get the better of that trade seems counter productive.
When the Apple App Store first came out there was no in app purchases. Amazon already had a payment infrastructure so when they released the free Kindle app on iOS it used the Amazon payment system. Apple later added in app purchases and changed the contract terms (as the were allowed to do) to require all apps to only use the App Store for IAP, they allowed Kindle to remain unchanged. The exception as just not forcing Amazon to change their app.
It was allowed under the old rules, then the rules changed, then the Amazon ad these emails were referencing game out. So at the point of these email the Kindle app was out of compliance with the App Store rules, but Apple was allowing it as an exception because they viewed it as a promotion of Apple products. This ad changed their view and now though that the Kindle app on iOS was a promotion of how easy it was to move to Android.
> It's certainly quicker to type, but that's not a good argument enough to make such a drastic change in javascript.
I am so glad this argument has not been winning out in the JavaScript language design community. There are so many wonderful constructs that have been added in the last 20 years that are just sorter ways to write things that could mostly already be done in the language. Many of these features focused on allowing developers to write what they intended to do without having to explicitly construction the intermediate steps to express the mechanics of how that should be carried out using basic language features.
After all why do we need arrow functions when we could just sprinkle our code with `var self = this;` declarations for anonymous functions to bind to, the way it was done in the late 90's and early 00's.
I'd much rather JavaScript adopt succinct ways to write common code patterns and let the developers and the community decide if those constructs are the correct ones to use on a case by case basis.
> APIs have been around for a while. For instance, the painful Simple Object Access Protocol (SOAP) used APIs in the early 2000s, but they really started getting interesting when representational state transfer (REST) came along. REST, which used the ubiquitous HTTP protocol, was lightweight and fun to work with.
Umm, yes, there were no APIs before the 2000s. Even ignoring non-web APIs there were plenty of pre-SOAP attempts at APIs on the web. XML-RPC was created in 1998 and is the direct predecessor to SOAP.
It feels like the author of this post has no historical perspective on the technology he is trying to explain, and if he skipped all the "What is an API" preamble that would be fine, but with it there it feels like an attempt at sounding like an authority that backfired.
I tried to see who this "Jesse Menning" is, but the author link goes to a twitter page for "Jeremy Menning" that hasn't seen use in 10 years. I'm not sure I should really put much trust in a blog post by an author that doesn't even know his own Twitter handle.
If the data is not stored in the git repo itself there is no workable solution. Any offered standard is just a bandaid on the problem.
If a project is renamed or relocated from one name to another it might (and should) preserve issue and merge related information and discussion, but any full URLs will have changed, making full URLs fail in specific cases. Using any form of shortened sequential identifiers will fail when referenced in commits merged in from forks of the project that have their own conflicting identifiers.
To solve this in any real way there needs to be a way that when a project is forked it carries information about issues and merges with it, and when commits from that fork are merged back into the main project, or merges from a fork of a fork are merged all the way back to the original project, all metadata about those merges are carried to the original project.
Linus' argument is that the correct place to store that is in the merge commit's message. That it is the responsibility of the person doing the merge to provide that information, and that GitHub does a bad job of providing tools to do that.
Standard Apple cables already have a chip inside, and USB 3.1 cables are also supposed to have chips inside.
I would also assume they are not paying enough attention to even notice, there is no regulation against them so there is no reason to even train to notice differences in USB cables.
> They probably see thousands of cables and it'd be pretty easy to spot the difference.
If anything seeing thousands of cables will make them less likely to notice anything, change blindness is a real problem in jobs like that.
These are more general purpose than just those attacks, the author of the firmware has demo videos of cables attached to Android and iOS devices that when the payload runs they open the system browser and loads a specific page. Depending on what you can do with a web page at any given time on those devices it could be a springboard.
You could also do some passive/active data gathering. On Windows when you plug in an iOS device, if the device trusts the computer it will allow it to access all the photos and videos on the device. The cable it self could then start grabbing those images and sending them over the WiFi link. I don't know if these cables support that, but the concept is valid.
The cables have 2km WiFi with a directional antenna (presumably on the other end), you could probably get similar range out of most of your devices if your bases station had a directional antenna, but that eliminates much of the value for many WiFi applications.
The cable claims that it's a random 3rd party keyboard when it talks to the Mac, the cable claims it's a random non Apple device when it talks to the keyboard, the keyboard falls back to non-encrypted mode as it's not on a product that supports it.
Man in the middle is hard to prevent when you need to be compatible with incredibly broken insecure legacy protocols.
Apple could maybe go the route that all new Apple keyboards only work with new Macs and iOS devices, but that would mean that they can't work with any existing Apple hardware or third party systems.
The product pages mention custom payloads, in some of the images it looks like some variant of the DuckyScript used in some of the other hak5 products. It likely depends on if what you want to do is supported or if it would need changes to the firmware to accomplish.
Not all market transactions are done to make money on the trade itself, many are done to protect a larger business interest. This is very uncommon on stock markets, but is very common on commodity markets. You don't generally hear much discussion of commodity markets because they are not the big way (at least not today) for people doing trading to make it rich quick.
Most consumer level goods have become insulated from price fluctuations in commodity markets, but there is still some variation at the consumer level in the price of fresh fish and meats, and sometimes fresh fruits and vegetables.
At the scale restaurants buy, and especially large chains or higher scale restaurants, price fluctuations can make a big impact on profitability. Getting tipped off early to a situation that might impact prices can allow a company to lock in a futures contract at the current prices for delivery later on when prices have risen before the people selling know that prices are about to go up.
The result is that the people gathering the data and producing information may not be in a position to get value directly, they are not already trading in those commodity, but people already doing that trading may get value from better or faster information on the market.
It's hard to complain to much about a free product that is a side line to the companies main business... Oh wait, we just lost the free version and it's now the companies main monetization scheme? Well now I care a lot about the little annoying bugs I've been dealing with for the last 3 years.
Proof of direct copying may not be required, if AT&T can instead prove Access and Substantial Similarity.
For access it could be a little tricky, certainly every one that has posted a reply here has had access, and if this post is popular enough it could be argued anyone could or has had access (this happened in some music cases in the last few years).
For Substantial Similarity your definitely in trouble if you have exactly 3 blank lines and probably in trouble if you have 2 or 4 blank lines, but you may be fine if you have like 6 or 12 blank lines.
While I'm being a bit sarcastic about the number of lines being "substantially similar", the legal standard in the US is not if you actually copied something, but if the plaintiff can convince a judge/jury that it's more likely that you copied it than it is that you created it on your own.
The term "Regular Expression" is very often misused, it had a very well defined meaning in the field of formal language theory, but like most terms when barrowed by another field some of that meaning is lost or transformed.
Some documentation has shifted to using terms like "pattern" or "pattern matching expression" to convey the meaning without the baggage.
> Some REs (i.e. the “Perl-compatible” or “extended” Regular Expressions) are Nondeterministic Finite-state Automata or “NFAs”.
That those engines are implemented using an NFA or a DFA does not actually matter for the question of being regular or not. A given pattern may be Regular while another may not be. There are multiple technical reasons these engines are built on NFA's and not DFA's, supporting non-regular expressions is one, but not the only, reason.
Ironically the library called "PCRE" or "Perl-compatible Regular Expressions" is in-fact not "Perl-compatible" (nor regular). It is at the same time both named "Perl-compatible" and absolutely not Perl-compatible. Both PCRE library and the Perl language have evolved and added mutually incompatible features which results in a valid PCRE matching expression failing to compile in Perl and a valid Perl matching expression failing to compile in PCRE.
Just because that is the name doesn't make it true.
With how most NFTs are implemented you need to have trust in the blockchain it self, in the implementation of the smart contract, in the server hosting the referenced metadata URL, and the server hosting the actual digital asset the NFT represents. If trust in any one of these is misplaced it can undermine the trust placed in the others.
The blockchain can not provide more trust than the least trustworthy part of the rest of the NFT chain. Since the URL referenced in the blockchain is likely stored in some single organization's SQL database, the maximum trustworthiness of an NFT is never going to be larger than the trustworthiness of that SQL database.