Hacker Newsnew | past | comments | ask | show | jobs | submit | Idered's commentslogin


1. You can always disable window controls. I'll try to add other types soon 2. You can send issue/pr with language you need. Here's current list https://github.com/Idered/chalk.ist/blob/c9b9d8662ab7fcc0b04... or you let me know here which one you need

Thanks!


2. Nope, I have it on my roadmap but far far away


Thanks! Here's how it compares to CLI npm command:

You can assign shortcut which will focus "Add dependency" input. Once it's focused you can start searching packages and get instant suggestions with data such as description, downloads in last 30 days, package size or info if package is deprecated. It will also auto-instal related @types/* package if available and not deprecated. Whole process can be done much faster than switching to terminal and typing "npm i react && npm i -D @types/react".

At this point extension is already winning(in terms of time to search and install package) over cli command but there are more good stuff: - it will highlight outdated dependencies + you can click "double arrow" button to update to latest version - it will highlight packages with security issues(works for yarn and pnpm). You can check package details to see list of issues and recommended solution. This is powered by GitHub Advisory Database - while searching you can add @ to see a list of versions or add @@ to see a list of tagged versions(e.g latest, beta) - you can remove pacakge/move package to normal deps/dev deps by clicking button - you can click on size info in footer to see a list of installed packages with package size info and download speed

For now it fails at 2 things: - it spawns multiple processes if you install/remove one package after another. Package managers can handle this but it's totally a perf problem on lower spec machines. - you can't install multiple packages via single search e.g you can't type in "react react-dom" and press enter. I plan to add this feature

My biggest pain solved by extension? It's probably that I don't have to switch to browser to search for package I need e.g if I need package to change color from hex to rgb, I can just type in "color" and I'll get decent amount of info to pick a package - preview: https://cloud.kasper.io/vDVclZ

That's all I guess, let me know if you find it useful or have a feature request, thanks!


Thanks for recommendations


Version 78.0.262.0 (Official build) dev (64-bit)


Nope, it's a good link. Once I open it in Edge, it closes. Here is a gif https://i.imgur.com/dWVqADz.gifv


As backend framework we're using Laravel hosted on digital ocean. Images are hosted on Amazon S3, we also queue uploads to S3 with SQS. Imgix is great service and I can't even imagine building tookapic without it. For database we use postgresql. Any other questions :)?


I just saw this thread while browsing the Show HN section. Nice stack, Laravel is a good framework.

My only suggestion would be with the domain you have, make user pages subdomains. It's easy to achieve in Laravel and makes a more pleasing url.

Instead of https://tookapic.com/photos/21408 you could make it https://pawelkadysz.tookapic.com/21408

And even take that a step further and use slugs for urls instead of ID's https://pawelkadysz.tookapic.com/playing-with-light

URL design is a huge thing that many often ignore, but I feel is essential to a website.


Thanks for the suggestion.

Actually we're testing premium features, like custom domains and themes. username.tookapic.com would be reserved for premium users. Right now pawelkadysz.tookapic.com points to 404 (which should be fixed next week). But the custom domain hooked up to the site works just fine, see for yourself: http://daily.pawelkadysz.com - this is the kind of premium theme I'm talking about (it's all powered by tookapic).

As for the slugs and URLs. At first we had it like this: tookapic.com/username/ID-slug but we had some issues with people changing their usernames (that's allowed) and putting weird characters in the photo titles, which all resulted in breaking the links and pointing to 404 in the end.

That's why we changed it to how it works now. No username change nor emoji in photo title will break the link now.


Ah cool cool. For slug issues, Laravel comes with a support strings helper function for turning strings into slugs.

Regarding usernames, well I see the usecases for allowing changes and not allowing. So I guess that's up to you.

All in all, I love the project. I'm not a photographer but the design of the site is beautiful, and well. I'm jealous. haha.


S3 for hosting, imgix for image manipulation


Almost similar stack we use. Good to hear that :)

Confusion you use s3 for images then why do you use imagix too?


You need to give me some feedback before I send you script :)


Good one, Thanks!


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: