Feedback on the new website Vin

So this is the new website, which I'm sure a lot of you have noticed. We'd like to know what you think about it, so I made one of these poll things that you can have your way with.

Here is the poll. Middle click if you want to open it in a new tab.

Also, feel free to give feedback in the comments. Preferably constructive, but I'm not forcing you to.

###Update
So, I compiled some feedback here with some responses and questions of my own. You can just refer to the numbers in case I want some clarification.
(Hiroto): Responded with my feedback, too (in red)

  1. Progress bar animation
  • A lot of people seem to have issues with this. If it's that much of a problem, I guess we should remove the animation.
  • Done
  1. Request marking on queue
  • This seems to be a bug, indeed.
  • Confirmed, fix pending
  1. DJ images not working
  • DJ images are not working mainly because the new site depended on the old one for the images, and that is no longer around. I don't even know if we still have the images, they might have been lost in the migration. DJs can just upload them again when it's working in the new site.
  • Pending~
  1. Page brightness/news header color similarity
  • I'm assuming that by "textbox" you mean the news posts on the front page? The background was nearly pure white a little while ago, so I can understand if the header and the background became too similar. I'll make a note.
  1. Mobile issues?
  • Some people were complaining about not being able to turn off the "mobile site". There is no mobile site; the site readjusts itself based on the width of your browser window. However, I do agree that the transition occurs way too soon.
  • Also, I wouldn't recommend arguing about anything related to mobile sites with Hiroto.
  • Device widths can be adjusted. You people realise that it's not a mobile site and that the scaling is for modern devices, right? I don't know about you, but 10px text on a 4.5" 1280x720 screen is unreadable.
  1. DJ themes
  • DJ themes will be available when they are made. All the themes have to be redone for the new site, which will take some time.
  • I also agree that the site lacks personality, but apparently this is how websites are made these days. I must have missed the memo.
  • Themes will be user-selectable when this is implemented.
  1. Comment formatting / Markdown syntax
  • Yes, comments use Markdown. Whoever suggested adding a note about this with a syntax link, good. It will happen.
  • Here is a Markdown syntax guide for now. Link
  • Should probably do that.
  1. Expanding Stats in mobile menu
  • This seems to be a bug? I don't know enough about how Bootstrap does the expanding to answer properly.
  • It's because the site is HTML5 (the player doesn't stop if you change page). Noted, will make page changes close this.
  1. Page titles
  • Most page titles seem to be rather experimental for testing. I think it will be fixed in the future.
  • Default is the URL or the first h1 tag found.
  1. Menu item remains toggled
  • This is probably a small bug. Not really a big priority.
  • duplicate of #8
  • Not a duplicate, you mistook this issue for #8. #8 is that expanding Stats on the mobile mode causes the menu to expand, but not into the page, which results in the menu becoming its own little scrollable.
  • Also, someone I showed the site to said that the menu (on mobile) should close or anchor the page down to the newly loaded page. It just stays where it is on the page, currently.
  1. Artist/title center alignment
  • I don't know if this is related to making mobile mode work, but I don't think so. I'll propose that it's changed to left alignment, or maybe left/right for artist/title respectively.
  • It's a clusterfuck anyway.
  1. Artist name clickable to search
  • That's a handy feature, but I wonder how much it would be used.
  • Usecase seems like it wouldn't be used enough
  1. LP/Q box size
  • I think many a lot of the site elements are a bit large too, but that's how Bootstrap works.
  • I think it would be better if the boxes resized themselves based on how much text is in them (number of lines etc) but I don't know if this is possible.
  • Resizing is actually done by default. I prevented it.
  1. Timeago time formatting
  • You can hover over the times in the LP and Q boxes to get the exact time.
  • The nice thing about relative time is that we don't have to account for time zones. Though, the old site handled this perfectly fine, so...
  • If enough people prefer the old style I guess we can change it back. Here's a poll.
  • Relative with a hover is what I want on the front page. Convince me otherwise.
  1. Missing stats
  • The Stats page was not preserved. It might be added some time in the future.
  • I don't think many people really used it that much, other than maybe for the listener graph and the pending song count.
  • (that's what i used it for)
  • I made a fancy stats page at some point and it's probably still in git that i will use.
  1. Missing search results
  • I don't know about this, sounds like a bug. What did you search for?
  • Known bug, fix incoming
  1. Song database statistics on submit page
  • This is a nice idea. Might happen.
  • Probably a good idea
  1. More options button does nothing
  • Works here. What browser/os are you using? Do you have JS enabled?
  1. DJ/staff page
  • This will probably be added in the future, though I can't say for certain.
  • It will be done, but without the blogfaggotry
  1. Volume control issue
  • I agree that the bar should move as you scroll.
  • Actually, now that I'm trying it for myself, it does this. What browser are you in?
  • Known issue with input ranges in a lot of browsers.
  1. Blurry logo on mobile mode
  • I guess that has to do with how the image is scaled. Just have to live with it until we get a higher res image.
    • I feel like just hiding it on mobile.
  1. "It looks like babys first website"
  • No comment.
  • u wan fite m8?

Not logged in

Comments use markdown formatting (guide)

500 characters remaining.

exci #516
2016-04-09 17:05:34 UTC

>>264
test

exci #515
2016-04-09 17:05:25 UTC

>>test

Anonymous (aeb1) #358
2014-10-22 03:07:59 UTC

Why aren't you using 8chan.co for threads? Seems a little more populated.

Amelia #91
2014-06-26 18:44:32 UTC

>>90

You can

Amelia #147
2014-06-26 18:44:32 UTC

>144

Actually, the old site was in dire need of an update and any changes were impossible to make. The new site uses a framework (bootstrap on the frontend which is up-to-date, laravel 4 on the backend) and we can actually open source it because we aren't doing security through obscurity.

Amelia #159
2014-06-26 18:44:32 UTC

>>157

Comments aren't deleted. They just have deleted_at = null set in the database and don't show up here. We can still see them.

Amelia #175
2014-06-26 18:44:32 UTC

>>167

Then you had the same issues on the old site. Same code.

Also playlists are incoming.

Vin #264
2014-05-22 13:07:15 UTC

>>250
If we stored that information it would be possible, but unfortunately when a song is played, Hanyuu doesn't keep track of whether it was a request or not.

>>251
Yeah that one is in the pipeline. It shouldn't change the volume though... Do you have HTML5 Storage on?

Anonymous (76f5) #251
2014-05-20 10:40:37 UTC

Also posting comments stops the r/a/dio playing and resets the volume.

Not a huge deal but maybe something to throw to the back of the to-do list.

Anonymous (a17f) #250
2014-05-20 10:35:24 UTC

How about some way to tell if the currently playing song was requested or not?

Sometimes I just get curious if someone actually asked to listen to what's playing.

Anonymous (90ad) #243
2014-05-18 15:46:36 UTC

wow le dev team xD

Vin #228
2014-05-12 21:43:30 UTC

>>225
They seem to be, yes. I hope to have local time implemented in the near future.

Anonymous (d58d) #225
2014-05-12 18:50:04 UTC

The queue times are all in UTC+0?

Vin #217
2014-05-12 13:04:38 UTC

>>215
It's in the works.

Anonymous (fa4f) #215
2014-05-12 12:31:31 UTC

Is it possible to add CD timers to songs that are on CD?

Anonymous (735b) #200
2014-05-10 18:02:10 UTC

Reducing spacing and padding on virtually all the elements would help a great deal. Also these solid bright colors are a strain on the eyes, what happened to this metallic background image? (some soft noise would to great too)
Oh and the progress bar's extent is not clearly visible, darkening its background could help.

Anonymous (ebb1) #199
2014-05-10 13:55:36 UTC

A search bar for the Last Played tab would be great

Anonymous (aaad) #198
2014-05-10 08:11:14 UTC

Just have the site snaped on xbone.

Vin #196
2014-05-09 22:03:15 UTC

>>193
I'm going to take a wild guess and assume that Hiroto probably doesn't give two shits about IE.

I don't either, honestly. Why are you using IE?

Vin #195
2014-05-09 22:00:39 UTC

>>191
Let me clarify. Every song has a number; let's call this number RC. It starts at 0 and is incremented by 1 every time the song is requested.

If a song has not been requested in the past 11 days, it is lowered by 5 every day until it is either requested or hits 0.

This number is used to determine the minimum time between a song being played or requested and when it can be requested again. The formula to calculate cooldown is in Hanyuu's source in the requests._py module.

Anonymous (4ec1) #193
2014-05-09 16:41:09 UTC

The progress bar doesn't work in IE10, not sure about IE11 I don't have it. Loops after 10 seconds and queue doesn't update.

exci #192
2014-05-09 16:18:39 UTC

>188
..ably have a very short re-request timer again). Curse you, character limit.

