Title: oEmbed privacy Last modified: May 13, 2018 --- # oEmbed privacy * [benhartwich](https://wordpress.org/support/users/yoursql719/) * (@yoursql719) * [8 years ago](https://wordpress.org/support/topic/wordpress-core-development/) * Hi, * as the GDPR release of WordPress is getting available soon, one topic is really problematic and not addressed so far: two privacy for oEmbeds like medium.com does it (example: [https://medium.com/lapsed-historian/yoko-kanno-the-greatest-composer-youve-never-heard-of-b452f64acc72](https://medium.com/lapsed-historian/yoko-kanno-the-greatest-composer-youve-never-heard-of-b452f64acc72)). * It´s very problematic, that all extra features regarding this topics has to be solved by extra plugins instead of a further development of the WordPress core. I´m counting up to five plugins only for GDPR. I think this problem could be very bad for the WordPress community in a few years in common – there would be many sites with a lot of plugins for very small problems, which all in one slows down the site and produces security issues: one tool for solving problems with comments and discussion, one for avatar privacy, one for checkboxes, one for emoji disabling, one for google fonts disabling… * I would like to help bringing this thought towards the WordPress developer community. I´m loving to work with WordPress, but there are more and more problems in creating a bigger pages with WordPress nowadays and I think, there should be a rethinking in building und developing WordPress regarding to a stable CMS system, which has more options present within the core. There are still many possibilities, but the little problems are not solved and you´ve to install up to 30 plugins– when using an online shop appr. 50. * For example: I have got no control about the sources which are loaded from different locations. Which scripts do really need a CDN to be loaded? Next big example: fonts. WordPress is going towards a new main release with gutenberg for redefining blogging. Why is there still no UI for fonts in WordPress? This is so basic! This should be a core element, when WordPress wants still to be a blogging cms mainly. Organizing these main issues for blogging should be more relevant to the WordPress core instead of having a broader mass of different providers, which all has developed a similar principle. * I think, there is too much, which has to be solved by third parties. I would appreciate it, when WordPress would become more development on the core. Feel free to give me feedback. * Regards, * Ben - This topic was modified 8 years ago by [Steven Stern (sterndata)](https://wordpress.org/support/users/sterndata/). - This topic was modified 8 years ago by [Jan Dembowski](https://wordpress.org/support/users/jdembowski/). Reason: Topic changed to a meaningful title from "WordPress Development" Viewing 4 replies - 1 through 4 (of 4 total) * Moderator [Jan Dembowski](https://wordpress.org/support/users/jdembowski/) * (@jdembowski) * Forum Moderator and Brute Squad * [8 years ago](https://wordpress.org/support/topic/wordpress-core-development/#post-10276072) * There doesn’t seem to be a focus to your topic and I’ve renamed it from “WordPress Core Development” to “oEmbed privacy” as that _seems_ to be what you are talking about. * It’s hard for me to tell though and I’ve read your post here 3 times. 😉 * WordPress has a very active development in core and has for years. You can follow that effort via the make core blog. * See [https://make.wordpress.org/core/](https://make.wordpress.org/core/) for more information. * > I would like to help bringing this thought towards the WordPress developer > community. * If you wish to contribute then please give this a read. * [https://make.wordpress.org/core/handbook/](https://make.wordpress.org/core/handbook/) * A patch is the best way to get involved if you can code. It’s easy to suggest something or to dismiss it as easy but it’s a lot of work and collaboration. A patch is the best way to show your work and demonstrate to others what you mean. * Not everyone can do so. I’ve never offered a patch though many people contribute by fixing typos or the documentation. * > For example: I have got no control about the sources which are loaded from > different locations. Which scripts do really need a CDN to be loaded? Next > big example: fonts. WordPress is going towards a new main release with gutenberg > for redefining blogging. Why is there still no UI for fonts in WordPress? * WordPress is extensible via plugins because it’s not a good idea to add every feature. Those features don’t matter user of many installations. Most just want to install WordPress and go. * For the features that you are mentioning those are plugin territory. Some people complain about the bloat from adding the “Hello Dolly” plugin. I don’t imagine that it would be well received putting in all that code when it can and is simply added via a plugin. * [doubleedesign](https://wordpress.org/support/users/doubleedesign/) * (@doubleedesign) * [8 years ago](https://wordpress.org/support/topic/wordpress-core-development/#post-10280224) * > Why is there still no UI for fonts in WordPress? * Typography is the responsibility of the theme, not of WordPress core. It is a design decision. Giving users too much freedom with things like fonts just creates a messy and slow site (e.g. imagine if they decided it would be fun to use seven fonts in one blog post). * Thread Starter [benhartwich](https://wordpress.org/support/users/yoursql719/) * (@yoursql719) * [8 years ago](https://wordpress.org/support/topic/wordpress-core-development/#post-10281768) * [@jdembowski](https://wordpress.org/support/users/jdembowski/): Thanks for your reply. * The GDPR going live is a good milestone in getting a different view on a software, which has evolved for years. * It´s a great idea, that the WordPress core has to be fast, easy to use and should be online within minutes, BUT the GDPR shows, that software has to be rethought in parts. And one part is, how we interact with frameworks. Do we load all interesting stuff from elsewhere and third parties or should we try to ensure, that the software is fast, easy and save (also for privacy and jurisdiction). And privacy IS beside safety one of the biggest problems of web applications. * I know, that GDPR is mainly bullshit, but there are some thoughts, which should give us a new view on the WordPress Core also. WordPress has developed / inserted a few great tools like oEmbed. It works great so far, but the time has changed and we´ve to discuss, if the wordpress core features needs more further development. Up to me, e.g. oEmbed is only developed for a basicly use and so other features also. If medium.com inserted a two click feature for embeds it seems to be very relevant. Also it would improve page speed of the core. Other features, which also need to be developed further? Using Avatars – till now there is no local avatar functionality – is this really stuff for third party plugins? * I think, WordPress could break a few traditions before it´s losing its power on the market, because users are too frustrated of searching und replacing third party plugins. And this has even recognized google. And yes, it would be great, if I could send you patches, but I´ven´t still the skills for doing so. If there is a great docu / training in getting a WordPress developer / coder let me know. * Regards, * Moderator [Jan Dembowski](https://wordpress.org/support/users/jdembowski/) * (@jdembowski) * Forum Moderator and Brute Squad * [8 years ago](https://wordpress.org/support/topic/wordpress-core-development/#post-10281802) * I just want to comment on this part. * > I know, that GDPR is mainly _[ TOTALLY REDACTED BY ME ]_ * I am not, nor will ever be, a fan of such regulation. That said, that was created as a reaction to real abuses from entities on the Internet and elsewhere. * In many places, your data is your own. I can’t obtain _your_ data and do what I like with it there. * In other regions or countries? The data belongs to the data collector and they can do anything they want with that collected data. That has lead to some real abuses for real people being victimized. * The GDPR effort in WordPress is to permit the WordPress user some tools to handle data as they see fit. In some places such as the EU, that’s no longer optional that handling of data. * But it will continue to go slowly and carefully. I have a privacy policy on my site that the new template in 4.9.6-RC1 offered. In the region that I’m in and where I’m hosted that policy is fine. In the EU? Probably not. Maybe. I’m not a lawyer either. 😉 * > I think, WordPress could break a few traditions before it´s losing its power > on the market * This is a opensource project. When people worry about TAKING! OVER! THE WORLD!( I know that’s not you, I’m just being complete) then they’re looking at WordPress wrong. It’s not about competition in the market. WordPress is about cooperation with the user base. As long as this project keeps it about that then I think the marketplace will be just fine. Viewing 4 replies - 1 through 4 (of 4 total) The topic ‘oEmbed privacy’ is closed to new replies. * In: [Requests and Feedback](https://wordpress.org/support/forum/requests-and-feedback/) * 4 replies * 3 participants * Last reply from: [Jan Dembowski](https://wordpress.org/support/users/jdembowski/) * Last activity: [8 years ago](https://wordpress.org/support/topic/wordpress-core-development/#post-10281802) * Status: not resolved ## Topics ### Topics with no replies ### Non-support topics ### Resolved topics ### Unresolved topics ### All topics