Title: rdelia's Replies | WordPress.org

---

# rdelia

  [  ](https://wordpress.org/support/users/rdelia/)

 *   [Profile](https://wordpress.org/support/users/rdelia/)
 *   [Topics Started](https://wordpress.org/support/users/rdelia/topics/)
 *   [Replies Created](https://wordpress.org/support/users/rdelia/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/rdelia/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/rdelia/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/rdelia/engagements/)
 *   [Favorites](https://wordpress.org/support/users/rdelia/favorites/)

 Search replies:

## Forum Replies Created

Viewing 5 replies - 1 through 5 (of 5 total)

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Flow-Flow Social Streams] Preferred language for Facebook content](https://wordpress.org/support/topic/preferred-language-for-facebook-content/)
 *  Thread Starter [rdelia](https://wordpress.org/support/users/rdelia/)
 * (@rdelia)
 * [6 years, 4 months ago](https://wordpress.org/support/topic/preferred-language-for-facebook-content/#post-12582452)
 * Sure man! I’ve just sent you a message on your contact form.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Flow-Flow Social Streams] Preferred language for Facebook content](https://wordpress.org/support/topic/preferred-language-for-facebook-content/)
 *  Thread Starter [rdelia](https://wordpress.org/support/users/rdelia/)
 * (@rdelia)
 * [6 years, 4 months ago](https://wordpress.org/support/topic/preferred-language-for-facebook-content/#post-12562279)
 * I modified the plugin code in order to achieve what I needed. I had to pass the
   locale parameter in the HTTP calls to Facebook; also I got to have each localized
   feed managed separately in cache.
 * I’d like to see localization of feeds soon officially implemented by the developer.
 * Btw, thank you for this great plugin!
    Cheers,
 * Raffaele
 *   Forum: [Reviews](https://wordpress.org/support/forum/reviews/)
    In reply to:
   [[Gutenberg] Meaningless](https://wordpress.org/support/topic/meaningless-2/)
 *  Thread Starter [rdelia](https://wordpress.org/support/users/rdelia/)
 * (@rdelia)
 * [6 years, 8 months ago](https://wordpress.org/support/topic/meaningless-2/#post-12242454)
 * Hi Michael,
 * other comments will tell you about lack of functionalities and bad UX and even
   provide comparison with other block editors. Instead, my comment is about an 
   ill-advised release strategy.
 * I appreciate the effort of the development team to give WordPress a native block
   editor, but, regretfully, they didn’t provide users with choice and forced them
   to adopt a still unappealing product. As a result, they totally crashed on launch,
   with users’ massive negative feedback.
 * It’s easy to say that the users are not ready for the innovation, when in fact
   it’s the product not being ready. A brave choice would be now taking a step back
   and make G. available as an opt-in, while they rework it or restart the project
   from scratch.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Gutenberg] Why doesn’t anyone see the real value of Gutenberg?](https://wordpress.org/support/topic/why-doesnt-anyone-see-the-real-value-of-gutenberg/)
 *  [rdelia](https://wordpress.org/support/users/rdelia/)
 * (@rdelia)
 * [6 years, 8 months ago](https://wordpress.org/support/topic/why-doesnt-anyone-see-the-real-value-of-gutenberg/#post-12194323)
 * Skilled developers or even semi-skilled users don’t whine, because they instantly
   install Classic Editor and forget about Gutenberg’s existence.
 * Instead, basic users really care nothing about all the pretty technical awesomeness
   you describe in the second chapter.
 * I can’t see why you state Gutenberg provides the best experience for the reader,
   as an editor should be intended primarily for writers.
 * Of course, trying to force users to adopt an counter-intuitive block editor proved
   a big mistake. As a consequence of that, now disappointed users’ feedback are
   the only reality to get in line with.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Clean Image Filenames] Existing files](https://wordpress.org/support/topic/existing-files/)
 *  [rdelia](https://wordpress.org/support/users/rdelia/)
 * (@rdelia)
 * [9 years, 9 months ago](https://wordpress.org/support/topic/existing-files/#post-8327410)
 * Hi Gesen,
 * thank you for your plugin, it works like a charm!
 * I stumbled upon a problem with Safari browser not supporting URLS containing 
   diacritics.
    See [https://discussions.apple.com/thread/4381117?tstart=0](https://discussions.apple.com/thread/4381117?tstart=0)
 * I had just a dozen image files names containing accented letters like àéì on 
   a WordPress site of mine. It appeared to me that deleting and re-uploading the
   images was fastest way to solve my problem.
 * Your plugin now is preventing future problems with file names on that site, but
   now I wondered: “what if I had 1000s already-uploaded images to rename?”
 * I didn’t found yet any WordPress plugin sanitizing media files names which were
   already uploaded on the server.
 * If you’ll ever consider adding such feature to your plugin, I know it would be
   a huge work to do on your part, but It would be literally of massive help to 
   many users.
 * For the moment, thank you for your plugin and keep up with your great work!

Viewing 5 replies - 1 through 5 (of 5 total)