Things have changed since then, so I'm looking for input of how to progress. I've been working on adding a feature to 2.0 which is along the lines of what the addon (linked above) does. The primary change is that "nofollow" is nothing more than a hint for search bots, and I think using "ugc" (User Generated Content), is what we should add, by default, to all links. Currently links have no "nofollow" restrictions at all.
rel="ugc" - We recommend marking user-generated content (UGC) links, such as comments and forum posts, with the ugc value. If you want to recognize and reward trustworthy contributors, you might remove this attribute from links posted by members or users who have consistently made high-quality contributions over time.
rel="nofollow" - Use the nofollow value when other values don't apply, and you'd rather Google not associate your site with, or crawl the linked page from, your site. For links within your own site, use the robots.txt disallow rule.
You can also combine values like rel="nofollow ugc"
The question is what are we trying (or thinking) to accomplish? You can read the various articles and its "experts" trying to guess what Google / etc. is actually doing, while pretending that they know !
The 2.0 update I'm working on
Adds "ugc" to all link tags.
A permission to allowing setting a links to "follow", essentially remove the "usg" TBH I feel this is a bit clumsy as you have to know to how to use the bbc url code to set this value, as such I really don't see it being used?
A simple allowList, so if the link is to a preferred site it removes the "usg", this feels clean.
I'm interested in your thoughts on the permissions thing. To use it you need to use a new variant of [url] and then the software needs to make sure you are allowed to use that. In my experience special codes are not used, maybe you have a different experience. Using an allowList seems easy for the admin to set sites you want to be affiliated with, so that makes sense to me.
Thoughts, comments, other directions, leave it alone
Quote from: Spuds – TBH I'm always wary of using google services as they have a track history of breaking changes and/or depreciation's and/or conversion to paid. Just seems to generate extra work when I least need it LOL
I was not aware of any Universal usage, so to be sure I did a secondto be sure. Looks like we are unaffected by this change.
TBH I'm always wary of using google services as they have a track history of breaking changes and/or depreciation's and/or conversion to paid. Just seems to generate extra work when I least need it LOL
Last post by Burke Knight -
Saw this, and wanted to share it, in case ElkArte uses Universal.
QuoteHello Google Analytics user,
On July 1, 2024, Google Analytics 4 properties will have fully replaced Universal Analytics properties, as previously announced. From that date, Google will begin turning off all Universal Analytics services and Universal Analytics APIs, which means Universal Analytics properties will be inaccessible through the Google Analytics front-end and APIs. If you haven’t completely migrated to Google Analytics 4 properties, follow the migration guide to start making the switch today.
Exporting your data To maintain access to data from your Universal Analytics property, you should download or export your data now. If this isn’t done through one of the methods provided in the Google Analytics Help Center, your data will be permanently deleted by Google and won’t be recoverable. If you intend to use the BigQuery integration to export historical data from your Universal Analytics 360 property, we strongly recommend initiating this immediately.
Product integrations Universal Analytics data and settings accessed or used through advertiser, publisher or other product integrations will be unavailable when services have stopped. For example:
Universal Analytics goals and ecommerce transactions will stop measuring new conversions, including within linked advertising accounts. This may affect ad campaign performance if those conversions are used in combination with Smart Bidding.
Universal Analytics audience lists will be closed, which may affect ad campaign media activation and performance.
API requests related to Universal Analytics properties will fail, including requests for deletion of Universal Analytics data through the User Deletion API. This also means that tools relying on an API, such as Looker Studio, will not show any Universal Analytics data.
BigQuery export and backfill of historical data from Universal Analytics 360 properties can only be requested up to and including June 30, 2024. Already exported data remains available in BigQuery. Attribution Projects that were part of Attribution (beta) in Google Analytics will be deleted.
Quote from: Spuds – First it now shows the preview above the hover point IF there is room, otherwise below. This is opposite of what it was. Since most users work down the list, having the popup above does not block your access to the next list item to hover over. Previously if you want to go to the next item you had to hover away to clear the hover in order to gain access to the next item.
Never noticed that, I just checked and works as you describe it.
Last post by Spuds -
I enabled post preview here, so when you are in a topic listing and hover (about 1 second) over the topic subject, you get a short preview.
We have had this since 1.0, so the changes are really behavioral/cosmetic. Also this was one of the former Jquery functions redone in vanilla JS
First it now shows the preview above the hover point IF there is room, otherwise below. This is opposite of what it was. Since most users work down the list, having the popup above does not block your access to the next list item to hover over. Previously if you want to go to the next item you had to hover away to clear the hover in order to gain access to the next item.
Second, it used (well still does) cut the post after xx number of characters, but it also now has a max height on the hover preview with the same fade away that we use on long quotes. The previous behavior was to always show xxx characters, which when you had an inline image or two it could become a very large popup.
Third It now has a defined min-width so it provides a consistent view/layout. Previously it was more like a tool-tip, where the width could be very short and kind of look odd.
to be sure. Looks like we are unaffected by this change.