In the past I found it useful to design and layout a pen-and-paper role playing game book and export it as a print-ready PDF i could send to the printer(s).
Specifically, it has CMYK support, allowed me to layout images and text side-by-side and/or overlapping, along with shaded backgrounds for readability and emphasis.
Most books didn't require something this heavy, but the images were a pain without it.
> Typically, research has focussed on synaesthetic musicians such as the composer, Messiaen, who experienced colours when hearing music. This new inquiry investigates and develops a novel approach:
> Can music be composed to evoke cross-modal sensory experiences such as taste, touch or smell in a general audience?
> From principles derived from current research, can a methodology be devised to evoke novel cross-modal sensory experiences through musical composition?
Since you say you've been following it, any idea what's going on with modems on postmarketOS? Is there any chance of getting working calls/SMS/data working on conventional phones or is that only likely to work on open source stuff like PinePhone?
I think I've laid the foundation for supporting Qualcomm modems with ofono (committed to the pmOS repos.) My device has a vendor kernel, and I helped someone else with a mainline kernel. I haven't seen much movement other than that, maybe due to lack of interest or skill in potential developers. (Each device needs a few custom bits like firmware packaged.) Another problem might be a lack of usable GUI to actually use the modem features, but I'm not up to speed on recent progress.
I haven't touched the code in a couple of years, but I wrote something combining Jekyll, Pandoc, and custom LaTeX templates for publishing my wife's novels (ebook and print).
The first time I really started thinking about this was years ago after watching the recycling episode of "Penn & Teller: Bullshit" where they essentially warn that many recycling programs consist of shipping our waste elsewhere for someone else to deal with and that some day the countries we send our "recycling"/waste to will likely get sick of it and start rejecting it and we'll be fucked.
Funny how this came up here. Just a couple of days ago, I was debating with my brother about recycling and told him to look up an old Penn & Teller episode on this topic. That episode really left an impact on me and looks like many others.
While I basically agree, one of the arguments in the episode (as I remember it, it's been a while) is that since we ship it away, we don't see the negative results of our lifestyle choices, making the problems created easier to ignore.
Also, they argue that modern landfills _can_ be pretty damned "green", capturing the heat/gases created and using them to generate power.
But since we've prioritized and financially incentivized recycling (shipping everything somewhere else) we haven't prioritized responsible ways to manage waste locally and once our waste gets rejected we'll likely to be playing catch-up.
The problem is mis-representing what's in the shipment.
(There's probably a lot of plausible deniability in the system. People throw a lot of trash into recycling bins for lots of reasons, including ignorance or laziness. Trash companies don't take responsibility to make sure that's what's in the bin is actually what's supposed to be there.)
Read the article. There's dirty diapers mixed in with so-called "recyclables."
It's a whole bidirectional cascade of misrepresentation I think: every time the materials change hands, the output side passes on the quality/purity promise from upstream, but more optimistic within an almost reasonable error margin. In the same transaction, the input side passes on the responsible handling promise of their downstream partner, but more optimistic, within an almost reasonable error margin.
How many intermediate subcontracting steps would it take to allow the original source tho pay for (supposedly) perfectly clean full reuse recycling of a toxic mess, and the final sink to dump (supposedly) perfectly harmless materials into the sea?
- each object can have a relationship to another (related, blocks, duplicates)
- each object offers a markdown text area, lists, github PR links/integration, comments, and can be moved between various stages (standard scrum stages or your own custom ones)
- each object can be assigned multiple owners, requesters, and followers
- each object can be tagged
- search by title, tag, owner, state, etc.
- each object can have files uploaded and attached
This allows me to track why the work was done, how the work was done, and what work was done, while providing a nice README as a comment.
Everything can be edited, or others in the team can leave their own comments.
First, a script that calculates what percentage of your AWS resources (15 different resources for now) are managed by the Terraform code in a given directory, and then creates GitHub style badges for each. https://github.com/chrisanthropic/terraform-infra-as-code-co...
Second, a script to fully automate importing an existing GitHub org into Terraform and create a basic Terraform resource block for each resource. Imports teams, users, user memberships, and all repos. https://github.com/chrisanthropic/terraform-import-github-or...
Both scripts are just bash and the AWS API, GitHub API, and Terraform. jq is also required.
Specifically, it has CMYK support, allowed me to layout images and text side-by-side and/or overlapping, along with shaded backgrounds for readability and emphasis.
Most books didn't require something this heavy, but the images were a pain without it.