newfeatureok

16 ms·

121.
by newfeatureok 7y ago
That is also a good idea. It really depends on what the rest of the requirements are.
122.
by newfeatureok 7y ago
I really don't understand your comment. 1. Supervisors are already by definition "superior" than their subordinates. 2. Supervisors on factories already wear distinctive clothing - especially in fully automated factories. Fin
123.
by newfeatureok 7y ago
The requirements were not changed. Supervisors of almost every working class position already wear different clothes to begin with. Heck, even doctors wear different clothing than nurses, teachers than students, coaches from athletes, etc.
124.
by newfeatureok 7y ago
I'm somewhat surprised at the responses for this. I believe your issue can be easily solved - have supervisors wear a distinctive color from a non-supervisor. For example let's say it's yellow. OK so now you have yellow weari
125.
by newfeatureok 7y ago
It's pretty much impossible to avoid the issue you described. When I did an MVP of something similar to this, I encountered the same solution. The only solution really is the following: - Use a reliable email, e.g. mymail@gmail. - Encr
126.
by newfeatureok 7y ago
The only way to prevent the issue you're describing is to use a custom domain.
127.
by newfeatureok 7y ago
From the landing page it does not support that functionality. Perhaps you should update it if you does support what I'm describing.
128.
by newfeatureok 7y ago
No worries! I believe that you will be better served being more like uBlock Origin and less like traditional email alias services. Once you implement the above, you could add a rich "rules" API and then you could do all sorts of i
129.
by newfeatureok 7y ago
One feature I'd love to see is automatic grouping, combined with the functionality you offer already. So for example if you have an email (using a custom domain): email@example.com You obviously will receive emails as you give out your