Last post by Spuds -
In the last 2.0 refresh, several updates were made to Notifications.
1) Standard notifications, such as Liked, Quoted, Mentioned, etc. Now have an option under Profile -> Notification Settings, to show notifications from:
- Everyone
- Everyone except those on your ignore list
- Buddies Only
This just gives members a little more control over what shows up under the Notifications button in the top menu. Note this setting does not stop likes or mentions, etc, but simply does not specifically show a "new" one received should you have On-Site notification enabled for a particular action. So for example if you have on-site notification enabled for likes, you could limit that to just buddies (others can still like, you just don't get a specific new indicator under Notifications)
2) The notification areas that are under the Notifications button in the top menu now respect what you have enabled in your profile. So if you don't have on-site notifications enabled for Quotes, then you will not see a quote button in that area for Unread. If you select "Show All", the button it will show up since there is not way of knowing if you change your options over time etc.
3) You can now enable on-site mentions for New Posts in watched topics and New Topics in watched boards. This setting is under the same area of Profile -> Notifications: For topics and boards I've subscribed to, notify me via: On-site mention, but only for the first reply. Previously the only options was via email (instant, daily or weekly) and the only way to see them on-site was to navigate to your watched topic or board listing in your profile.
Hope I've made some sense in the above explanation
- Several more bugs fixed, such as search by board not working when using a custom index - Coppa not really working - Error sending PM to multi recipients - Full ILA image inline shown as thumbnail in preview - Many other annoyances
In terms of new/updated features, several changes have been made to notifications, I'll outline those in a separate post.
Last post by Spuds -
Here is where I ended up on this.
All links by default get a rel="noopener noreferrer nofollow ugc" If you allowList a domain you get rel="noopener noreferrer ugc" If you have permission and use [url url=somesite.com follow=true]somesite[/url] you get rel="noopener noreferrer ugc" You can also set that to false to override the allowList on a per link basis
I'm thinking of dropping the noreferrer from the allowed to follow links, I don't see the harm with passing the site info to the link you are following.
Last post by Spuds -
I envisioned the allowList as a list of Domains that the site wanted to allow following.
Example, if you had a fan site for Kia cars, you could put Kia.com in the allow list, or perhaps a site you were affiliated with that sold Kia parts, like kiastuff.com that you get a affiliate payment or whatever.
Going the membergroup permission route you would have to a) be in that group and then b) use a url like like [url url=somesite.com follow=true]yowsa[/url] and I just don't feel members would remember or bother to do that. There is also the complication of auto embedded urls which is, again my experience, what most member do (cut/paste). Those could be handled automagically with an allowList but not really with permissions.
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.
to be sure. Looks like we are unaffected by this change.