astro / bitlove-ui Goto Github PK

I’m too lazy to split them in separate issues.

• CSS3 multi-columns for the directory (keyword: columns: 2; and column-break-inside: avoid plus some minor tweaks)
• Compress/gzip content (HTML, CSS, JavaScript, SVG)
  • JavaScripts in one file
  • JQuery from Google for caching (https://developers.google.com/speed/libraries/devguide#jquery)
• CSS Sprites for images (see http://www.spritecow.com/ and http://www.smushit.com/ysmush.it/)

Suggestion for the UI

In order to improve the "what does this service?"-answer and the start page:

• maybe remove first sentence ("Bitlove is…") and center the second one right under the menu
• briefly list advantages for users (left column) and podcasters (right column)
• move podcast list down on the startpage and make it horizontal

Generel:

• color active page in menu
• menu entry for start page ("About" maybe)
• …and "Getting started" page
  • "Users" and "Podcasters" in submenu
  • simple step-by-step guide including promotion for the widget :-)
• cleanup help page
  • no overview help page, but rather single pages for API doc, FAQ, feed doc etc.
  • links in footer
• adjust font sizes of headings and subheadings
• create new images (like "edit.png" and "activate_account.png", which in my eyes are a bit clumsy)
• extend color scheme

And font selection is already on the TODO list. If some things here a selected to be useful I might do one or two.

Hey,

i just tried to fetch all Bitlove feeds to automatically import them into Podfilter :)

Then I noticed that some feeds produce 500 errors:
http://bitlove.org/landfunker/landfunker/feed

cheers!

bitlove.org is currently down.

First draft of a new header:

RFC. Direct link to image.

Feed URLs and the UI URLs should be decoupled, to free the user interface from restrictions and allow future changes.

Currently, both the UI and feeds are served via bitlove.org. Instead, feeds should be moved to the subdomain feeds.bitlove.org.

This can be achieved by issuing by changing the feed URL in the UI and apply a Permanent Redirect when the old URL is accessed by applications. After some time, most if not all clients should have accepted the new URL as most clients do understand the concept. Those who don't should get a bug report and take a class in web protocols.

Example:

A feed currently residing under

http://bitlove.org/metaebene/cre/feed

should be redirected to

http://feeds.bitlove.org/metaebene/cre

I tried to use the feed lookup API similar to by-enclosure.json. Therefore I copied http://bitlove.org/widget/base.js and just changed the API url. However, I get the following error in the JavaScript console:

XMLHttpRequest cannot load http://api.bitlove.org/feed-lookup.json?url=http%3A%2F%2Fmeta.metaebene.me%…ga&url=http%3A%2F%2Fmeta.metaebene.me%2Fmedia%2Fraumzeit%2Frz057-gaia.opus.
No 'Access-Control-Allow-Origin' header is present on the requested resource.
Origin 'http://localhost' is therefore not allowed access. 

Is this intentional or is it just the missing permission?

Requests over http should produce http links, likewise with https. nginx runs as reverse proxy for the latter.

Multiple Feeds should be able to be grouped under a single name. The UI could be extended in such a way that a podcaster can either create a new feed with Bitlove as before or create a feed group instead.

A feed group then gets multiple feeds assigned with one of them being the "default" feed. Each feed gets a separate slug that gets added to the feed groups slug, separated by "/".

Example:

User: metaebene
Group Slug: cre
Feed Slugs: m4a mp3 oga opus
Default Feed: m4a

Resulting Feed URLs:

http://feeds.bitlove.org/metaebene/cre/m4a
http://feeds.bitlove.org/metaebene/cre/mp3
http://feeds.bitlove.org/metaebene/cre/oga
http://feeds.bitlove.org/metaebene/cre/opus

Resulting Feed Group URL:

http://feeds.bitlove.org/metaebene/cre

When accessing the Feed Group URL, the system issues a Temporary Redirect (HTTP 1.1 Status Code 307, HTTP 1.0 Status Code 302) to point to the feed URL that is marked being the default, in this case:

