Michabo v0.1 release (future plans)
The primary focus for Michabo v0.2 will be the Plugin system and (on traditional UNIX systems) the D-Bus interface.
The Plugin system and D-Bus IPC will build the foundation of this “bridging the fediverse and desktop computing” design goal. These systems will allow for desktop components to interact with each other.
For example, it will be possible for you to share what you are listening to on Audacious or Spotify just by clicking a share button. This is just one of many possibilities unlocked by the Plugin and IPC components.
Because all of this work is being done in the open where the community can observe, we hope that it inspires other people working in the client space to follow our design guidance and specifications to enable these same experiences in their desktop environments and clients.
Michabo represents significant strategic value for the entire fediverse moving forward: the transformation of desktop computing into a social, collaborative experience is something that the proprietary services have been unable to accomplish. They have been unable to accomplish this level of integration because their business model prevents it. We, however, do not have such business models, and that is truly our greatest asset — we are empowered to build the technology people actually want without worrying about profitability.
I intend to write more about this in a blog soon, but this is a major part of the puzzle that, if we can solve it, will give us a big advantage that should be compelling enough to cancel out the user lock-in problem imposed by the proprietary walled gardens. If users can do cool shit and it just works, then they have a compelling reason to push their friends to come join them in the fediverse.
@agudbrandson I suppose the alternative would be to run a query that populates the missing data with /something/. That would make the warning go away, but whatever that /something/ is would not likely be true and that would need to be redone against new records if the underlying data entry problem isn't fixed.
@agudbrandson These changes should not affect existing roasting records and will not impact any saved profiles.
@agudbrandson My understanding of things is that as you enter correct green coffee data for future batches, the reports against that data should no longer have the note you're complaining of. Is this not true?
In any case, I'm reworking Typica's handling of green coffee inventory and will need to make a lot of interface changes for anything that touches that for the 1.10 release that I'm hoping to have the time to finish late summer/early fall.
@agudbrandson The simplification notice should only be visible when batch data cannot be requested with the query specified on line 178 in Windows/batchdetailsnew.xml
I believe this was originally done because Typica allowed you to save batch data without green coffees properly specified, but any failure on that query will trigger the fallback case.
The real solution is for future data to be properly entered: coffee purchase records and weight of which green coffees used for the batch.
@gnomon I try, though she would like me to stay home more (her preferred schedule for me would be 36 hours at home for every 8 hours out)
@neal selling stacks of ebook readers painted with the book cover that can only read that single book :thdnking_face:
@cpsdqs A brick and mortar ebook shop could be really cool. I'm imagining shelves full of epaper readers of various age with a book pre-loaded and set to a random page for browsing.
https://social.typica.us/ is now running Mastodon 2.9.0. Also, this is apparently my 3,003rd toot. Awoo!
@gnomon Just hanging out, smelling the grass, enjoying the yard.
Amie Wilkinson’s Only Constant Is Change | Quanta Magazine https://www.quantamagazine.org/amie-wilkinsons-only-constant-is-change-20190613/
Author of Typica software for coffee roasters.
This is a place for Typica users to connect and chat, but toots need not be related to that program or coffee roasting.