Direct links
Posted: Tue Feb 12, 2013 7:18 amLong time fan, first time poster.
Sharing is a great feature, but fundamentally centered on sending links to people who are not a member of the Subsonic community.
What I'd like to see is the ability to directly link to folders, albums, or videos within Subsonic for other people who are members of my Subsonic community. I originally added this myself by editing the main Subsonic landing page to take a type character and a base64-encoded anchor tag and redirect the center pane to the appropriate URL. This worked fine for my purposes; I have a Facebook bot that posts a link whenever a new file appears on the server. Unfortunately, the move from base64-encoded paths to inscrutable IDs has made this workaround impossible, so I'm stuck making a feature request. (though if anyone has an idea for how to make a workaround, I'm all ears)
This feature should be pretty simple to add: something as simple as the landing page redirect I outlined about plus an additional sharing option that produces a direct link should be sufficient. If the link were predictable from the file location that would be great, but otherwise an API addition that allowed going from a file location to a direct link would be necessary (even if it required multiple steps).
Sindre, I'd be happy to add the feature myself (or simply re-add the base64 encoding plus the share option) if you wouldn't mind me working in your codebase. I'm a software engineer by trade and no stranger to NDAs or working on java webapps.
Would anyone else find this feature useful?
Sharing is a great feature, but fundamentally centered on sending links to people who are not a member of the Subsonic community.
What I'd like to see is the ability to directly link to folders, albums, or videos within Subsonic for other people who are members of my Subsonic community. I originally added this myself by editing the main Subsonic landing page to take a type character and a base64-encoded anchor tag and redirect the center pane to the appropriate URL. This worked fine for my purposes; I have a Facebook bot that posts a link whenever a new file appears on the server. Unfortunately, the move from base64-encoded paths to inscrutable IDs has made this workaround impossible, so I'm stuck making a feature request. (though if anyone has an idea for how to make a workaround, I'm all ears)
This feature should be pretty simple to add: something as simple as the landing page redirect I outlined about plus an additional sharing option that produces a direct link should be sufficient. If the link were predictable from the file location that would be great, but otherwise an API addition that allowed going from a file location to a direct link would be necessary (even if it required multiple steps).
Sindre, I'd be happy to add the feature myself (or simply re-add the base64 encoding plus the share option) if you wouldn't mind me working in your codebase. I'm a software engineer by trade and no stranger to NDAs or working on java webapps.
Would anyone else find this feature useful?