4 ms·

It’s a bit strange hitting the google redirect notice when linking from the site. You also might want to put your .idea directory and secrets in a .gitignore

netsharc 6y ago
If I were to fork his code I'd fix that the first thing, I'd hate to annoy my users like that. Reminds me of this jwz post (you have to copy and paste manually since he doesn't like HN as a referrer: https://www.jwz.org/blog/2008/02/looking-forward-into-the-past/ https://www.jwz.org/blog/2008/02/looking-forward-into-the-pa... ).
- deleted 6y ago
  [deleted]
- gibolt 6y ago
  This feels like such a weirdly specific block... You have a blog that you want people to read, but not people who come from a specific source
  - Polylactic_acid 6y ago
    This is why browsers are working to remove user-agent and referer. Almost all real world use is tracking and nonsensical blocks.
    - bryanrasmussen 6y ago
      I was familiar with removing user-agent work, but what's this about removing referrer? Can you give a link?
      - Polylactic_acid 6y ago
        Firefox removed the path in 2018 while in private browsing, now their tracking protection is in normal mode too so I imagine it will happen there as well. I'm guessing the only thing stopping them from removing it totally is some sites break if they cant see the domain you came from. https://blog.mozilla.org/security/2018/01/31/preventing-data-leaks-by-stripping-path-information-in-http-referrers/ https://blog.mozilla.org/security/2018/01/31/preventing-data...
  - egypturnash 6y ago
    If one place is a source of much more annoyance than delight, then why not block people coming from there?
- cookiecaper 6y ago
  Right-click -> Open in Private Tab/Window also strips the referrer, FYI.
harikb 6y ago
I wish IDEs (with collaboration from git) made it clear what should and shouldn’t be checked in to source control (or rather they had a way to do both) - where I want to store per-person level settings as well as shareable settings. In this particular case though - IntelliJ itself would have prompted him to add these files - so those are in fact shareable files Note: I do know IntellJ purposely excludes workspace.xml , but these things should be handled much more explicitly and IDE should provide better conventions and guidance.
- Larrikin 6y ago
  The .ignore plugin and the GitHub repo it is built around I think do the job well enough by having a list of suggestions. I may actually have a private repo and have all the settings on both computers that I use.
RupertWiser 6y ago
Hah fortunately those secrets were never actually in use. I just did the unspeakable and quickly rebased master to update that though so thanks for that! I wasn't planning on sharing the code at first so I probably didn't give it as critical an eye as I should have. This was also a learning project for me to try out Kotlin so I'm sure there are a million things others would do far better.
- amenod 6y ago
  It is soooooo easy for something that was just an experiment to get published somewhere, that I have learned (the hard way, multiple times) to never commit any secrets to a git repo. Well, intentionally that is... but if I do it by mistake, I treat them as compromised and change them. Instead I just create a .env file and put them there. It's a bit more boilerplate but it is worth it when I don't need to decide between keeping secrets and having code history before publishing. And env vars are supported everywhere afaik.

netsharc 6y ago

If I were to fork his code I'd fix that the first thing, I'd hate to annoy my users like that. Reminds me of this jwz post (you have to copy and paste manually since he doesn't like HN as a referrer: https://www.jwz.org/blog/2008/02/looking-forward-into-the-past/ https://www.jwz.org/blog/2008/02/looking-forward-into-the-pa... ).

deleted 6y ago
[deleted]
gibolt 6y ago
This feels like such a weirdly specific block... You have a blog that you want people to read, but not people who come from a specific source
- Polylactic_acid 6y ago
  This is why browsers are working to remove user-agent and referer. Almost all real world use is tracking and nonsensical blocks.
  - bryanrasmussen 6y ago
    I was familiar with removing user-agent work, but what's this about removing referrer? Can you give a link?
    - Polylactic_acid 6y ago
      Firefox removed the path in 2018 while in private browsing, now their tracking protection is in normal mode too so I imagine it will happen there as well. I'm guessing the only thing stopping them from removing it totally is some sites break if they cant see the domain you came from. https://blog.mozilla.org/security/2018/01/31/preventing-data-leaks-by-stripping-path-information-in-http-referrers/ https://blog.mozilla.org/security/2018/01/31/preventing-data...
- egypturnash 6y ago
  If one place is a source of much more annoyance than delight, then why not block people coming from there?
cookiecaper 6y ago
Right-click -> Open in Private Tab/Window also strips the referrer, FYI.

harikb 6y ago

I wish IDEs (with collaboration from git) made it clear what should and shouldn’t be checked in to source control (or rather they had a way to do both) - where I want to store per-person level settings as well as shareable settings. In this particular case though - IntelliJ itself would have prompted him to add these files - so those are in fact shareable files Note: I do know IntellJ purposely excludes workspace.xml , but these things should be handled much more explicitly and IDE should provide better conventions and guidance.

Larrikin 6y ago
The .ignore plugin and the GitHub repo it is built around I think do the job well enough by having a list of suggestions. I may actually have a private repo and have all the settings on both computers that I use.

RupertWiser 6y ago

Hah fortunately those secrets were never actually in use. I just did the unspeakable and quickly rebased master to update that though so thanks for that! I wasn't planning on sharing the code at first so I probably didn't give it as critical an eye as I should have. This was also a learning project for me to try out Kotlin so I'm sure there are a million things others would do far better.

amenod 6y ago
It is soooooo easy for something that was just an experiment to get published somewhere, that I have learned (the hard way, multiple times) to never commit any secrets to a git repo. Well, intentionally that is... but if I do it by mistake, I treat them as compromised and change them. Instead I just create a .env file and put them there. It's a bit more boilerplate but it is worth it when I don't need to decide between keeping secrets and having code history before publishing. And env vars are supported everywhere afaik.