tsucres
1) There are a lot of similar websites, and usually, when I am looking for inspiration, I just google something like "landing page design template" or something and look into the first results. Do you have a plan to make Landub stand out?
2) If I understood correctly, if no screenshot is provided (for a new submission), then you automatically generate one? If so, it would be nice to directly show the generated screenshot so that the user can decide if it needs to be changed or not.
Also, once a screenshot is selected, there seems to be no way to change it (without reload the submission page). (It's a detail but it would be nice to add this possibility).
3) On the submission form, you ask for "Features or sections included inside the landing page", which IMO is a very interesting search criterion. Though I don't see it on the front-page. Are you planning to add it?
On a different note, do you blog about your 12in12 journey somewhere?
The article points out several issues about this project that I didn't think about before reading it. Basically, there's more issues than just "finding the right math", and on different levels, not only the technical one. I'd recommend reading it.
[1] https://dev.to/bosepchuk/is-it-ethical-to-work-on-the-tesla-...
It's kind of frustrating to spend to much time on details like that. Nobody will ever think "wow, that navbar is smooth!".
Btw, the navbar is implemented in an open source project [2], if you want to get a look at it.
Do you know about an alternative?
> There is a classical algorithm whose output distribution is O(ε)-close in total variation distance to the distribution given by l2-norm sampling from the ith row of a low- rank approximation D of A in query and time complexity [O(poly-func)] where δ is the probability of failure.
So the classical algorithm would give a "sufficiently close" approximation of what the QML would output? The article doesn't mention this at all. Is it fair to compare a quantum algorithm with an equivalent classical approximation algorithm?
From the quanta magazine article:
> Computer scientists had considered [the recommendation problem] to be one of the best examples of a problem that’s exponentially faster to solve on quantum computers — making it an important validation of the power of these futuristic machines. Now Tang has stripped that validation away.
Has he really?
HNBuddy interacts with the HN website through a web scraper that is open source [1]. Though, as discussed in another comment, I can't really give you any proof that the code of this scraper is the actual code built in the app.
Anyway, if you don't trust me, you can still use the app as a simple reader :)
Concerning your last thought, I want to keep all the rights on the source code (at least for now, and as long as I'll have the time and the motivation to maintain it), so I won't release it. However, note that several of the components that I used for this project are open source and PRs are welcome on their GitHub pages.
I took note of everything else you said! Thank you for your constructive feedback!
Note though that:
1. There's a built in "reader" equivalent to pocket/readability. I actually open-sourced this module [1]. It uses MercuryApi (the successor of Readability) [2]
2. it's possible to bookmark articles: this action saves them even for offline reading (you have to open/load the articles at least once though).
Concerning your last idea, I find it difficult to integrate it in the current UI without overwhelming it. Maybe if I add an option (as it was suggested in another comment) to choose between a "detailed" and a "dense" list, then I'll think to this feature.
Anyway, thank you for your detailed feedback!
I focused on the "passive" usage of HN for this first version.
I'll add the downvote feature (along with the post/comment submission feature) in the next major update.
But I'm adding this on my list of potential new features for next versions!
2. That doesn't seem complicated to add! Seeing the feedbacks here really gets me motivated to improve the app, so I'll try to add this in an upcoming version.
Thank you!
2. Not currently. I'm planning on adding this in the next few weeks
Thank you for your feedback! I'm glad you like it!
You're making me thinking I should probably setup a bug reporting system for long term maintenance. Thank you!
2. Thanks a lot
3. Not yet. I'm planning on implementing that in an upcoming version
4. I'm going to look into that!
Thank you very much for your feedback!
I also plan to add support for comment and post submissions. I hope I'll have the time to do so in the next few weeks.