Recent Replies

  • Replying to: @lucasfreeman

    @lucasfreeman Hmmm. Will have to bring @vincent in on this first. It might be too resource intensive to properly incorporate.

    @vincent - Your thoughts on multiple kudos buttons on a single page?

  • Replying to: @huntsyea

    @huntsyea It also works with Homebridge, I believe. Although for our use-cases, the hardware unit is plenty.

  • Replying to: @JohnPhilpin

    @JohnPhilpin I like to think so!

  • Replying to: @rexbarrett

    @rexbarrett I replied within your Craft doc. You can get back to me here or shoot me an email (hi @ mattlangford .com).

  • Replying to: @JohnPhilpin

    @JohnPhilpin Tiny and Powerful are not mutually exclusive. 🤓 As I've learned more, the code base has actually improved and shrunk over time.

  • Replying to: @pratik

    @pratik Here are my main goals with Tiny.

    1. Support as many first party Micro.blog features as possible in the way they were designed to be used
    2. Layout things from top-to-bottom in a way that is logical
    3. Provide a CSS only design that is easily customizable (Custom CSS)
    4. Allow people to inject their own layout and design philosophies
    5. Be flexible enough to follow Micro.blog as it makes changes/enhancements

    It is not a theme that fundamentally changes Mb. The vast majority of people either use it out-of-the-box or make CSS-only changes. In a perfect world, no one would ever have to change any of the theme's core files to achieve what they want (this is where Microhooks come in to play).

    In theory, any existing plugin you use should work with Tiny. Any conflicts typically can be addressed with CSS only. Tiny theme does not inject any 3rd party scripts by itself. No font-awesome or jquery or google fonts or analytics.

  • Replying to: @pratik

    @pratik That’s coming. Working on supporting a couple more as well. For now, it’s the usuals:

    • Reply on Micro
    • Reply via Email
    • Reply via Mastodon
    • The Tiny branded ones

    Many others don’t require “support” from themes as they just work.

  • Replying to: @pratik

    @pratik

    Profile Photo - For multi-blog users or people who want a logo instead of their account photo. Or who want to do something completely different like use text.

    Description - Enables links and scripts and anything else you can imagine. Or makes it removable.

    Share - Plugins needed. Very little is “included” in the theme other than support/design. It’s meant to be lightweight.

  • Replying to: @huntsyea

    @huntsyea Hm. The screenshot I posted is from My Mac (Safari). Can you send me what you see?

  • Replying to: @huntsyea

    @huntsyea Hmm. Do you have a screenshot (or link) of exactly what you're referencing? It appears the same height for me. screenshot

  • Replying to: huntsyea.xyz

    @huntsyea Oh, that’s nice!

  • Replying to: @rexbarrett

    @rexbarrett Nice! I've been to Oklahoma a few times, primarily Oklahoma City. My role is executive as well.

  • Replying to: www.mangochutney.me

    @mangochutney Is X100F following the same pattern?

  • Replying to: @bloftin2

    @bloftin2 But now I'm gonna have to leave the library! 😢

  • Replying to: @bloftin2

    @bloftin2 Yeah, and there is always the $ issue. Overdrive is more, I'm sure, than alternatives. But they've also integrated with Kindles and Kobos, etc. Usage of e-books will plummet, without a doubt, because of the switch. But they'll save money too.

    My view is self-centered, admittedly. My whole family reads frequently and much of that is because of Overdrive. cloudLibrary won't replace that. The closest alternative for us is Amazon/Rakuten (and for many will be piracy). In all cases, it leaves the library behind.

  • Replying to: @bloftin2

    @bloftin2 Obviously, I’m on the outside looking in. But if it’s equal price to a physical copy, I’d consider that fair from my viewpoint.

    It requires no cleaning, checking, servicing. It can be “picked up” seconds after being returned. It also allows 24/7 access to the book from any location.

    I had not been to a library in years (probably 15+) until I learned about Overdrive. Now I use Overdrive almost every day…and even visit the library here and there.

  • Replying to: @bloftin2

    @bloftin2 Exactly.

  • Replying to: @bloftin2

    @bloftin2 It’s ridiculous. Moving to an e-book service that doesn’t work with e-book readers. 🙄

  • Replying to: @rexbarrett

    @rexbarrett Let me know what kind of changes/customizations you’re looking for and I’ll see what I can find/do for you.

  • Replying to: frankmeeuwsen.com

    @frank Nice!

  • Replying to: @willtmonroe

    @willtmonroe That’s a very popular request. I’m hoping to have a basic write up on how to accomplish that soon.

  • Replying to: @xxxx

    @xxxx Thanks!

  • Replying to: @rexbarrett

    @rexbarrett Awesome!

  • Replying to: @jonah

    @jonah In theory, that would work. I already have the Profile Photo and Text for Bio custom options in Tiny Theme using microhooks. Favicon just presents a unique issue because of how it's provided by micro.blog and not manually coded into each theme.

  • @manton One minor issue with creating multiple blogs under the same account. If a theme uses the recommended partial microblog_head.html, then all blogs using that theme will have the same favicon (taken from account photo). As an example, this site I'm working on is using my first blog's favicon. I know I can fix that with a custom theme by removing microblog_head.html, etc…but I don't think the average person would do that.

    Potential fixes off top-of-my-head: - Favicon removed from that partial - Favicon uploader in dashboard - config.json option? - Different account/profile photo per blog