@JriSv250 - here is a quote from the profile of wheelmap_visitor:

This is a proxy user for all wheelchair tag changes happening on Wheelmap by anonymous users of the website and app Wheelmap.org. Please send a message to the wheelmap team for any concerns: https://news.wheelmap.org/en/contact/

Was the deprecation of <site>=* scheme for social media discussed some place? Could you provide a link to it as I haven't been able to locate where a discussion took place?

I see. Well, I will just be walking through the "I may be mistaken" door now. Thank you for taking the time to explain.

I disagree with this change. I believe the error is on Wikidata's side and not OSM's side.

Yes, Q85812269 links to the Wikipedia article yet Q30253741 seems to hold more relevant information. I believe there are duplicate Wikidata entries and that the two entries need to be combined into Q30253741. I admit, I do not know how Wiki works so I may be mistaken.

The W CoMotion building appears to be building=commercial instead of building=retail. W CoMotion is a UW business and research incubator program.

I've made the correction. Feel free to make corrections if you feel there is an error.

Is the addr:street for these address nodes "17th Avenue East" or "17th Avenue"? It appears that "17th Avenue East" is north of East Denny Way and "17th Avenue" is south.

It looks like an error occurred. This changeset shows two version changes to the same node (V3 & V4). V4 has removed all kerb tags and left a blank node.

I noticed a few barrier=kerb tags were incorrectly added to crossing nodes which are on highway (road) ways. OSM wiki notes that the exclusion of barrier=kerb, in this specific case, is related to routing. Below are the first few that I caught but because of the size of this changeset, I did not check every node. osm.wiki/Key:crossing (under Accessibility)
6336579560, 6336579559, 6336579558, 6336579557, 6336579556, 6336579555, 6336579554, 6336579553, 6759791272, 6759791271

I noticed a few barrier=kerb tags were incorrectly added to crossing nodes which are on highway (road) ways. OSM wiki notes that the exclusion of barrier=kerb, in this specific case, is related to routing. Below are the first few that I caught but because of the size of this changeset, I did not check every node. osm.wiki/Key:crossing (under Accessibility)
6045027044, 6045027043, 6044587907, 6044583364, 6000940429, 5984433410, 6242084021

I think this changeset and other similar ones, would benefited from a preliminary conversation with the greater Puget Sound / Washington State mapping community. If that has occurred, I apologize and could you point me to where this conversation happened?

After reviewing this changeset and other similar ones, I believe a number of these corrections are in error. Judging by this OSM Wiki entry, in Tag:place=suburb, "For example, the Lake City area in Seattle (node 150938688) should be tagged as a 'suburb'", I suspect many of these hamlets are more appropriately tagged as "suburb" as opposed to “neighborhood”. It appears that larger regions, such as North Seattle, might be best tagged as "borough". Smaller areas, such as Little Saigon, might be best tagged as "quarter" or “neighborhood” with the surrounding International District tagged as "suburb". In Changeset #92546447, neighborhood O'Brien (down in Kent) was deleted. Looking at the history of the area and noting the fact that Neely O'Brien Elementary is a school in the area, I think O’Brien suburb/neighborhood is valid even if it is in the process of fading into obscurity.

It was an iD identified issue. The change was given by iD.

It looks like the oneway=yes tag refused to be removed. I just took it off. All should be good now. Thank you for all the editing you've doing. Good luck mapping.

I agree. The odd geometry of the intersection is what piqued my curiosity.

Bing 2020 sat image shows a through lane from Fremont Place North to North 35th Street. Has the city removed that travel lane option?

Careful, you added "oneway=yes" on this dual way street.

At the moment, none of the transit platforms or traffic calming islands(?) are in the OSM database. I think, converting Roosevelt Way NE will not result in any loss of information.

I agree that knowing that the bus stops are platforms, separated from the sidewalk by a cycleway, is important (such as to the blind). Going forward, what is the locally prefered way to include this information seems like a topic for a local OSM group or the OSM mailing list (Talk-us-pugetsound). That's my two-cents but I leave it up to you (or others).

Wislander, you are always welcome to message me about my edits. I'd be happy to explain my reasoning. I can't speak for Natfoot yet with 14,950 edits he might be responsive.
I have removed my section of the separate cycleway. No need for unnecessary OSM bloat, I'm sure you understand.
Since, the cycleway along Roosevelt Way Northeast resembles the one, you have disabled, along Northeast Ravenna Boulevard, should it be corrected to match the cycleway mapping standard of the surrounding area (University / Seattle / Washington)? Not me, just someone.

Success! (Recently, I've also had trouble with JOSM)

Removed duplicate nodes (trees); Adjusted building outline and removed the fixme tag; Added name:en to multilingual named locations; Changed bicycles to bicycle and "except=bus" + "except=bicycles" to "except=bus;bicycle".
(I don't understand why JOSM isn't closing my changesets and ends up combining them when I've explicitly closed and uploaded them at different times.)