HNHacker News
TopNewBestAskShowJobs

bearfrieze

116 karma · joined March 19, 2015

submissionscomments
bearfrieze··on Comprehensions in Python the Jedi way
Thanks for the excellent explanation and your great work on Python.
bearfrieze··on Comprehensions in Python the Jedi way
Thanks for pointing this out along with some folks over in the comments on GitHub. I've updated the Gist.
bearfrieze··on Comprehensions in Python the Jedi way
I like the replace method. It's a great way of doing the same thing.

I considered using the [::-1] syntax to reverse the list, but decided that there was enough "cute" stuff in the examples already.

bearfrieze··on Comprehensions in Python the Jedi way
1: Seems pretty clear that The Force Awakens is an "...origin story of a female Jedi." [1]

2: At some point while writing this I realised I would spend all evening if I had to round up all the planets, and chose to note that the lists are "non-exhaustive" instead :)

[1]: http://www.wga.org/content/default.aspx?id=6130

bearfrieze··on Comprehensions in Python the Jedi way
Nice bonus info. I didn't know about this (haven't spent much time with Python 2.x).
bearfrieze··on Comprehensions in Python the Jedi way
Author here. Thanks for this brilliant comment. May the force be with you.
bearfrieze··on Ask HN: What are the best practices for web authorization at the moment?
Defining authorisation rules as part of your application sounds fine to me. Aim for making compilation and deployment of your application trivial.

Sounds like you want a linear hierarchy of roles. Attaching a number to each role and making rules based on that number might be all you need. For example:

  Superadmin : 100
  Admin      : 90
  Manager    : 80

  if (a.number > b.number) a can delete b
bearfrieze··on Noma's taste of tomorrow: creating the future of food
Noma is Danish: https://en.wikipedia.org/wiki/Noma_(restaurant)
bearfrieze··on Show HN: Ship – A fast, native issue tracker for software projects
https://confluence.atlassian.com/jira/configuring-workflow-1...
bearfrieze··on Show HN: Litenin – A light and fast feed reader
Thanks for the suggestion. I have added it to the issue on Github: https://github.com/bearfrieze/litenin/issues/10. Will look into it.
bearfrieze··on Show HN: Litenin – A light and fast feed reader
First and foremost, "light" and "shocking" are references to the word which Litenin imitates: Lightning. I see a mysterious moderator has changed the title – I do not mind, but find it pretty curious.

When I started building Litenin I often found myself waiting several seconds for Feedly to load. My colleagues at work had desktop readers that were equally sluggish. In that perspective it seems rather fast.

I find that Feedly has improved significantly recently. I just loaded my feeds in ~1 second which isn't terrible considering it has a wealth of features that Litenin lacks.

bearfrieze··on Show HN: Litenin – A light and fast feed reader
Update: I have implemented teaser texts. I will push it to production in ~24 hours. Right now there are very few teaser texts in the database, but in 24 hours Nimbus (the back-end for Litenin) will have updated all feeds at least once. Thanks once again.
bearfrieze··on Show HN: Litenin – A light and fast feed reader
Thank you for the kind words and the bug report.

I tracked down the feed in the database, and it seems like Nimbus (the back-end for Litenin) read the published date correctly. The item was published ahead of time (it's 21:29 UTC time right now): http://feed.dilbert.com/dilbert/daily_strip

Any suggestions on how to handle this in a more graceful way?

bearfrieze··on Show HN: Litenin – A light and fast feed reader
That sounds very painful indeed. This is unintended – the title of the feed should be displayed to the left of the items title like this: http://i.imgur.com/iqD1f0J.png. Would it be possible for you to attach a screenshot and/or a link to the relevant feed(s)?
bearfrieze··on Show HN: Litenin – A light and fast feed reader
I agree, it is confusing not being able to differentiate between feeds with identical titles. I hadn't thought of this problem myself since I didn't encounter it.

With regards to the amount of information displayed, the initial idea was not to have any content/previews inside the reader, and just offer a list of titles that link to the actual content. Previews is a popular request, and I will definitely consider adding some text-only previews to start out with. I like the idea of the "view all" button.

Thanks for your feedback, much appreciated.