Kind of like the “uncooked spaghetti length” sorting algorithm: gravity. Hold them in your fist vertically, let them gently fall to a flat surface. Sorted.
Because it is exercise for the imaginative mind. Reading can force a reader to build worlds. Some readers are good at this, others need practice. To call reading “consumptive” is severely minimizing literature’s impact on communication throughout human history.
Even looking back at my mother reading Stephen King and romance novels … her reading undoubtedly shaped her and helped her understand the world and her experiences within it.
Note: this comment written from the bathtub after putting down “The Stand” by Stephen King, you know, one of those “little value” books.
Blending hot liquids requires care because turning on and heating the air causes the lid to blow off. Most blenders are limited by physics. Vitamix have an analog dial for speed which allows you to heat the air more slowly. Turning off bubble? Maybe I’ve experienced that … but seems like an inexperienced operator with hot liquids and powerful motors is just a recipe for disaster.
TeleGuard is an app downloaded more a million times that markets itself as a secure way to chat. The app uploads users’ private keys to the company’s server, and makes decryption of messages trivial.
From DYMO: Dear user, Thank you for contacting [DYMO]. I am sorry to hear about the inconvenience you are experiencing.
Kindly be informed, that unfortunately, but the DYMO Label Software v.8. is incompatible with the new macOS 26 Tahoe. The software is officially obsolete, we do not develop it anymore. The last update for it was introduced when Apple released their macOS 11 Big Sur, it was in 2020. The printers you have, with the exception of LabelWriter 450, are incompatible with the current software.
LabelWriter Duo and LabelManager PnP Wireless are obsolete for some time now (keep in mind that LabelWriter Duo is a 20 years old printer) and there are no drivers for them in a our current DYMO Connect software.
LabelWriter 450 was still being manufactured when the DYMO Connect was released, therefore drivers for that model were and still are included in the software.
Those older models would be working on an older OS (up to macOS Sequoia) and on Windows PC. Once again, I am sorry for the inconvenience you are experiencing.
I deeply want to understand and solve this problem. I’m an indie dev that created a desktop app (electron) to design and print labels. I sell a one-time license for $147 but also a subscription for $14.99/month. About 20% of my revenue is MRR. It’s up to the user, and they seem to love it when they have this choice.
Is it sustainable for me? I think so. I license per computer. My largest customers have 20+ computers (grocers and franchises). My competition is 2-3x my price, and require yearly support contracts.
I purposefully do NOT enable auto updates because when label printing works you don’t want it breaking because I failed to catch a regression. Users can downgrade and their subscription still works.
My subscription server/license system is custom built on jwt, so I effectively embed license information inside the signed token and the app verifies authenticity using a public key. Thank you, node and react.
So why buys the subscription? Mainly four types of users:
1) seasonal, such as farms who only label a few months a year
2) users who can afford $15 now but not $147
3) users who can put a $15 monthly charge on the cc without filling out an expense form
4) suspicious users, who then fall in love, cancel and convert to a one time license
Yet, I don’t offer anything from the cloud. Yet …
I’m about ready to deploy a “cloud rendering” service that lets users upload a saved design file, and then you can call an API with variables that get rendered into the label result (barcodes, hide/show logic, color). But here’s the kicker, the result can be a bitmap image, or it can be the base64 data to send to the printer to achieve the exact label you need to print. With this solution you could effectively offload all design of labels from within your app, but still interface with the messy world of label printers.
For this last bit subscriptions make sense. I’m offering a monthly service that costs me money.
I’ve lived 20 years as an amateur SQL database designer and last year I designed my first production nosql schema on mongo. Nosql is a different world... collections, embedded documents. I’m not sure it’s 100% “correct” but it’s working great for me so far.
My project is a license server for my electron app. The tech stack is a joy: mongo/mongoose, express, graphql, JWT, all with a React web front end. Payments by Stripe. The actual licenses are the signed JWT vended by the graphql API (not to be confused with the totally separate JWT for auth).
The main goal is to sell software so I license by machine fingerprint (node module on electron).
It’s been running for over 6 months without issue. I’m just beginning to start architecting an update where I allow a subscription model similar to Jetbrains Perpetual Fallback license, but slightly different in favor of the user. I’ve taken a lot of notes from comments at https://news.ycombinator.com/item?id=17007036
Here’s what I’m thinking so far:
A) Non-Expiring License at $97.99. Unlimited bug fixes for that one version.
or
B) Expiring License at $9.79/month, and you always have access to the latest version. After 12 consecutive payments you are granted a Non-Expiring License for the most recent version at the time of each payment.
Creator of the mydpi label printer and Label LIVE printing software.
https://label.live https://mydpi.com https://semireg.com