bfarber

What would you hope to achieve through this change? Google (currently at least) treats sponsored/ugc the same as specifying nofollow from an SEO standpoint.

I've made a note for us to review this area of code for 4.5.

I've made a note for us to review this area of code for 4.5.

I've made a note for us to review this area of code for 4.5.

The standard wasn't published until after we implemented our own solution, and I'm certain in due course we will switch over to it.

We use a custom lazy loading solution, rather than the new built in lazy loading option Chrome provides. As time goes on and and the behavior is more widely adopted by other user agents, we will explore switching to the native option.

https://web.dev/native-lazy-loading

Admittedly I haven't tested it, I was going directly by the documentation on the very website you linked to. Perhaps this sentence means prior to 76 you had to enable the flags, and if so that's great that it's out "stable" now. Still, if no other browsers support the functionality, and Chrome only began supporting this functionality 13 days ago, it's probably worth giving the feature some time to mature before jumping on it. ;) 

It's only a beta feature (i.e. it's hidden behind a special flag you have to manually enable) in Chrome 76, which was released 13 days ago.
I think we need to give a little time for this to mature first, but definitely when it does I think moving to natively supported browser functionality where possible would make sense.

It's only a beta feature (i.e. it's hidden behind a special flag you have to manually enable) in Chrome 76, which was released 13 days ago.
I think we need to give a little time for this to mature first, but definitely when it does I think moving to natively supported browser functionality where possible would make sense.

Yeah, I mean the reality is Google will just get the info from a different site if you don't supply it. Your strategy isn't going to help your site overall.
I, for one, will say that while I browse the snippets Google shows like anyone else, I almost always also click into the site if the information seems relevant. The short snippet in a search result is rarely enough to answer whatever it is I'm searching for.

Yeah, I mean the reality is Google will just get the info from a different site if you don't supply it. Your strategy isn't going to help your site overall.
I, for one, will say that while I browse the snippets Google shows like anyone else, I almost always also click into the site if the information seems relevant. The short snippet in a search result is rarely enough to answer whatever it is I'm searching for.

Yeah, I mean the reality is Google will just get the info from a different site if you don't supply it. Your strategy isn't going to help your site overall.
I, for one, will say that while I browse the snippets Google shows like anyone else, I almost always also click into the site if the information seems relevant. The short snippet in a search result is rarely enough to answer whatever it is I'm searching for.

Thanks for pointing that out, I've raised this internally for discussion.

Thanks for pointing that out, I've raised this internally for discussion.

Yes, it's impossible to tell you how big it "should" be. There are several factors:
How long you cache guest pages for (you already said 30 seconds). How big your site is - is there a lot to cache? How much guest traffic you get - if you don't allow guests to access your site, that page will stay small by the nature of your traffic patterns. If you don't get much activity in general and aren't using cron, the task that clears the table may not be running enough. You get the idea. Note that you can also store guest cached pages in Redis or in a remote MySQL database, or turn the feature off entirely. That said, it can improve performance quite dramatically for sites with any significant amount of guest traffic, especially during "surges" in traffic.

If you are talking about direct remote video URLs, that functionality will be available in 4.5.
Otherwise, if you link to a specific tweet on Twitter, it will automatically embed (including any video in the tweet).

Yes, it's impossible to tell you how big it "should" be. There are several factors:
How long you cache guest pages for (you already said 30 seconds). How big your site is - is there a lot to cache? How much guest traffic you get - if you don't allow guests to access your site, that page will stay small by the nature of your traffic patterns. If you don't get much activity in general and aren't using cron, the task that clears the table may not be running enough. You get the idea. Note that you can also store guest cached pages in Redis or in a remote MySQL database, or turn the feature off entirely. That said, it can improve performance quite dramatically for sites with any significant amount of guest traffic, especially during "surges" in traffic.

As it happens, this is on an internal discussion tracklist - but there's nothing else to report right now. I can't say if support will be included in any specific upcoming release yet.

Actually, looking back - the Blog version prior to 4.0.0 used TEXT column type. It appears that you changed this to MEDIUMTEXT yourself, and the upgrade routine is naturally not aware of this and expects it to still be TEXT at this point (incidentally, we changed the column size to MEDIUMTEXT in a 4.x release later on).
To that end, you're going to need to customize your upgrade routine - it's not something we can account for, since the issue is based on a customization you previously implemented.

We don't implement every single suggestion ever submitted, particularly when only one client has ever requested it. It's not an objection or unwillingness, but rather an attempt to gauge the request and how relevant or important it is, in the context of everything else we have going on, and also to see if it's something widely needed or desired, or just something one person wants for their own reasons.

Charles and coffee do.not.mix.

Actually, I did some research and RSS has an enclosure tag which can be used to link to media. We'll review this suggestion further for a major release.

It wouldn't be too hard to create a plugin to add support for this leveraging the GMagick extension.
I don't think we would add native support in the software unless there was some level of demand, however.

I raised this internally in our tracker to get some more input, and unfortunately this isn't something that can/will be changed.
Setting the 'required' flag on a form helper most often sets the 'required' HTML attribute as well, so there is browser-level validation going on as well which has no understanding of our toggles system. What you will need to do is what you are already doing - set required to NULL (or set appearRequired) and then perform custom validation on the input as needed.

Setting aside the fact that only 2 people have responded to this topic (one of which was you, the original poster) - improvements and consolidation of code/consistency for custom fields features is something that has been discussed internally, more than once, but there is no current timeframe we can say to expect to see it.
Unfortunately, it's simply not feasible to respond to every single topic to say "we've read this but there's nothing to note or add at this time".