I do have a vivid imagination, but when I imagine doing something disgusting voluntarily I can anticipate it. Not so much when I imagine it from hearing or reading a story and in the middle of imagining things.
So does x86. The difference is license. Just like how Intel and AMD have a VERY different design (implementation) as of now, so does RISC-V. Any vendor can implement it however they want, but they won't have to pay anyone for using RISC-V ISA
I'm being pedantic here but RISC-V is not a hardware architecture as in something that you can send to a manufacturer and get it made. It is an ISA. How you implement those ISA is up to you. Yes there are open implementations but I think it is important to distinguish it.
Yeah exactly why I said that it is my opinion. But it is not just for PCB assembly, a mechanical assembly too if you only have the mechanical drawings will be quite hard to edit. To me, the ability to easily modify and redistribute something is what makes it open source. If you can only replicate something without the right to modify it then it is just source available.
For hardware, there is a difference between knowing the schematics and actually editing the schematics. You can have all the schematics you want, but when you try to modify it to suit your needs you need to either remake the schematic or if the original file is shared, edit that instead. As I said, this is my opinion and the ease of modification is generally also part of open source. For a simple part, yes it is possible to remake it. But a complex assembly requires significant effort. Say a roller needs to be spaced a certain amount. You may want to tweak those distances. Before you manufacture it, you check what parts need to be changed to accommodate for your modification too.
Hmmm, I think that depends very much on the license of the schematic then. Can you share the schematic? Is it in editable form? Yes? Then it is open source, if not then it still is not open source. I think there is a lot to argue about in open sourceness of hardware. And I'm not really qualified to make such an argument, but folks at OpenHardware have IMHO a decent opinion on it.
I think that is quite a different thing no? Those are standard vs open source implementation. Standards make sure we can interop and we can have some high level assumptions/expectations about something. But open source means we also know HOW does it fulfill the standard. A calculator can perform the operation 1 × 4 just fine, but we won't know HOW it does that. It could be that they have a dedicated circuitry for it or its using the addition circuitry with a parameterized loop.
I just wanted to thank OP for this thread since this is quite enlightening about sex workers/industry in general. From where I come from, sex work is technically illegal but not very enforced. But those things also make it hard to regulate the market and make it safe. I learn so much and a lot here.
As for my opinion before I read about all the intricacies of sex industry, wank it first to think with a clear head. Then if you happen to come to the same conclusion, hey, more bang for your bucks!
I think sandboxing the filesystem by default is a good security measure. For Android it makes sense since you can sideload an app and that always carries risks. I think it can be improved on the UX side without compromising much on security but that is not my expertise. And note that I have not used iOS devices in ages too so I don't know how they handle the filesystem now.
Yeah, I am not having issues with battery life so I do not tweak my power settings. The mouse works in wired or bluetooth too, just the dongle is a bit problematic
No, see Gödels Incompleteness theorem