Talk:Royal Crescent, Brighton

Latest comment: 7 years ago by InternetArchiveBot in topic External links modified

Statue really Coade stone?

edit

The rapid weathering described here is inconsistent with descriptions of Coade stone. See my comment there.

— crism (talk) 20:53, 19 February 2010 (UTC)Reply
Sources suggest that the poor design and manufacture contributed to the damage. The designer is described in at least one source as "mediocre". The position (especially in those days, when the crescent was extremely isolated) was also very exposed indeed, facing the prevailing wind which was laden with salt from the sea. Anyway, all sources do indeed confirm that it was Coade stone. Hassocks5489 (tickets please!) 21:01, 19 February 2010 (UTC)Reply
edit

Hello fellow Wikipedians,

I have just modified 3 external links on Royal Crescent, Brighton. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check}} (last update: 5 June 2024).

  • If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
  • If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—InternetArchiveBot (Report bug) 16:25, 20 May 2017 (UTC)Reply