• 10 Posts
  • 362 Comments
Joined 4 years ago
cake
Cake day: May 31st, 2020

help-circle
  • Hmm, I don’t know anything about Whoogle, but from other privacy-conscious search engines, I would expect it to work when you use that URL in your bookmark.

    Three things I can imagine:

    • Something in your hosting stack strips the URL parameters, like maybe your reverse proxy, if you use one. You might be able to see in the Whoogle or web server logs, which URLs actually reach it. Might need to set it to debug/trace logging.
    • Maybe there’s a flag in the Whoogle configuration you need to enable to accept these preference URLs.
    • It’s a bug in that Whoogle version.





  • Ephera@lemmy.mltoProgrammer Humor@lemmy.mlDesigners cry quietly
    link
    fedilink
    arrow-up
    45
    arrow-down
    3
    ·
    5 days ago

    I, unfortunately, have to use GitHub at $DAYJOB and this is me. I navigate most of the webpage via the URL bar now.

    Basically, let’s say I’m working on a repo github.com/tomato/sauce/ and want to navigate to the Releases page.

    Via the webpage:

    1. Type github.com into the URL bar.
    2. Don’t find tomato/sauce/ in the list of recent repos, even though it’s the only repo I work on.
    3. Click on some other repo that’s at least in the tomato/ org.
    4. Navigate up to the tomato/ org.
    5. Find the sauce/ repo in the list.
    6. Traverse half the fucking screen to hit the “Releases” heading in the middle of the About-section.

    Via the Firefox URL bar:

    1. Type gi→t→s→r→.
    2. Hit Enter.

    I admit, it’s hard to compete with the latter, but I wouldn’t know how to navigate that way, if the former wasn’t so terrible.








  • Ah, yeah, I don’t think there was anything in the app. I guess, they could’ve mentioned it in the changelog, which gets shown in the app by default after an update.

    But yeah, I think we’ll have to excuse a bit of a bumpy ride here. I know, it says “Mozilla” on there now, but to my knowledge, it’s still just the one core dev…








  • For a project called “Potato Peeler”, I’ll put it into a structure like this:

    ~/Projects/Tools/Potato-Peeler/potato-peeler/
    

    Tools/ is just a rough category. Other categories are, for example, Games/ and Music/, because I also do gamedev and composing occasionally.

    Then the capitalized Potato-Peeler/ folder, that’s for me to drop in all kinds of project-related files, which I don’t want to check into the repo.

    And the lower-case potato-peeler/ folder is the repo then. Seeing other people’s structures, maybe I’ll rename that folder to repo/, and if I have multiple relevant repos for the Project, then make it repo-something.

    I also have a folder like ~/Projects/Tools/zzz/ where I’ll move dormant projects. The “zzz” sorts nicely to the bottom of the list.