http://feeds.bitlove.org/metaebene/cre/m4a

Feed Groups are presented as such in the User Interface so that users see that what kind of feeds are available and can choose to select the default feed or a specific feed.

I would like to use https URLs but your certificate seems to have been expired.

As the original podcast feed gets replicated, Bitlove currently only replaces the element to point to the generated torrent file instead of the original media file.

In order to create a valid feed (and to hide the original feeds URL), the URL attribute in every <atom:link rel="self" href="url"> element needs to be replaced with the URL of the outgoing torrentified podcast feed.

moved from #18 (comment)

[...] no_content_length error messages (for each episode that has a /podlove/file/tracking URL) [...]

[...] server is not supplying the Content-Length: header. Are you generating download files on the fly? :)

It's a webhosting service, so I'm not sure I can influence what it sends or generates. However, there is definitely a length parameter in each file's <enclosure /> (with Podlove Tracking switched on). Can Bitlove be made to fall back to that one?

Hey astro,

At the moment the torrentByEnclosure widget isn't working at all. I can't figure out which URL I have to put into it to make it work. I think @timpritlove has already told you but the best would be if you would follow redirects, so you can match URLs.

But right now I can't get it to work at all.

Example: NSFW089 Spitzbübisch feixend

In http://bitlove.org/metaebene/not-safe-for-work/feed the following two enclosure URLs are mentioned:

• http://bitlove.org/metaebene/not-safe-for-work/nsfw089-spitzbuebisch-feixend.m4a.torrent (enclosure, but I shouldn't need that)
• http://not-safe-for-work.de/podlove/file/1761/s/feed/c/m4a/nsfw089-spitzbuebisch-feixend.m4a (feedburner:origEnclosureLink)

The native URL is http://meta.metaebene.me/media/nsfw/nsfw083-darmspiegel-online.m4a?ptm_source=download&ptm_context=select-show&ptm_file=nsfw083-darmspiegel-online.m4a.

None of them match when I pass them torrentByEnclosure:

So I am a bit confused. What can I do to make it work on my end?

You've published your Yesod's encryption key here :
https://github.com/astro/bitlove-ui/blob/master/config/client_session_key.aes

This is quite unsecure because anybody can read your sessions' values now.

curl https://bitlove.org/methodischinkorrekt/mp3-cdn/feed > /tmp/min.rss
xmllint /tmp/min.rss

creates errors:

/tmp/min.rss:101: parser error : Char 0xDE09 out of allowed range
<img src="https://s.w.org/images/core/emoji/2.2.1/72x72/1f609.png" alt="😉
^
/tmp/min.rss:101: parser error : PCDATA invalid Char value 56841
<img src="https://s.w.org/images/core/emoji/2.2.1/72x72/1f609.png" alt="😉
^
/tmp/min.rss:447: parser error : Char 0xDE09 out of allowed range
<img src="https://s.w.org/images/core/emoji/2.2.1/72x72/1f609.png" alt="😉
^
/tmp/min.rss:447: parser error : PCDATA invalid Char value 56841
<img src="https://s.w.org/images/core/emoji/2.2.1/72x72/1f609.png" alt="😉

curl "http://api.bitlove.org/by-enclosure.json?url=http://satoripress.com/wp-content/ppp/ppp000.m4a"

Doesn't work (empty JSON reply).

Generate a ping URL for every feed to reset next_fetch time.

Causes the CSS not to load properly.

Hi, I don't know if this is the right place to issue that, but nevertheless:

I lately started a WordPress with Podlove-Plugin and also have an account for my podcast on bitlove.
I also checked the box for my feeds to integrate biltove-feeds and - after finding out the necessity of a trailing '/' - the url for the feed could be verified.
But ... unfortunately the torrent-feeds do not appear in the dropdown list. (See e.g. https://plapperbu.de/podcast/)
Did I miss some necessary step or activation?

Thx for help and advice,

Homer