Hey peeps, there's a difference between expressing the preference that custom operator name configuration is back, and being 'ungrateful' at the work people put in / being not willing to take risks that come with testing.

Fun fact, if people that didn't like the changes like the cbs applet dropping compatibility for custom operator applet didn't voice their dislike of the fact, then no one notices. Kinda like half the people in this thread thought the cbs applet was comparable even though it was nothing alike until those who actually used custom operator applet complained.

Anyway, it's great to see more open packages replacing closed ones, but I presume CBS operator applet and qwerty12's custom name applet could have their code combined fairly easily? (Haven't myself had a chance to look at the source, but I don't imagine it would be difficult unless both are in completely different coding languages.)

I think that's really the most 'right' direction here, honestly, as doing so would benefit the most people with the least amount of inconvenience for the end-users.