jreicherWell when it comes to Emacs I do almost everything in it. Pretty much the only other application I ever run is a web browser.
dreamrealRight, but how does that affect the documentation?
jreicherEmacs has terrible discoverability. And perhaps necessarily so, given the richness of the environment. It would be like expecting the syntax and standard library of a programming language to be discoverable. So there's a strong self-generating force for documentation with anyone who cares about Emacs.
dreamrealAh, I see what you mean. Yeah, agreed.
dreamrealAny thoughts on #196 up there?
jreicherI haven't been looking at any of the issues but I'll look at that one now.
jreicherUmm. You would put blobs in the DB?
dreamrealQuite possibly.
dreamrealThey'd take up about the same amount of room on a filesystem.
dreamrealI'm still not entirely decided there.
dreamrealI'm not even sure the idea has merit *regardless* of the implementation.
jreicherYeah, I understand. Just that point jumped out at me because I've heard very strong opinions on that over the years.
jreicherAnd I have a strong opinion myself.
dreamrealBut feel free to add your own comments to the issue! I mean, seriously: I've done podcasts before for javachannel.org but that was very much a manual process.
dreamrealWell, feel free to share! I'd be working clean-room (and smooth-brain) so I need all the input I can get.
dreamrealMaybe the "right way" is to literally do a companion podcast and provide a way to add pointers to the manual podcast; I do not know.
dreamrealMy expertise here is going to be in the *recording* process and that's pretty much the end of it.
jreicherAt the moment I'm trying to wrap my head around a multimedia post. The simple version is obvious but I'm not sure I really know what it means "in depth". At least not when it's text-led. A video or audio file with closed captions is more clear.
dreamrealWell, the text posts are the main thing: I'm a writer, not a speaker (one of my biggest challenges here would be in DOING the speaking, because I don't want it generated.) So I'd be publishing text and then recording audio using the text as a base transcript, and amending the text posts with something that says "hey, would you rather hear someone mumble their way through this, instead? HERE YOU GO."
dreamrealThere will never be video if I'm involved.
dreamrealWould definitely be interested in further thoughts on the audio thing, it's very much a lark
jreicherIf you were to do an audio-only post, what do you think it would look like? I'm not suggesting you actually do this, but I'm trying to flesh out what audio "means" in this context.
dreamrealOn the site, it'd be a player at the top of posts with audio (so you could listen there) and there'd be a podcast RSS feed
jreicherNo I mean no text for the post at all. Just audio.
jreicherWhat would the "post" look like?
dreamrealOh, would be HIGHLY unlikely
dreamrealI can't see doing audio-only
dreamrealnot personally
dreamrealI mean, I guess it'd be a content-stub: "Here's an audio only post! Go listen, y'all!"
jreicherIt's just a thought experiment; I'm not suggesting you would do it. But I wanted to know what it would look like if you did.
jreicherOK so even with that the audio is kind of "to the side"
jreicherit's not the entry point of the post, if that makes sense
dreamrealyeah
dreamrealaudio would be, for me, almost always ancillary, mostly because *I* am not a strong speaker, especially extemporaneously, and nevet is not a "content delivery site" - if you want a podcast, nevet has podcast FEATURES but you wouldn't use it for "a podcast"
jreicherI don't like it. :) I think it would make sense to have the "post" directly playable from the front page. And it might make sense to do something like that for a text-and-audio post too. So the front page carries a link to the text post, but there's a play button for the audio next to that link on the front pager also.
dreamrealWell, that'd be easy enough to add, honestly
dreamrealthe front page for the UIs is made up from the content feed from nevet, so the information would be available
jreicherDoing it that way might make the feature quite appealing.
dreamrealYeah, I mean, the backend and the frontends are separate things.
dreamrealbut new features tend to show up on the backend first, so the frontends are just views on the content.
jreicherAnd if you really wanted to go to town you could have AI-generated speech from the text. Not sure what would be a cheap way of doing that though (if one exists at all)
jreicherWell one of the reasons why I've asked the questions I have is that it might have a bearing on the backend. The post now has multiple objects and the text is no longer a primary one; they are all of equal status.
dreamrealPlenty of ways to do that, but that'd be a really crappy way to represent the text forms. Doable, but not good. Most of the posts would be 5-7 minutes to read aloud, and I have a full pro rig here, so the tech aspects would be easy.
dreamrealPro mics, even good "podcast-pro" mics like a Yeti (it's not a pro mic but it suffices for easy stuff, I'd probably use it because the EQ profile is so normal for podcasts)
dreamrealI don't have NPR-level gear here, but a standard NPR broadcast in the US has about $100K of production gear involved, it sounds FANTASTIC but is a little out of what my audience would need or want or know they wanted, I think