7 ms·
Thread: Tech we can’t use or teach?
- thebiss 3y agoWould the license allow a hobby group to raise funds then create and sell a raspberry pi "hat" that supports thread in a licensed way?
- shermantanktop 3y agoJust be thankful they did this upfront, instead of at the tail end of a painful evolution from an open-source effort to closed-source commercial product, complete with a fig-leaf GitHub with all the interesting bits removed, and a graveyard of abandoned forks. They saved you all that disappointment.
- weinzierl 3y agoAbsolutely, sometimes I feel the mid 2020's will be known as the era of enshittification.
- kevindamm 3y agoIt merited "word of the year" last year, could happen.
- fmajid 3y agoThe Italian word for it, “Merdocene”, sounds even pithier.
- quesera 3y agoMerdocene sounds like geological epoch. Pleistocene, Holocene, etc. WFM!
- fmajid 3y agoExactly, or Anthropocene, describing the changes wrought by humans including climate change.
- kevindamm 3y agoCan we just call it "the scene"?
- bitwize 3y agoThe D in "Système D" (economic concept, not to be confused with the controversial init system) stands for démerder which means "to deshittify". We're gonna see a lot more Système D applied in the future...
- epicureanideal 3y agoLet’s hope the result is that the 2030s are known as the decade when consumers, users of apps, figured out it was worth paying for software from honest developers or companies, rather than getting it for free temporarily and then getting their data used in unexpected ways, enshittification, etc.
- bboygravity 3y agoHi, I'm a time traveller from the 2030s and chuckled a little at the prediction that people would still by writing apps by then.
- leduyquang753 3y agoWhat about when the consumers pay for software and still get their data harvested and the product enshittified?
- josephg 3y agoMicrosoft Windows has entered the chat. Apparently the next insiders version has even more ads in the start menu. This stuff is so horrific.
- einpoklum 3y agoThat is completely irrelevant. A large fraction, if not most, of potential users of software in the world can simply not afford paying any non-trivial amounts of money (by US/European figuring) for software of any kind; they simply don't have such money to spare. Look at median incomes in different countries: https://worldpopulationreview.com/country-rankings/median-income-by-country https://worldpopulationreview.com/country-rankings/median-in...
- generic92034 3y agoCountry-specific pricing is not a new thing, though. After all, if someone in a developing country paid for a smartphone they might be able to also pay for some apps.
- Kiro 3y agoSuch an overused word and in this context it's not even relevant.
- tjoff 3y agoIt is kind of relevant, we have zigbee. Which is a bit quirky, along comes Thread that promises to make it more open, better compatibility between vendors and more modern. If it turns out that big companies use Thread in a way to oppose those goals then I feel that is an attempt to enshittify the entire home-automation ecosystem. Which must be the holy grail of enshittification, I mean it is one thing to make your own product/service worse. But to make everyones products worse? Jackpot!
- Petersipoi 3y agoAt least back up why you think it's irrelevant if you're going to call someone out like this
- huhuhu111 3y ago[dead]
- Signez 3y agoWill we have to wait for a regulation body to come and force it open as soon as it becomes the de facto standard of home communication? I won't make a bet on which one, because I don't want to nag, but we all know which one it will be.
- 9dev 3y agoWell, Google lost against Oracle too, so it appears a mere API specification can be closed down arbitrarily; than is the world we live in. Unless the US gets a lot more tech literate and open minded judges and officials, I doubt that will change for the better. And, looking at their presidential candidates… well.
- franga2000 3y agoI thought Google mostly won against Oracle and the court decided just APIs aren't copyrightable...
- aero_code 3y agoThe court decided the opposite--that APIs are copyrightable. However, the Supreme Court ruled that Google's usage was fair use, so I would agree that Google mostly won. The Supreme Court didn't consider whether APIs are copyrightable (the lower court ruled that) because Google would win regardless because it was fair use. So I'm not sure it matters much whether APIs are copyrightable when what Google did was ruled fair use. I'd prefer if the courts ruled APIs weren't copyrightable, but I think it was still a good result because doing what Google did probably covers about any use case anyway.
- josephg 3y agoI wonder if making a device which uses Threads could be considered fair use in the same way, because implementing threads is required for interoperability with many devices.
- jauntywundrkind 3y ago
- daredoes 3y agoI wouldn't mind if developing for it as a hobbyist was so difficult if it had some quality products and user interfaces.
- cryo 3y agoThe Matter specification has a similar touch. The devil is in the details and due clever marketing people don't understand what they are praising. The real problem here is people who invest money in this anyway.
- RA2lover 3y agoDidn't it go even further by requiring device attestation certificates signed by a licensed PKI provider? I noped out of even considering it as a hobbyist as soon as i noticed that part.
- crote 3y agoCorrect, and the intent is for genuine devices to refuse to work with "fake" ones. All certificates are registered on a blockchain for validation, of course.
- fulafel 3y ago> if you’re a hobbyist without access to some serious throwaway money to join the Thread Group, there is no way to use Thread legally Is this really true? I assume the licensing legalese means patents, and patents don't apply to private tinkering unless there's commerce involved. More generally aside from hobby scope - The absurdity of the monopolies granted by the current patent regime are made obvious by this arrangement: Big companies that have patent portfolios to countersue with can use OpenThread freely, small businesses and startups can't. (Obviously it still sucks and is a major chilling effect)
- IanCal 3y agoThe quoted part above is about shipping products too, so I don't understand why they are using that as an example about not being able to play around with something or write blog posts. Here's the FAQ question > What Would Prevent A Company From Shipping A Product Based On OpenThread Without Joining The Thread Group?
- jauntywundrkind 3y agoAnswer, also quotes in the post: > If developers choose not to join Thread Group and ship products using Thread technology, they are not conferred the IP rights required to practice and ship Thread technology, and may subject themselves to legal action, including but not limited to licensing fees. It feels like even sharing my designs run a major risk of landing me in trouble. This sounds catastrophically hostile to open source in general. If I ever want to make use of what I've built in any even remotely commercial setting, everything I've built feels liable to be infected & polluted with this copyright. I could rip out Threads & still not feel safe. I definitely can't sell a couple copies of this cool thing to other hobbyists on indiegogo. The terms of use essentially outlaw community. Yes, maybe hobbyists can play with this, but they cannot form communities, they cannot share wisdom, they can't sell boards to each other, they can't even talk about the protocol or spec on detail. So yeah, hobbyists arent expressly forbidden. But having any community of hobbyists seems fraught with difficulties. You can only hobbyist by yourself, discussing with no one. Fuck Threads.
- alexashka 3y agoI wonder if this rant would've not existed if the Thread website said 'costs 7500$/yr to use' on the front page. To me, the issue isn't that someone wants people to pay to use their products, it's that they make you work to find out. There really ought to be price transparency for everything, mandated by governments. I'm a dreamer, maaan.
- snthd 3y agoAt least we have wikipedia. https://en.wikipedia.org/wiki/Thread_(network_protocol) https://en.wikipedia.org/wiki/Thread_(network_protocol) >Thread is an IPv6-based, low-power mesh networking technology for Internet of things (IoT) products.[1] The Thread protocol specification is available at no cost; however, this requires agreement and continued adherence to an End-User License Agreement (EULA), which states that "Membership in Thread Group is necessary to implement, practice, and ship Thread technology and Thread Group specifications."[2]
- eviks 3y agoIt's missing the most important part - the sticker price to shock you away from it
- Terretta 3y agoGiven how much R&D expense Thread Group members have invested over the years developing its IP and the commercial value developers get from building on it, compared to, say, Apple's iOS APIs that developers can build on, it's interesting to consider the proportionality of Thread's annual licensing (USD 7500) being 75x Apple's dev license (USD 100). Either one of these is expensive or one of these is cheap.
- actionfromafar 3y ago“you’re a hobbyist without access to some serious throwaway money to join the Thread Group, there is no way to use Thread legally” Well, there’s no way to know until someone finds out if they have relevant patent covers. We need Compaq to clean room copy the stuff and then take the hit if there truly are valid patents…
- erik_seaberg 3y agoA cleanroom process is evidence that you reimplemented without copying, but that's not enough to avoid infringing a patent. You need to redesign to avoid doing anything they claimed, convince the patent office that they made a mistake in granting some or all of the claims, hold a war chest of patents you could counter-sue with, or YOLO: https://paulgraham.com/softwarepatents.html https://paulgraham.com/softwarepatents.html
- actionfromafar 3y agoYes. What I meant about valid patents is that you can’t really know what a patent is worth until you challenge it. There are SO MANY filed patents which are basically just crap, nothing more than camouflage and bluster.
- devjab 3y agoOne of the reasons my city decided to go with LoRawan is exactly because it’s less complicated from the legal side of things. It’s much more complicated to work with, however, and because of Danish telecom laws any such tech comes with ridiculous restrictions that give telecom a sort of monopoly on high speed “internet”. This would also apply to threads though. Anyway, one of the advantages a city gets is that it has a lot of locations to set up antennas. A public school, a library and so on, are all good locations that local citizens wouldn’t have access to. So the trick is to get your city to open up their LoRawan equivalent to the public. At least if you want to deploy things all over the city. Luckily mine does. It also gives you free access to power supplies if your project is benefiting the city (and open), and they are often interested in supporting you financially as well. But as a whole, just don’t use threads.
- tjoff 3y agoThreads would never scale to that anyway? Isn't it a completely different usecase than what Threads was made for?
- lakid 3y agoare you mixing up Thread with Digital Threads ? https://www.ptc.com/en/blogs/corporate/what-is-a-digital-thread https://www.ptc.com/en/blogs/corporate/what-is-a-digital-thr...
- jensenbox 3y agoI have not read the fine print of all of this so my idea here may be dead in the water but... What if we (the community) were to establish an entity that would pay the licensing for whatever required level and pitch in a small amount each towards the fees and we could all then be legal? Essentially the new entity would be licensed and we all would be licensed unter the entity. Fractionating the larger dollar figure across us all.
- Terretta 3y ago> I have not read the fine print of all of this so my idea here may be dead in the water... Many commercial software patent licensing agreements for at least the last twenty years (the timeframe I've noticed contracts tend to have realized open source and networks are a thing) have clauses that specifically prevent or limit this, called "preemptive sublicensing restrictions": https://ipkitten.blogspot.com/2019/10/sublicensing-considerations-in-software.html https://ipkitten.blogspot.com/2019/10/sublicensing-considera... In the "fine print" of the Thread agreements including IP agreement -- reading not very closely and while commenting here -- they ensure this a little obliquely: https://www.threadgroup.org/Becomemember https://www.threadgroup.org/Becomemember In the various agreements they've defined Implementor as what you need to, well, implement it, and it does allow sublicensing to affiliates, but separates out Participants and Associates from Affiliates, and puts a high bar on what can be an Affiliate. Based on the provided definition of "Affiliate" in the context of the Thread Group, Inc. Implementer Participation Agreement, an Implementer cannot simply sign agreements with third parties to make them "Affiliates" in order to sublicense the Implementer's license. According to the definition, an "Affiliate" must be a corporation, company, or other entity that either owns or controls the Implementer, is owned or controlled by the Implementer, or is under common control with the Implementer, with a significant threshold of more than fifty percent ownership or control. This means that the relationship defining an entity as an Affiliate is based on substantial ownership or control rather than merely contractual agreements. An Implementer would need to have a majority ownership or control over another entity for that entity to qualify as an Affiliate and thereby enjoy the rights and privileges, including any sublicensing rights, granted under the Implementer's license. This ensures that Affiliates are closely tied to the primary Participant, maintaining a direct and substantial connection rather than a loose contractual relationship. // IANAL, YMMV, ask your attorney, standard disclaimers apply
- einpoklum 3y ago> if you’re a hobbyist without access to some serious throwaway money to join > the Thread Group, there is no way to use Thread legally - the license does > not include an exception for non-commercial uses. Well, in this situation, and assuming Thread is technically worthwhile - perhaps people would start using it "illegally" (with or without quotes). If such use is wide enough, it might get effectively legalized, albeit gradually.
- crote 3y agoDon't worry, the protocol is explicitly designed to prevent it from interacting with "fake" devices. Your device needs to present a special cryptographic certificate in order to work properly.
- surajrmal 3y agoYou're thinking about matter
- advisedwang 3y agoPirate adoption just helps cement thread as the winner in the IoT space. Which forces organizations in the IoT space to use thread. And they are afraid of being sued, so will follow Thread rules. So tactically I think this actually plays against making it effectively legalized.
- einpoklum 3y agoI wonder if that's true. I mean, think of what happened with DVD copying: Supposedly, everyone bought into a DRM-laden scheme; but it got circumvented into eventual irrelevance, will all-region readers pretty much the norm after some point. But - it's not impossible that what you're describing is what will end up happening. Question is - is there a worthwhile alternative?
- odo1242 3y agoDo these license terms apply if you use OpenThread directly without ever agreeing to the license on the Thread specification? I don’t see how you could be sued if you never agreed to anything except the BSD license lol
- p_l 3y agoSimilar to how you have to join certain patent pools even if you have otherwise an open license to the code.
- 542458 3y agoThe BSD license just selectively releases the copyright on the openthread code. It doesn’t affect other legal constructs, like patents or copyrights outside the repo.
- josephg 3y agoWhat are “copyrights outside the repo”? The BSD license doesn’t grant any patent or trademark rights. But how would copyright cause problems?
- 542458 3y agoOpenThread is by Google, and not the thread group. Google has released their copyright claims with the BSD license, but the thread group could still C&D you for copyright issues I.e., that your project that includes openthread code violates their spec’s copyright.
- denton-scratch 3y ago> OpenThread is by Google, and not the thread group. Wow. So Google is in the Thread Group, and so is licensed to practice and ship the technology; which they do, in the form of OpenThread, under a permissive licence. BUT anyone that uses OpenThread for anything at all is exposed to legal action unless they cough up the fees. Is that right? So this is hard for me to understand: Google's OpenThread code is open to be inspected, and you can contribute to it, under a BSD-like licence; but Thread Group holds the IP, and reserves the right to sue. As always, the patents covering it are not listed, and some of them might be submarines. I don't see why it's called "Open" Thread, if you probably can't even use the library without a Thread Group licence.
- indeyets 3y agoYup. Just use zigbee. 3.x is open and well specified. And dongle-bridges for HomeAssistant are cheap
- alfiedotwtf 3y agoPrediction: the world will move on and probably choose something less wrapped up in a legal Trojan. Although not IP based, LoRa is pretty neat. Slow, but so easy to play around with
- Petersipoi 3y ago"Slow" meaning what exactly? There is going to be a delay between pushing the button on my phone and the lights turning off? Or is it more a "theoretical" slow that doesn't matter too much in practice?
- ianburrell 3y agoThe maximum bandwidth for LoRa is 27 kbps. That is shared with everyone in 5mi range. Home automation doesn't use much bandwidth but enough users will saturate the channel. LoRa is perfect for sensor networks that it was designed for, and good for mesh messaging as long as it stays niche.
- oohshiny 3y agoI'm not super familiar with licensing at this kind of level - how does the licensing for Thread compare to e.g. Bluetooth, which also requires payment to integrate into products? https://www.bluetooth.com/develop-with-bluetooth/join/membership-benefits/ https://www.bluetooth.com/develop-with-bluetooth/join/member... (I've also been playing around with Thread this week, as it happens. Surprised how easy it was to flash the example project to an ESP32 and start pinging it from my laptop)
- squarefoot 3y agoI'm also not familiar with this legalese stuff, however in the case of Bluetooth, it has been "illegally" implemented in many (mostly imported from far east) devices that use it but don't show its complete name. If you encounter a Bluetooth device that claims "BT version x" compatibility and not Bluetooth version X, then it might be one of them. This makes me think that should Thread gain some traction among users, cheap clones implementing it under a similar name, yet without any licensing, would appear shortly on sale at the usual vendors.
- nox101 3y agoAnd Apple and Google signed up for this.
- scotty79 3y ago> If you’re like me and want to write a series of blog posts about how Thread works, there’s also no legal way. I feel like their conditions are refering to manufacturing and delivering products that use Thread tecg to some third party (selling, gifting, possibly renting). Not about teaching, publishing or experimenting. As long as you don't transfer what you've built to another person you should be fine. Am I misreading?
- advisedwang 3y agoThe section of the license agreement excerpted: > Thread Group, Inc. […] hereby grants you a […] license […] to view, download, save, reproduce and use the Specification solely for your own internal purposes uses the term "internal purposes" which doesn't seem to include writing a blog post for the external world to see.
- scotty79 3y agoWhen you write a piece that you publish externally the research you do for it is still done by you internally.
- maufl 3y agoI'm a little confused, I thought Thread was exclusively based on open standards, like 6LowPAN, that already existed before Thread. How can a licence be required for those? I understand the application layer Matter is new (although also using open standards like CoAP) and might not be that open.
- ianburrell 3y agoThread adds mesh networking on top of 6LowPAN. Thread, and Zigbee and ZWave, don’t have range to cover whole house so need relays and added mesh.
- gdcbe 3y agoThe latest “Decoder” episode was about local smart homes. Mainly about “Matter”, but also about Thread: https://podcasts.apple.com/be/podcast/decoder-with-nilay-patel/id1011668648?i=1000655034698 https://podcasts.apple.com/be/podcast/decoder-with-nilay-pat... Might be of interest if Thread is of interest to you.
- advisedwang 3y agoDoes it touch on the legal issue this post is about at all?
- gdcbe 3y agoNot at all. That is why I did not mention the legal part. Which is a bit disappointing as the host has a lawyer background. Oh well…
- zackmorris 3y agoThis tickles my spidey sense. Real tech is what we can't use or teach, that Neo lived for in the Matrix, stuff like: Tor Browser, BitTorrent, pre-Microsoft Skype, WebRTC, Bitcoin, etc etc etc. It's anything that lets the mind seek the truth uninhibited to get closer to the divine. The tech purgatory we live in today between utopia and dystopia is mostly walled gardens and surveillance capitalism. We pay a fortune for 5G and streaming services that technically have no reason to exist. It would be borderline trivial to develop real p2p networking for smartphones that self-organizes with others near them to share some fraction of their bandwidth and create a darknet. Like BitTorrent, performance would increase with the number of peers, so it would run faster at a festival for example, not slower. Which means that a gigabit radio would fully saturate and we'd be enjoying internet speeds perhaps 10-1000 times faster than we have now, even millions of times faster when the protocol runs on wired networks. Maybe something like Thread would facilitate the creation of a p2p network running on and alongside existing infrastructure. I believe that this free p2p network should have been developed around 2007 when the iPhone and Facebook exploded, but greed took us into this alternate timeline where expenses rise faster than wages so we never have the time, money or resources to escape the rat race long enough to get the real work done that gets us closer to a Star Trek UBI economy and self-actualization. Meanwhile there are countless Mark Zuckerbergs, 1000 billionaires and millions of tech influencers who have won the internet lottery but don't pursue the goals that I'm talking about here. They just seem to build out ever more infrastructure to expand their wealth, creating a black hole that shrinks the wealth of the working class. I can only think of a handful of benefactors like MacKenzie Scott who might do it in reverse and seek out eager minds to offer them what they need to work at the pace they're capable of outside the status quo. Which brings me to my point: the legalese obfuscating the Thread protocol isn't to protect their working group, but to prevent the disruption of the status quo in order to protect the fortunes of the biggest tech companies. The thing is, we're crossing thresholds now where I don't think a lot of people under 50 expect the future to get better. They're waiting to have children because they don't have enough money. Children are dying in proxy wars and we can't even call out the political party responsible because the other one is scarier. We're facing enormous geopolitical threats like the rise of authoritarianism and we can't even call it out because we depend on products made by child labor in those same countries, created using minerals and fossil fuels which only exist there. I mean this is like, really serious stuff. If we want to actually invent the real innovation that heals the world and improves the quality of life for everyone, it starts with the most fundamental disruptive tech like this.
- kazinator 3y agoI wouldn't use anything called Thread regardless of its qualifications and pedigree, because I don't want to face months and years of meetings in which people will be be forever heard explaining whether they are talking about operating system scheduler threads, or the framework by that name. (Imagine non-native English speakers who don't distinguish plurals like "threads" and "thread" talking to other such speakers). Just kill me now.
- mindcrime 3y agoI had never heard of Thread until just now... and I wish I still had not heard of it. Seriously, I don't need more reasons to be angry at the world. And I was having such a good day to boot! Seriously though, I agree with the other poster who suggested just avoiding this as much as possible and hope it dies off. I definitely wouldn't encourage anyone to actually embrace or adopt this. :-(