So, #Letterboxd informed users that an unnamed actor gained access to an administrator's account. Not great.
In the announcement:
> The information accessed for each of the affected members included their email address, private lists, private watchlist (if enabled), and deleted content.
A free, not-entirely-thought-out @eleventy idea: Template Generators.
• adds an eleventy generate [template] command,
• --templates-path defaults to _templates in src directory,
• interactive prompts for variables defined in template front matter
• optional dynamic flags on the command line that fill in the same (e.g. eleventy generate post --title “My post title!”)
• drops a processed template to the "right" place in src directory
@aardrian Thanks! I appreciate your feedback and expertise. Adjusting my example and updating the docs with guidance is now on my to-do list.
I’m also thinking about dispatching an event when the component’s state changes. Authors using the component could listen for the event and do focus management, etc. based on circumstance and best practices.
That might allow for accessible use with multiple regions in non-consecutive source order? Maybe as an announcement using live regions?
@jgarber At the risk of you taking this the wrong way, sure, dispatch an event, but do not suggest either the navigation (multiple regions or not) nor live regions.
You need to understand how those are exposed to users and how they can mess with users.
So unless you are running tests with daily SR users across a few SR/browser combos, maybe no.
Nothing dictates that receiving a Webmention means you’re bound to display its source content on your website.
You could…
• forward the Webmention to your email,
• build a private notifications dashboard (with or without a moderation queue),
• add a link to the source page to your website without including its content,
• do something wild like set up an auto responder to the original author thanking them for the like/boost/reply,
• etc. etc. etc.
Add #IndieAuth to your website and allow others to sign in. They’d be able to view a dashboard of the content they’d posted that made its way onto your website. Maybe add some lightweight self-service moderation controls?
@jgarber That takes the concept further and further into nerd-only territory.
I like the concept of the IndieWeb but so much of it is fiddly and requires dev experience that it’s hard to imagine someone who just wants to write and share their own content ever succeeding in implementing it well.
“Can you lie down on your back and watch a movie on the ceiling like Tim Cook and have the back of your head be comfortable?
“Sure. I watched 20 minutes of Moana while staring up at the blue sky and clouds above Joshua Tree and it was so tranquil and comfortable that my wife thought I was asleep.”
With the impending #Comixology shutdown (or Kindle integration or whatever) around the corner, I carved out spare minutes over the weekend to download the DRM-free (though possibly watermarked) CBZ and PDF files from #Amazon.
From a purchased library of nearly 1,000 books, between 200 and 300 were available in this manner. 🫠
There is no bulk download, pagination maxes out at 50, and the user interface is incredibly finicky. Every single download requires assenting to a modal dialog. 🫠
The next step is/was to download and umm liberate the entire purchased library. The #Kindle app’s support for comics is worse than #Comixology’s app (which itself was mediocre) and I have no desire to be locked into that ecosystem.
Downloading a library of nearly 1,000 books is even more tedious. In the abandoned Kindle macOS app, it’s one-at-a-time. 🫠
You can go do a “send to device” workflow but pagination is limited to 25 books per page and #Amazon doesn’t guarantee they’ll download. 🫠
@jgarber I did this recently for my regular Kindle books when I moved to using the Kobo reader. I don’t envy your pain. Are there good 3rd party options for reading / storing / whatever’ing comic files?