Give Me a Wall

Give Me a Wall was the debut album from ¡Forward, Russia!, and was released in the UK on 15 May 2006 and in the US on 19 December 2006. Tracks on the album include previous singles "Twelve", "Nine" and "Thirteen". The album was released through the band's own label, "dance to the radio". When asked why the album was self-produced, guitarist Whiskas proclaimed, "We're sick of waiting around for labels to sort themselves out, so we're doing it ourselves." Following the previous releases tradition, all the tracks are named after the order they were written.

Give Me a Wall
Studio album by
¡Forward, Russia!
Released15 May 2006
Recorded2005
GenreIndie rock
Length49:15
LabelDance to the Radio
ProducerPaul Tipler
¡Forward, Russia! chronology
Give Me a Wall
(2006)		 Life Processes
(2008)
Professional ratings
Review scores
SourceRating
Allmusic link
NME link
Pitchfork Media(6.2/10) link
Rocklouder link
The Guardian link
StylusB+ link

Track listing

All tracks written by ¡Forward, Russia!

  1. "Thirteen" – 4:02
  2. "Twelve" – 2:14
  3. "Fifteen Pt I" – 4:14
  4. "Nine" – 3:56
  5. "Nineteen" – 4:54
  6. "Seventeen" – 4:05
  7. "Eighteen" – 3:37
  8. "Sixteen" – 5:48
  9. "Seven" – 3:28
  10. "Fifteen Pt II" – 5:23
  11. "Eleven" – 7:28

There is also a short instrumental track in the negative space of Eleven and if the CD is rewound at the beginning of Thirteen an extended version of the intro plays for 46 seconds, linking the end of Eleven to Thirteen.

gollark: This is weird. I may be capturing wrong, or... Firefox just isn't actually sending any requests to make the websocket?
gollark: I tried looking at it in Firefox's network pane in the debug thing, the websocket connection just doesn't show. I also tried mitmproxy, which also doesn't show anything. Now I'm trying wireshark, but I don't know how to work that, though it seems to show discord opening websockets okay.
gollark: I know websockets don't work with HTTP2 because it doesn't support protocol upgrade, but as far as I know it should just use HTTP 1.1, and Chrome does this.
gollark: <@!690636955108638740> I think it's enabled, why?
gollark: This is EXTREMELY ANNOYING. I have a bunch of websocket-based things which work fine in Chromium and wscat and whatever else, and appear to work if I run them locally too, but if I both have them behind my reverse proxy (caddy) and use them in Firefox it fails and just says `Firefox can’t establish a connection to the server at wss://[the things]`.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.