Devs probably know the exact times and can correct me if anything was completely wrong.

exci #191
2014-05-09 16:17:15 UTC

>>188 I recall 3. being so that the first time it's requested, it's requestable again in some time (let's say 6 hours), then for each time it's requested after that, the timer for re-requesting is increased, until a certain point (let's say a week), with the timers for re-requesting going down again if it's not requested at all for some time (so if a song that was requested a lot of times in January that has a week long re-request timer isn't requested again until, say, March, then it would prob

Vin #190
2014-05-09 15:31:44 UTC

>>188

  1. It's just not displayed any more. The query for that data was immensely complex and really hard to port over to the new system.

  2. That used to be there, no clue why it was removed.

  3. The whole thing is unreliable because it's grabbing times from the search index instead of the database. This results in tiny delays so you often see green songs that should be red. The cooldown itself is determined by how much a song is requested. I could go into detail if you want.

Anonymous (6a6a) #188
2014-05-09 15:11:59 UTC
  1. What happened to song stats? I liked seeing how often a song got played/favorited.

  2. There should be a countdown for request cooldown times in the future.

  3. What even determines whether a song is requestable at all (green) or not (red). I'm assuming the staff disables songs that would be spammed too much.

Anonymous (ab8e) #187
2014-05-09 14:38:55 UTC

I've noticed while requesting from the website, if you try to request something after recently requesting, say an hour, it'll change that song to red but won't play it (due to the 2~ hour request limit)preventing anyone from requesting it until the unrequestable status fades again. Also like the old site there should be a notification at the top telling you your not able to request again for x time.

Anonymous (3154) #186
2014-05-09 03:11:09 UTC

>>180
when is eventually?

Vin #184
2014-05-08 14:15:57 UTC

>>183
I'm pretty sure that the reason the queue is so long is because so many songs are now requestable, not because Hanyuu's 5 (yes, there are only FIVE of them) requests are in there too.

Anonymous (b8c3) #183
2014-05-08 10:31:48 UTC

guys please make it so hanyuu requests get pushed aside for real requests...

Anonymous (b996) #182
2014-05-07 17:45:53 UTC

Where the fuck is the fave list?
I can't know what my tastes are without the fave list.

Anonymous (cf18) #181
2014-05-07 14:37:41 UTC

>>180
Make some "Export Fav List" functionality, at least as a JSON file. Not sure if the previous fav list had such thing, I never used it.

Vin #180
2014-05-07 13:27:00 UTC

>>173
>>174
It's there, just paginated. Also the pagination is broken. It should be fixed soon.

>>176
>>177
What is with the hivemind today? Fave list is gone, yes. It will be implemented eventually.

Anonymous (754a) #177
2014-05-07 09:16:34 UTC

I liked the new design. Only problem is the missing fave list.

Can we expect it to be back?

Anonymous (3154) #176
2014-05-07 08:17:36 UTC

give me my fucking fave list back, I need to see how many I lost.

Anonymous (cf18) #174
2014-05-06 19:49:46 UTC

>>173
Looks like that's the all queue there is http://r-a-d.io/queue
Admins, is queue now capped?

Anonymous (369d) #173
2014-05-06 18:48:35 UTC

What happened to being able to see the rest of the queue?

Anonymous (97db) #167
2014-05-05 23:24:23 UTC

This may have already been brought up, but I've noticed that having the browser stream up causes firefox to lag. Navigating between tabs becomes a pain and it'll temporarily read as not responding for a few seconds before continuing along. Ending the stream returns the browser function to normal. I have yet to test whether this also affects the direct stream.

Additionally the playlist downloads don't appear to be working correctly.

Vin #166
2014-05-05 21:09:55 UTC

>>165
...Which is pretty much what I said in >>153.

Anonymous (831b) #165
2014-05-05 20:10:22 UTC

I liked the comment box on the right side better. Now it's doing some crazy things and overlapping posts. Also, the comments are way too long. Looked way better when they were condensed.

Vin #162
2014-05-05 13:13:04 UTC

>>160
If you read the next news post there are some updates on how the queue works. It's made to give some more variety now.

Vin #161
2014-05-05 13:12:13 UTC

>>159
Sorry, but I have to interject. That matters... how?

If it was deleted, it was deleted. Don't nitpick over something that's utterly irrelevant, like implementation of deletion.

Anonymous (4174) #160
2014-05-05 09:50:11 UTC

Hiroto, thoughts on adding a no-requests hour?

Anonymous (4174) #158
2014-05-05 03:33:59 UTC

I really love the new site!

One thing that I'd like to see fixed is... if I move the volume bar with my touchscreen, it doesn't adjust the volume until I click on it with my mouse.

Probably not too much trouble right?

Anonymous (5ce7) #157
2014-05-05 01:41:54 UTC

Cool, thanks for deleting my comment. Goes to show all that favoritism and power-tripping all over.

Anonymous (e5f2) #154
2014-05-04 20:54:20 UTC

Oh, and the link in "Help" points to https://stream.r-a-d.io/main.mp3.m3u , which in turn contains the entry http://localhost:8000/main.mp3 , which probably isn't going to work.

re the comment form, I literally could not find it. I can't think of any other website that has the comment form outside the column with the comments.

What about having it in-column and expand when needed? There's no requirement for /anything/ to be in the right-hand column; this very page, 99% of it is whitespace

Vin #153
2014-05-04 20:26:29 UTC

>>152
I don't know why the PLS and M3U links are missing. I can only assume that they were simply not added and will be added in the future.

About the comment box; overall the new site follows the old site's layout, and well, the old site had the comment box on the right. Personally I think that expanding the comments to cover the entire width is a bit distracting, so having the comment box on the right draws more attention to comment texts.

Anonymous (e5f2) #152
2014-05-04 19:47:03 UTC

Are the "Stream .m3u Playlist" and "Stream .pls Playlist" links meant to go somewhere? (Shouldn't you be generating the links in "Help" and the links in "More Options" from the same place, so as to DRY?

(Why is the comment box in a separate column from the comments? Normal people will be looking for it first at the bottom of them, then at the top of them, and only as a last resort "to-the-right-of-the-topmost-comment, disguised as a sqawkbox".)

Anonymous (d79b) #151
2014-05-04 19:24:12 UTC

>>143
I want this so bad ;_;

Vin #150
2014-05-04 18:29:13 UTC

>>148
It is, but not in the way you think...
I should add that to the new post.

Anonymous (cf18) #148
2014-05-04 18:10:59 UTC

Queue is still a bit glitchy

Vin #146
2014-05-04 10:59:30 UTC

>>144
>>145
We utilize all of the latest redundancy and web scaling technologies to ensure a constant stream of weeaboo music in your general direction.

In all seriousness, the old website also used Bootstrap (albeit a very modified one). I think Bootstrap uses LESS for CSS generation, though. It's not up on the repo yet last time I checked.

Anonymous (cf18) #145
2014-05-04 00:56:07 UTC

>>144
Not only SASS, but even SaaS.

Anonymous (f579) #143
2014-05-04 00:50:48 UTC

Here's a preview of what a dark theme might look like - might, since I didn't spend more than a few minutes on this, but I thought some people might want to see it anyway.

(Also it (the picture) shows darker for me on firefox than chrome for some reason - the chrome one had the right colours.. so if it seems too dark, try chrome. Or maybe it's just me.)

Anonymous (83b6) #144
2014-05-04 00:23:00 UTC

Apart from some of the DJ themes having broken layout in FF, didn't really feel the old site needed improving. But I'm in the biz, and I understand when you discover something like Bootstrap you suddenly realize that you simply MUST reimplement everything because the new hotness. You guys using SASS? Because you should.

Vin #142
2014-05-03 21:24:44 UTC

>>135
I think what Hiroto is trying to say here is that while you made a good effort, you really could do better.

To be honest, your script doesn't really make the site look any better. You remove way too much padding (and yes, I think the new site has too much of it), and what is up with the font?

In your defense, the LESS files are not in the repo yet, do you couldn't have changed those even if you wanted to.

Anonymous (d3c4) #139
2014-05-03 20:05:19 UTC

Days without requests on Hanyuu.
You know... it's nice to tune in and discover that the same songs aren't playing.
These days with people not able no request have been pretty sweet.

Vin #138
2014-05-03 15:40:35 UTC

>>137
I think the site has a lot of strange timing issues. I've had several case where the updating stops working if a tab is left too long.

Anonymous (0018) #137
2014-05-03 15:34:52 UTC

i.imgur.com/MZZLP07.png

how do I read this shit?

kilim #136
2014-05-03 14:59:23 UTC

how do you embed images

test

???

Anonymous (9c35) #135
2014-05-03 04:51:41 UTC

GM script to

  • Remove rounded corners
  • Fit on a 900px wide screen
  • Moderate padding

(https://bitbucket.org/Abex/r-abex-dio/)

Anonymous (74dd) #133
2014-05-02 22:54:02 UTC

Was there a reason to change the layout? It is much worse right now and I don't see how the current design will become better.

Anonymous (8b4f) #132
2014-05-02 13:08:39 UTC

Stats dropdown on the top bar stays dropped down even after clicking one of the links. If this is intentional, that's fine, but I've found it a little jarring.

Anonymous (d79b) #131
2014-05-02 02:50:31 UTC

>>110
Just hop on IRC and type .thread when the time comes.

Anonymous (cf18) #110
2014-05-01 21:28:04 UTC

So, Friday is coming up, will there be a place for a thread URL on the new website?

Anonymous (6d89) #102
2014-05-01 20:23:52 UTC

>>100
because youre gay

Vin #101
2014-05-01 20:23:02 UTC

>>100
No idea. I think they should too.

Anonymous (cf18) #100
2014-05-01 14:54:43 UTC

Why the news posts don't have datetime?
I only see "Feedback on the new website Vin".

Anonymous (9473) #99
2014-05-01 12:44:51 UTC

>>98

Is this nerd for real?

Also, czech'em.

Anonymous (145b) #98
2014-05-01 11:55:40 UTC

Love the site! keep up the good work.

Anonymous (2c00) #95
2014-05-01 01:19:58 UTC

Just one small annoyance here: when in the narrow view it's not possible to select the currently playing song text. It selects the "Listeners: ..." text instead. (using Chrome)

Anonymous (cf18) #94
2014-04-30 23:28:35 UTC

Anonymous (99af) #93
2014-04-30 22:09:32 UTC

>>86
Yeah, I figured as much.

Insert random songs x/n where x = requests queue, and n is some number that just works well?

Using n=5, a queue of 5 songs would have a random inserted every other song, a queue of 10 would have a random every 2 songs, queue of 20 every 4 songs, and so on.

Change up 'n' to your liking/user feedback, but longer queues would get requests through faster, shorter queues still keep some new music coming through.

Anonymous (dff7) #92
2014-04-30 22:09:10 UTC

looks like shit. When will it stop looking like shit?

Vin #90
2014-04-30 20:11:25 UTC

>>89
This is a nice idea. The issue is, I think, that you can't both implement this and have the split version on the regular page. And of course, the combined one doesn't really work on a regular sized page.

Anonymous (6bff) #89
2014-04-30 18:38:12 UTC

Queue and last played should be merged together (at least on mobile). I'm thinking of something similar to how youtube displays audio transcripts (see image), with the last played above, the currently playing song in the middle (highlighted), and the queue below. All the songs would shift up after the currently playing song ends. The only problem is it wastes horizontal space, hence it being most suitable for mobile.

youtube transcript

Anonymous (dbd7) #88
2014-04-30 17:24:09 UTC
Anonymous (9473) #87
2014-04-30 15:26:05 UTC

Website this, website that.. So when is the android app coming out, faglords.

Vin #86
2014-04-30 14:48:06 UTC

Above post is me, if that wasn't clear.

Forgot to log in.

Anonymous (4222) #85
2014-04-30 14:43:17 UTC

>>78
I've been thinking of ways to redo the queue and request system for ages, but never realized any of them because I can't come up with a good one. Making every other song a random feels like a bit too much.

One system that I had in mind was that there has to be at least X number of randoms in the queue at a time. So, every time Hanyuu plays a song, randoms are added so that there are X of them. That allows for people's requests to come through, but still give variety.

Anonymous (f579) #84
2014-04-30 12:22:37 UTC

One thing I hope will sooth some people is that it's now possible to make DJ themes (and other themes assuming I'll make other versions than dark) that are drastically different from the default layout. So, you can suggest a general idea for that as well and I might make something based on that.

But for now, the dark theme should be ready by the time theme selection is ready.

Anonymous (85d0) #83
2014-04-30 12:09:43 UTC

I like the layout, but the color scheme is a bit too high-contrast for me. I liked the tiled sort of cloud/metal background the old site had because it's nice and soft on the eyes, unlike this really stark white present in the new site.

Anonymous (e123) #82
2014-04-30 11:24:06 UTC

Site design looks kind of bland, like a newly created blog

Anonymous (cf18) #81
2014-04-30 04:59:48 UTC

>>80 Someone should make a userscript for the website.

Anonymous (5ce7) #80
2014-04-30 03:22:45 UTC

Rest in peace, old r/a/dio. At least it looked nice and clean, now it's just rounded out and enlarged and shit. I already miss having my messed-around list of 20 songs that were last played and queued/requested and all the space I had on my screen.

Now everything is just sized up to waste space. Christ almighty, this looks awful.

Anonymous (d0c3) #79
2014-04-29 22:12:46 UTC

>>71
Towards changing the time: could possibly have a toggle under more options or somewhere else, though I'd say go more minimal and just have it click/touch to switch.
Help documentation could inform the user, if that's not considered too bloat. I feel that a srs bsns r/a/dio listener will go hunt that down or ask in IRC, similar as to how I had to hunt for all possible IRC cmds.

I tend to do a lot of search on tracks looking for sources/more info. Would be great to have db info pull on

Anonymous (99af) #78
2014-04-29 22:07:55 UTC

>>57
I've been meaning to suggest this forever, and since you brought it up... would it be possible to have Hanyuu add requests every other song, and play her own selection? Like, if there are 10 requests in the queue, Hanyuu plays a song, then an /r/, back to Hanyuu, then another /r/ and so on. It allows for some different stuff to get through.

Vin #77
2014-04-29 18:56:04 UTC
Anonymous (cf18) #76
2014-04-29 17:47:05 UTC

>>74 didn't know you could select themes on the old website...

By the way, thanks Hiroto for working on the website!

Vin #75
2014-04-29 17:10:37 UTC

>>74
Probably a more intuitive way.

Anonymous (d924) #74
2014-04-29 16:59:36 UTC

When the DJ themes come back will /?mode=# still work, or will there be a more intuitive way to select specific themes?

Vin #73
2014-04-29 16:52:27 UTC

>>72
Things broke.

It's fixed now.

Anonymous (cf18) #72
2014-04-29 15:59:11 UTC

Vin #71
2014-04-29 15:03:51 UTC

>>62
A DJ schedule has been in the pipeline for a very long time and never realized.

>>64
This is a nice idea. Maybe a button in More Options could toggle between relative time and local absolute?

>>70
That's a rather small cosmetic issue.

Anonymous (d335) #70
2014-04-29 12:52:14 UTC

>>69 Got it.

I wish we could edit messages, but I guess that will be too much work to do.

Anonymous (8e33) #69
2014-04-29 12:50:47 UTC
Anonymous (b484) #68
2014-04-29 12:48:58 UTC

>>67 pasted wrong image, here is the right one.

![]http://i.imgur.com/FuKslCb.png)

Anonymous (cf18) #67
2014-04-29 12:47:07 UTC

"radio" selection is a bit off.

Seems like it doesn't go all the way down to the bottom, while other buttons do.

Anonymous (092d) #66
2014-04-29 11:26:36 UTC

Commenting stops the music.

Anonymous (cf18) #65
2014-04-29 05:05:00 UTC

Those images I posted, if they are too small, just open the image URL in a separate tab. Images just get resized to fit into the comment box.

I figured out how to make them clickable though

[![](http://i.imgur.com/uUCfmzs.png)](http://i.imgur.com/uUCfmzs.png)
Anonymous (9cf3) #64
2014-04-29 01:12:15 UTC

Agree with >>55 in that there should be a way to change out the relative for absolute, local times. Idea for smooth implementation between touch and mouse users:

  1. Default is local time. If themes are supported, can support a change of the default to relative times.
  2. On mouse hover, display opposite time format. ex: Display relative time when local time is enabled.
  3. Click/touch time to stop. Could touch the bar alternatively, but other cool features could live here.

I hate md #:3

Anonymous (cf18) #63
2014-04-28 23:30:31 UTC

>>61 Please no.

Anonymous (47d8) #62
2014-04-28 22:28:26 UTC

Some ideas.
Maybe adding an "upcoming stream"on the mainpage when there's going to be a Dj doing his Dj-thingy?
Maybe reducing the request times to specific times of a day and slightly reducing the "cooldown?

Anonymous (f0b0) #61
2014-04-28 22:21:04 UTC

New dong clock when?

Vin #60
2014-04-28 22:09:41 UTC

>>57
I like it too!
>>59
I think it's only like that because that's how it was on the old site.

Personally, I like it, but I think the comments should be sorted in the opposite order, with newest at the top. The top entry is the most relevant, and it's probably the one you are responding to; I'm finding myself having to scroll down all the time to read the posts.

Anonymous (b484) #59
2014-04-28 22:05:51 UTC

>>56 Sorry, I meant on the right, not on the left.

Also, why is Comment Form takes so much space on the right side of this page? Why not place it on the bottom or something.

It also doesn't resize the containing box.

http://i.imgur.com/4s3mN4z.png

Also, when you refresh a page with a comment typed, your text remains in the comment text box but letter count gets reset to 500 until you type anything. Not that much of a bug but still repor

Anonymous (4e08) #58
2014-04-28 22:01:26 UTC

It doesn't allow to send two consequtive messages. Maybe you could bump the letter count limit?

And the Help link in Comment Form doesn't link to GitHub's Markdown description. I think they use a modifed Markdown, like they did add checkboxes recently and such, so some things from the GitHub's Markdown might not work here.

Anonymous (0018) #57
2014-04-28 21:59:47 UTC

Frankly, I quite like the current situation that no one is able to request songs. I like having new songs to listen to rather than the same songs that get requested every 3 days.

Anonymous (cf18) #56
2014-04-28 21:44:24 UTC

In small-width window mode the text on the left of Last Played and Queue drops down a line.

Small Width

http://i.imgur.com/9yTOjit.png

Big Width

http://i.imgur.com/qe8RLcc.png

Anonymous (dbd7) #55
2014-04-28 21:22:38 UTC

About the absolute vs relative times: since the information for both is already there, could there be an option along with the colour scheme to toggle which one is the default? Like, just a button that would swap display and hover values? Personally, I think it's fine as is, but that doesn't seem like a difficult feature to implement if it would please a lot of people.

Vin #54
2014-04-28 21:04:06 UTC

>>53
Could happen, but I think essential functions will be implemented first.

Anonymous (ab8e) #53
2014-04-28 20:52:01 UTC

Could clicking on a song title in search give extensive details including tags/artist/album/database# etc?

Vin #52
2014-04-28 20:49:54 UTC

>>51
I've been seeing a lot of reports about those not working, and yes indeed, they don't lead anywhere. I don't know why. The stream link is also wrong, it should be http://stream.r-a-d.io/main.mp3.

Anonymous (f234) #51
2014-04-28 20:48:23 UTC

>>18
Old .m3u playlist doesn't work and I can't download new playlist from "more options menu". Menu drops but "stream" buttons don't work.

Firefox 28.0 Win7
IE 11 same problem

Vin #50
2014-04-28 20:26:50 UTC

>>48
There will be a theme system in place later, so that could happen. There could be a Light and a Dark theme. Or something.

>>49
Yeah, I recognize this bug.
...I could have sworn Hiroto told me he'd fixed it.

Anonymous (08e3) #49
2014-04-28 19:17:57 UTC

"16.
Missing search results
I don't know about this, sounds like a bug. What did you search for?"
Assuming this is directed at me (#32):
It doesn't matter what I search. Every page after the first page gives no results.
Here is a picture of what I mean:
http://i.imgur.com/vj4ADww.png
Notice how I searched the letter "a."
So far this has happened on a machine running Ubuntu in Firefox and Chrome as well as a different machine running Windows7 in Firefox (have not tried Chrome + W7).
Is

Anonymous (8d22) #48
2014-04-28 19:11:36 UTC

I'd like to see something like this http://a.pomf.se/dhiqkf.webm

Vin #47
2014-04-28 18:27:18 UTC

>>46
Oh, he meant volume changing, not bar being choppy. Got it.

Anonymous (dbd7) #46
2014-04-28 17:15:58 UTC

Regarding #20; I'm not >>42, but am having the same experience in both FF and Chrome on Mac. I think it's just the way the range element works, but the volume doesn't actually change until you release the nub (or tab away, if you're controlling it with the arrow keys).

Anonymous (d79b) #44
2014-04-28 15:05:25 UTC

#Testing
#\Testing
#Testing

Testing

I don't know what I'm doing.

Anonymous (831b) #43
2014-04-28 13:02:20 UTC

There seems to be some problem with DJ images not loading correctly all the time, but I didn't notice this before on the dev site so it might just be a temporary problem.
Also, when viewing the page with certain size browsers the r/a/dio logo gets large, but also blurry. See: http://a.pomf.se/bymqzl.png
Other than that, I really like how the layout changes on my phone so that it's easier to use, since using the old website on a phone was a bit of a pain.
Overall, looks a lot nicer than the ol

Anonymous (092d) #42
2014-04-28 10:37:04 UTC

Scrolling the volume control should change the volume as you scroll rather than only when you let go.

Anonymous (3c7d) #41
2014-04-28 09:48:08 UTC

i like it
you made the more option button simpler
the only problem is, i kinda cant wait to see and try Request and submission feature.
also.... where is our DJs list page :o

overall : i like the new web layout, it's way more simple and smooth.

Suggestion : i want to see r/a/dio DJ list again ;)

Anonymous (c0f3) #40
2014-04-28 04:04:48 UTC

It's Monday and I can't even request Miku. The new site is shit.

Anonymous (430e) #39
2014-04-28 03:11:57 UTC

btw, the "More options" button does nothing

Anonymous (0018) #38
2014-04-28 02:57:24 UTC

Where's the statistics stuff?
Also, this had always been bugging me since the last site, the "# of songs are waiting to be accepted to the database" should go with the Submit page rather than the statistics page.

Anonymous (cf18) #37
2014-04-28 02:52:48 UTC

I'm sorry for the large letters in >>34, it was caused by pound/hash sign preceding "32".
There should be a note somewhere saying that comments use markdown formatting and a link to the formatting options.

kilim #36
2014-04-28 02:33:48 UTC

>>29
maybe you should stop using intel processors

stupid israeli

Anonymous (499b) #35
2014-04-28 01:37:35 UTC

I think it'll look fine once the kinks get sorted out. Though, I liked request being its own button. Not that it's hard to find now, admittedly. I also like that the search form shows the cooldown on request times.

Anonymous (cf18) #34
2014-04-28 00:50:34 UTC

(continuing my previous post) ying too.

#32, those text boxes seem to have such overhead in order to fin multiline text. I reduced the height of boxes from 55px to 40px, see how the second line at the bottom right box doesn't fit? http://i.imgur.com/nTVHbo4.png

The website is kind of too bright indeed.

Anonymous (430e) #33
2014-04-28 00:31:13 UTC

I like the old site more

Anonymous (832c) #32
2014-04-28 00:28:50 UTC

It feels awkward to look at the box size around last/queued songs, but I feel that I will get used to it quickly.
The animated progress bar is unnecessary.
I preferred seeing the time at which queued songs would play rather than the time remaining until they play.
I can't seem to find actual recent statistics under Stats tab.
Almost, too bright
In the event that a search yields N pages, pages 2-N yield no results.
"Feels" better.

See #18, #22
Major improvement (after corrections) over

Anonymous (cf18) #31
2014-04-28 00:12:12 UTC

When Stats in the menu is toggled and you click on, say, News, it's still toggled. The expected behavior would be for it to untoggle when News is pressed.

Also, why author and song names in Search are center-aligned?

In Search you could have made author names clickable, so that it would use author name as search request. Might be somewhat annoying because it would need to be somehow decorated to indicate that they are clickable, and accidentally clicking on them when copying would be anno

Anonymous (f579) #30
2014-04-27 23:55:01 UTC

>>22
They will, as soon as they tell me what they would like on them (I tried reminding them a couple of times but it seems they're being busy masturbating or whatever it is they do on their free time)

Anonymous (15b4) #29
2014-04-27 23:10:15 UTC

>>25
Not him, but when your progress bar takes as many cycles as a 720p youtube video with GPU acceleration turned off, that's a bad sign.

Anonymous (3f29) #28
2014-04-27 22:59:43 UTC

The biggest issue is it uses bootstrap and therefore forces mobile view on my desktop. unless i zoom out 3 times, and everything is a bit too small and gives me a headache because it is so small.
in addition:
It looks like babys first website.
Just like the last one, animations are poor and overused.

Anonymous (e218) #27
2014-04-27 22:43:24 UTC

Mostly what has already been said.
Broken DJ images
Also would really like a darker/more interesting default theme (or even selectable ones, eg: default, dark)

The progress bar does sorta seem a little much, but it's probably just because I'm not used to it yet,.

Anonymous (dbd7) #26
2014-04-27 22:42:04 UTC

Oh, another minor note: page titles for news posts could use some kind of separator between the post title and the author. (Currently reads "Feedback on the new website Vin", could read "Feedback on the new website - Vin".)

kilim #25
2014-04-27 22:16:33 UTC

>>19
what
are you on a compaq or some shit

Anonymous (d79b) #24
2014-04-27 22:05:48 UTC

>>21

I thought mobile view was mostly to make a site look better on a phone's small screen and different layout, not because phones aren't powerful enough to handle the website.

Anonymous (763f) #23
2014-04-27 22:03:52 UTC
  • comments system expands both initial dash and initial asterisk to bullet points, so you can't use an asterisk for a footnote.

  • if you expand "stats" in the /// menu, the menu gets taller but the thing containing it doesn't, so the menu now scrolls independently of the page

  • multi-minute rate limit == no bugs for you.

Anonymous (ba81) #22
2014-04-27 22:03:11 UTC

Will DJs still have their own backgrounds i liked that and it would add some much needed colour to the site

Anonymous (e5f2) #21
2014-04-27 21:58:59 UTC

AFAICT:

  • no way to see more than five previous comments
  • no way to disable mobile view*
  • in mobile view, lines 2 onwards of song titles can't be seen when the title wraps; the element stays the same size
  • in mobile view, something is taking six-to-ten seconds to finish loading

Can't comment on the desktop site; it won't let me see it.

  • please don't mandate a mobile view or serve it to iOS or Android. Smartphones are as powerful as 2003's desktops. Mobile views are annoying.
Anonymous (3442) #20
2014-04-27 21:46:20 UTC

It looks really slick and there are some weird bugs that I'm guessing will be resolved with time.

But design-wise, I think that the textbox header (light grey) and the background (white) is too close to each other. Overall, it's a bit too bright for me.

Anonymous (184c) #19
2014-04-27 21:16:15 UTC

I like the new design but the progress bar eats a lot of cpu. Also DJ images are not working but I guess that's to be expected.

Anonymous (dbd7) #18
2014-04-27 21:15:29 UTC

>>17
It seems like the highlighting is persistent based on position. For example, if I load the page while there are three requests in the queue, the top three positions will stay highlighted even as those tracks rotate out; the highlighting won't change until I reload the page. I'm almost certain that's what's happening, anyway, from the handful of times I noticed. Using FF 28 on Mac, if that matters.

Vin #17
2014-04-27 21:01:20 UTC

>>15
What exactly do you mean by wonky?

Thanks for the input.

Anonymous (dbd7) #15
2014-04-27 20:30:07 UTC

I voted 'like' overall, but have a couple of nitpicks. Firstly, the motion on the progress bar seems a bit much; distracting, almost. Secondly, the shade of blue used to mark requests keeps making me think that part of the page is highlighted. (Also, the request marking itself seems wonky at the moment; code troubles?) Aside from that, it all looks very slick. Nice job.

Not logged in

Comments use markdown formatting (guide)

500 characters remaining.