Readit Newsbenstopics commented on Show HN: Weejur – micro-blog from your email account weejur.com... · Posted by u/npilk
Yes, it parses based on the from email. The short answer is that it doesn't protect against email spoofing. I do have some filtering set up, but it hasn't been effective in my testing.
However, you do receive a confirmation email after every new post. So if someone spoofed your email to make a post, you would get a notification email about that post. In the notification, you'd see what had been posted and could easily delete it. (Note that the email address associated with an account isn't made public anywhere, so someone would need to have doxxed you in this scenario.)
Of course, it would be pretty easy for a determined attacker to set up a mailbomb that flooded someone's page with hundreds of spoofed posts. At that point I would have to disable email posting for that account to stop the attack.
I'd be interested if you have any suggestions!
I think a pin number might be an easy solution. Just sign with #1234 at the bottom of the email.
benstopics commented on Show HN: Weejur – micro-blog from your email account weejur.com... · Posted by u/npilk
Does it just post to the correct page based on the from email? If so, how do you protect against email spoofing?
benstopics commented on Show HN: Follow-up “With a 9-5 job and 2 kids I finally finished my first MVP” · Posted by u/mrhichem
To me MVP still means "Microsoft Most Valuable Professional".
I'm guessing that in this case it is "minimum viable product", as in "a service that is just barely useful and good enough that some people will pay money for it".
I also use MRP (Minimum Remarkable Product) as in, your product has at least one feature that is of value to someone.
This is cool. Apparently I’ve saved over $1500 and 370 hours of drive time since WFH of March 2020. I also can speak cat now.
benstopics commented on Yak Shaving: A Short Lesson on Staying Focused (2018) americanexpress.io/yak-sh... · Posted by u/thunderbong
Refactors usually take much longer than the bug fix, and while it acrues technical debt, there may be more urgent things to take care of. The article is about focusing on your initial goal, and then filing the refactor as a next step action item, instead of just growing scope endlessly.
I understand where you’re coming from. I would argue that if the amount of refactoring required to make the bug clear takes that much longer, then all the more reason it should be prioritized. This is really the purest definition of tech debt, because there may be other bugs present in the code you are unaware of. This is assuming no tests cover the bug, because if they did, it wouldn’t have made it into production. Honestly you should be doing it all, because you have to understand the full scope of the issue to properly fix the bug, test it to prevent regression, and in order to test it it must be testable. So I would say if there are no tests, and it is not testable code, the least amount of refactoring you should do is make it testable. You actually don’t even have to write the test if you really want to cut corners. Just through single responsibility principle, dependency injection, and writing code that could be tested is enough to bring it 90% the way there. You can even break the dependencies and theoretically as long as you don’t violate the interface the functions you refactored should hold up. The simpler and more broken down the code is, it gets to the point where you say, this function has one if statement and two return statements, writing a test is actually redundant compared to the code. If it’s not mission critical code, you can really cut corners, if you’re in a hurry…
benstopics commented on Yak Shaving: A Short Lesson on Staying Focused (2018) americanexpress.io/yak-sh... · Posted by u/thunderbong
“ Never fix a bug and refactor in the same pull request.”
I’m sorry, but this is backwards. Bugs are many times caused by badly written code and you can tell when it’s the case. Refactoring the code many times fixes the issue without ever having to figure out where the needle was in the haystack.
I guess in every field there are platitudes and prescriptions. At the end of the day, I try to follow first principles and ignore them and just focus on building a great product.
What I see in this article is a disregard for the costs associated with context switching. My argument is, if you think you can handle the rabbit hole, and you think those related tasks will need to be done anyway at some point, head off to Wonderland. Because you have the context of the situation fresh in your temporary memory, so you’ll get it done faster than if you switch contexts and come back later.
benstopics commented on Show HN: Ducks, the Python Object Indexer github.com/manimino/ducks... · Posted by u/manimino
Thanks for building this. The speed boost is pretty insane, this would actually be great for an API layer for performing multiple operations on large query results in memory to reduce requests to the database. I imagine you could add a simple condition to use ducks if the array size exceeds a certain length.
Also, kudos for snagging the ducks pypi slug. I can’t believe that was available.
benstopics commented on Show HN: Scrib.am, my encyclopedia, inspired by Diderot. One article per day scrib.am/... · Posted by u/astonfred
This is an interesting concept. Reminds me of changingminds.org which I am guilty for reading hundreds of his pages.
An idea I had was a way to login and keep track of what pages you’ve already read or how many times you’ve read them so you could rank your favorite articles and revisit them as a refresher.
fyi when i try to clear the input boxes I can't get rid of the leading zero.