• 9 Posts
  • 59 Comments
Joined 1 year ago
cake
Cake day: June 11th, 2023

help-circle

  • I’m kinda sad to see it enshittify, for gamers and for those who find it fits their actual collaboration use case, but I also really hate the number forum-format communities that Discord has displaced or prevented from coalescing. Discoverability on Discord is terrible, as is having help available long term, as well as older advice and other content that helps newbies get the culture of a community. Even where the functionality exists, the general “real time” transitory feel of it reduces the quality of content and encourages people to be dicks, since it will all scroll by or be forgotten (if streaming) in a few moments anyway.

    Horses for courses, and my old-ass X-ennial self thinks Discord has been pressed into service on a lot of courses where it’s terrible.


  • This all feels a lot like any low- or mid-range CAD suite that gets acquired by Autodesk, Siemens, or PTC. Promise enough to avoid a revolt, but start eroding with the next release.

    The educational licensing for lock-in is also par for the course. It can be done well (Rhino 3D is legendary for letting small-shop designers use their cheap edu license forever, even commercially), but generally it’s just there to maintain the supply of baby drafters and get subscriptions from employers.










  • From my keebtalk post, which also has more pics:

    It’s early obviously, but I’m optimistic about this one. It feels pretty nice, and the Jades are almost as nice as the Navies, just missing that slight “kerchunk!” that the Navies have. The Jades are a bit snappier, and I agree that they may be ever so slightly louder, but I don’t think they dethrone my dark blue fingerbreakers.

    After my last set of keycaps came out with some fairly obvious alignment issues, I rethought my jig and made a new one that could support 26 1u keys, plus one of arbitrary width. I also went with corner legends instead of centered, as that punishes a lack of accuracy much less, if you can at least get your setup repeatable. Then, I did clusters together in batches (i.e. all alphas in one run, all F keys together, etc.). The result is a much less jarring alignment situation. It would be ideal, if the plastic itself had cooperated. This PBT recipe didn’t like the infusible ink nearly as much as the DSA keycaps on my other no-stabs build. Legends are not as crisp as I’d like, and the colors are pretty muted, but the improved alignment makes this a modest victory.

    Overall, I like (though not quite love) the way they came out, and the overall effect for the board, between the layout, case, and font, is a bit “Apple meets Logitech,” which may or may not be a good thing, but it’s always satisfying to wrap one of these up.




  • My first two DIY builds were orthos, but it sort of didn’t take. I did realize that while I don’t type properly or even all that well, I still don’t particularly need a full size spacebar as I almost always land in the same spot with my right thumb or (forgive me) index finger. I use KMK for my boards, and the debounce is good enough that if I happen to double tap the two spacebars, it won’t register two taps. The rest of the longer keys don’t REALLY need to be that long, and everybody hates lubing and tuning stabs (or they damn well should) anyway.





  • The sense I get is that it is more lazy than anything. The verbiage feels like the fact that designs were public documents was tacked on last minute to satisfy some desire for market segmentation or to create a parts and design library to draw traffic. It would make sense that the company hosting the software would not want the headache of being unable to use your stuff commercially or even of parsing what they could use, since in some sense they always are using everything commercially. Refusing the to thread the needle with their verbiage, though, has left a situation where the Terms of Use say clearly that (1) a design is Content, (2) a free user’s Content is a public document, (3) a free user cannot use their own public documents for commercial use, and (3) a free user grants EVERY OTHER USER a license to sell their public documents.

    1. “End Users’ files, designs, models… (collectively, “Content”).”
    2. “All documents created by a Free Plan User, and all Content contained therein, is made public and therefore considered a Public Document.”
    3. “If you intend to use the Service outside a trial context to create and/or edit intellectual property for commercial purposes (including but not limited to developing designs that are intended to be commercialized and/or used in support of a commercial business), then you agree to upgrade to a paid subscription to the Service.”
    4. “For any Public Document owned by a Free Plan User… Customer grants a worldwide, royalty-free and non-exclusive license to any End User or third party accessing the Public Document to use the intellectual property contained in Customer’s Public Document without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Document, and to permit persons to whom the Document is made available to do the same.”

    The only possible wrinkle is that the ToU distinguish between a “Customer” and an “End User,” so maybe you the customer can grant you the End User the same commercial rights that Joe the slightly shady CNC machinist in Peoria has when he downloads your widget to fabricate and sell. Something tells me that PTC’s license compliance folks don’t interpret things that way, though.