Hi, Glassman!!
Thank you for clarifying! The tag barrier = kerb was removed from pedestrian crossing nodes, because it affects routing, however mapping crossings is currently not in our policy, and unfortunately, this is out of our scope of projects for now. Please, feel free to remove any other tags if you think that they are incorrect.
Have a nice day!
Best regards,
Darya

Hi, Glassman!
My name is Darya and I am a mapper on the OSM team at Lyft. Thank you for bringing this to my attention.
According to the OSMwiki crossing=*, tags kerb = lowered and tactile_paving = yes are related to the crossings. These tags along with the tag highway = crossing are set for the node where both ways are crossing (footway and street, street and railway and so on). As we can see from the aerial imageries, Bing Streetside and Mapillary, these lowered kerbs and tactile paving exist on all the crossings of this intersection. So that, according to the OSMwiki, tags kerb = lowered and tactile_paving = yes should not be removed.
Please let me know if you have any further questions or evidence that could help me to understand your point in this case. Sorry for any inconvenience this may have caused.
Thank you,
Darya.

Hello Fluffy89502,
Thank you for your timely response. I have gone ahead and updated the changes. See new changeset changeset/86441238
Thank you,
Darya

Hello Fluffy89502,

My name is Darya and I am a mapper on the OSM team at Lyft. While mapping in the Los Angeles area, I noticed that you added oneway=yes tag on East 32nd Street to this way (way/13351103, https://osmcha.org/changesets/82259252/) in March of 2020. According to current Maxar imagery, this road should be bidirectional. Did you have a local resource that provides evidence of such changes? If so I would love to see them. If not, can you please revert the previous changeset to reflect current imagery?

Thank you,
Darya