aboutsummaryrefslogtreecommitdiff
path: root/doc/todo/blogging.mdwn
blob: 1065a609a6587ff2a382bc20100d7c5b00dbbea6 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
- Add Discussion and Edit links at the bottom of each inlined post.
- It would be possible to support rss enclosures for eg, podcasts, pretty easily. 

Here is the last of those items. Using the meta plugin you can give the appropriate 
info, and the enclosure will be added to the entry. It will also add a <link /> tag
at the top, but I don't know if this is necessary. It also includes a fix for
when make is used without PREFIX. 

<http://jameswestby.net/scratch/podcast.diff>

-- JamesWestby

	Hmm. Not quite how I'd envisioned podcasts would work, my idea was
	more that the sound files would be kept inside the wiki, and the
	inline plugin could be told to eg, inline *.mp3, and would add
	those to the rss feed as enclosures. Maybe you'd also inline some
	regular blog pages to describe the files or the like.

	Do you think that would work or that it's worth pursuing that
	approach? I haven't looked at podcasts enough to know if that
	method would be technically feasable; for one thing it would limit
	the blog items for podcasts to just having an enclosure but no
	description.

	Even if that doesn't work and pages are needed to desribe the items
	like you did, it still seems better to keep the podcast items in
	the wiki..

	--[[Joey]]

That's fair enough. I'm a little unsure of how it all works, so I just did the
simplest thing I could. 

You don't need a description for podcasts it seems. So there's nothing stopping
you there. 

I have another patch that I think does what you want. It only supports .mp3 files,
.ogg or similar could be added easily. 

It has the disadvantage that the filename is all there is to go on, as I can't
think of a way to associate any information with the mp3 file. I don't 
want to add a dependency on a IDv3 tag library. You could add another file
.mp3.info with the title/description in. 

It's obviously up to you which way you want to go.

<http://jameswestby.net/scratch/podcast2.diff>

-- JamesWestby

	Hmm, this could be taken a step further, and assume that if
	IkiWiki::pagetype doesn't return a defined page type for the page
	in the blog, then no matter the extension it should be fed into the
	rss feed in an enclosure. This would allow for not only podcasting,
	but vidcasting and a form of photo blogging. Or even an rss feed
	containing the source of ikiwiki. ;-)
	
	--[[Joey]]

Yes I agree that this would be great, but rss2 spec says that enclosure
must have mime-type. How about I use the File::MimeInfo trick from the 
first patch to do this? I don't know why I didn't do this before.
This will probably clean the code up a little as well. 

What do you think of the change that when using raw, if the filetype is not
known it adds an entry anyway? I did this so that the entries appear if
this mode is used. It might be that this is not necessary, as can we assume
that people wont use raw if they want to pod/vid/whatevercast?

-- JamesWestby

	Using File::Mimeinfo makes sense to me.

	I think it probably makes sense to make the (html) blog page
	add an entry with a link to the file that's in the enclosure in the
	rss feed. Whether or not raw is being used.

	Note: I'm still unsure about whether podcasts should support
	descriptions for the enclosures or not. Here's an early podcast
	that did use descriptions:
	<http://static.userland.com/gems/backend/gratefulDead.xml>
	Here's a contemporary podcast, which also uses descriptions:
	<http://www.lugradio.org/episodes.rss>

	The podcast client I use certianly doesn't care about the
	descriptions. But it's podracer, probably not the thing most
	podcast users use. :-)

	--[[Joey]]