562 karma · joined November 12, 2019
Thanks for your feedback!
Oh, also, the open source repos are coming soon. Only so much time in a day. :)
TricepMail is designed specifically for privacy, and not only privacy for your data on TricepMail’s servers but for preventing others from tracking and selling your information as well. The privacy policy specifically states that there is no collection of your personal information. TricepMail is based out of Colorado, US, but considering moving to another country which might be better for privacy.
The UI is definitely very minimal, but that is on purpose by design. No need for a bunch of visual clutter when reading/sending email. Improvements can and will be made though, of course.
See also https://www.testfront.io/ for an actual description of how it works, but don't bother signing up. I'm really bad at marketing/getting the word out, and google took forever to approve the extension so I lost interest/ran out of money. Maybe if others show interest, I'll be motivated to resume the plans I had for it.
Here's a 4 minute video of it in action, covering every user join/login/update possibility: https://www.youtube.com/watch?v=ifkaptIYeL8
> Now you can download Steam and basically install anything and it will probably work. Microsoft really did some amazing magic in getting both 32-bit and 64-bit x86 programs running on arm64.
The author makes it sound like you can run basically all Windows software on Mac without issues with Parallel, including more demanding software like games you'd find on Steam.
Does anyone here have experience with Parallels? How does performance compare? My assumption with this kind of emulation was always that performance would typically suffer too much for it to be worth it.
I'm really bad at marketing/getting the word out, and google took forever to approve the extension so I lost interest. I made it because I hate manually writing E2E tests like with Cypress.
Maybe if others show interest in it, I'll be motivated to resume the plans I had for it.
I've also gotten into the habit of using uBlock Origin to kill all of the "Accept Cookies" type popups without ever clicking accept. Those are just as intolerable as ads to me.
Last time I used Fastmail, I had to manually setup the aliases in advance, before they could receive mail. It also isn't possible to send from aliases on Fastmail. I find Fastmail's UI/UX to be too cumbersome for what I want to do with my email.
Once I've added a few more key features and polished the UI a bit, I am planning on revamping the landing page to make things clearer.
Thanks again for the feedback. It's incredibly useful.
In TricepMail, messages to e.g. hn@loh.tricepmail.com versus ignore@loh.tricepmail.com are separated in the UI, and you can configure the "ignore" mailbox to block all incoming messages. You can also setup mailboxes that accept messages from specific senders only.
TricepMail also has everything (and a bit more) that you've listed under "Web interface". TricepMail isn't meant to be used for trash/throwaways, but you can use it for that if you want. It's meant to compartmentalize real email for the demands of today, especially for things like the FCC requiring email addresses on applications.
For example, I would consider incoming email from the FCC to be extremely important (definitely not trash), but I wouldn't want to use my usual personal email address for this. I would still want to see it without going through all the hassle of setting up a separate email server and/or using a separate email client. I want everything in one simple, organized place. This is why I created TricepMail.
I've starred your repo. Looking forward to seeing its progress. :)
What will be really interesting is when it is actually a GPT-3 bot but no one has any clue, conversing with it like it were anyone else.
I soft launched something eerily similar ~6 months ago and got zero feedback (probably because no one was able to actually try it since Google took forever to approve the extension).
TestFront.io: https://news.ycombinator.com/item?id=22130590
Ran out of money though and had to pursue other things so I put it on hold. Maybe I'll resume work on TestFront at some point and you'll have some competition. ;)
Apologies for the unsubstantive comment of my own here. I felt like an upvote wasn't enough to show my appreciation.
I actually don't use DO, but I've used their articles many times after searching for how to setup some things on Linux. Their tutorials are excellent and have saved me a ton of time. I'd imagine those articles alone drive a lot of traffic to them.
I'll probably repost if/when Chrome Web Store approves the extension, especially since I've gotten zero feedback (so far).
I created TestFront to solve some pain points for me when creating end-to-end and/or UI tests. Awesome tools like Cypress are still too tedious for me and take way too long.
TestFront is free and open source, MIT licensed. Check the issues on GitHub (notably the high priority ones) for what's next on the agenda. Issues will be prioritized based on user feedback so feel free to give issues a thumbs up or thumbs down and/or create issues of your own: https://github.com/testfront-io/testfront-devtools/issues?q=...
I did a short screen recording yesterday, covering every user join/login/update possibility in under 4 minutes: https://www.youtube.com/watch?v=ifkaptIYeL8
You can probably watch it at 2x speed to get the idea. At the end, you'll see me commit the tests I made to the https://github.com/testfront-io/starter-kit-app repository, which you can clone and run yourself to get an idea for how easy it is. (Note that for the API, I used the `serverless-dynamodb` branch of `starter-kit-api` for easier installation and data resets, but the `express-postgresql` branch should work roughly the same.)
Form is critical too, so with every single lift that you do, make sure you're using the correct form first, otherwise you're potentially wasting your time and putting yourself at risk of injury.
It is crazy to me to think that so many people spend such a large percentage of their lives doing something (usually just for money) and don't consider it to be who they are, especially if they hate the work that they do. Your work is a huge part of who you are. It affects everything about your life. It isn't something you should do just to do it or because you feel like you have to. It's a path that people should choose carefully.
For way too long I latched onto the first opportunity or idea that came along. I'm 32 now and find myself constantly wondering how much different (maybe better, maybe worse) things could have been if I had taken a step back and considered more possibilities for the future. Now multiple times per day I try to consider where each decision might lead, no matter how big or small of a decision, ranging from hours from now to years from now to thousands of years from now. This mindset is less stressful/neurotic than it sounds, and I would suggest more people try this approach. Good, well thought-out decisions lead to a better future (for everyone). Imagine that.
That doesn't mean that you shouldn't take risks. Sometimes a risky path is the best possible path to take. The potential rewards should always be worth the risk, so that is something to always be considered. You usually learn a lot more in a shorter period of time this way.
Family is the most important thing in life. Material things don't matter. Sure, nice things are certainly nice to have and it can make life more enjoyable, but if you have no one you love to use these things with and spend your time with, life feels pretty empty.
Spend your time wisely, and try to do things that, when you look back on your life on your deathbed, you think to yourself, "I am so glad I made that decision."
An exception to this rule is that in terms of front-end (or end-to-end) testing, if an application is deterministic, you most certainly don't need to write any code to create tests for it. You can record actions and snapshots and replay the actions and compare snapshots. There can often be more to it than that (like filtering dynamic elements/attributes and pattern matching), but for the most part, this approach works quite well.
For most people, I'd imagine "degoogling" seems pretty daunting at first, but if you do it gradually, you'll have rid yourself of Google before you know it. You'll also be supporting a better future for everyone. I don't mean that in an anti-Google way. I mean it in a pro-indie-dev (or small company) way and a pro-decentralized way, the way the internet is supposed to be.
Competition is always a good thing, in the context of goods and services, at least.
I think it's much better in the long term if we support businesses that specialize in doing one thing and doing it extremely well.
It may even be reasonable to think of businesses (companies) like you would well-architected software, where businesses that do one thing well are like small modules designed for a specific purpose, simple and predictable, easy to replace with something better if needed, without affecting much else in your life... while Google is like a monstrous spaghetti codebase with too many entangled dependencies, where changing a single thing has the potential to adversely affect many other things in your life.
I see this as a good sign that I'm on the right track.