I think we should differentiate the note-filed filter ARC in two classes:
Regular Payment transactions (ALGO): I agree that Wallet should display only ARC compliant note-fields with no URL. Since users can no opt-out ALGO, Wallets should proactively comply with this ARC to protect users from spam/fishing;
Asset transactions (ASA): if the user has consciously opted-in an ASA than no filter should be applied by Wallets on those transactions note-fields. Note that since 0 ASA transactions are always possible, even towards not opted-in accounts, the opt-in requirement for no filter on note-filed should be enough.
My gut feeling for this idea is that no one obliges me to “subscribe” to a given ASA while I have no mean to opt-out ALGO. Although ASAs users are always a voluntarily subset of ALGO users, I recognise that this second point could be exploited to circumvent the first one in case of widely adopted ASAs (e.g. stablecoins), so my opinion is not so strong on this.
Adding a note on a payment is bread-and-butter stuff, just like Venmo’s model or writing in the memo field of a paper check. I am working on an app where users may opt to provide a note with arbitrary text that would appear on the payment to give the recipient context.
I do not support any blanket rule to hide/block all notes, but it does make sense to solicit feedback for a standard around filtering.
Some unstructured thoughts I had:
A user-configurable wallet setting to hide transactions and/or their notes if the amount is under a threshold
Extensions of the address book concept to filter transactions from known vs. unknown accounts (which might go into some version of a “spam” folder for dust transactions
Protective filtering of or warning about clickable links
More granular settings around notifications, in particular. Maybe the transactions still appear in your history, but push notifications don’t fire for amounts under a threshold.