HNHacker News
TopNewBestAskShowJobs

whatl3y

234 karma · joined December 7, 2016

Developer for a start up in Atlanta.

https://github.com/whatl3y

https://lance.to

[ my public key: https://keybase.io/whatl3y; my proof: https://keybase.io/whatl3y/sigs/LY68u61-jMyMVoAU-iLUMvuI72WBOe879q-XSLTwQUE ]

submissionscomments
whatl3y··on [dead]
Although I respect that this shouldn't be confused as a standard, as a Go beginner with some very small attempts at creating Go projects[1] I would appreciate some sort of guidance on organizing code for a larger project. I've considered rewriting some of my larger NodeJS side projects in Go and I, possibly misguidedly, feel like the biggest barrier to entry is understanding the correct way to organize everything (i.e. directory structure). Is there any documentation, tutorials, anything that you or others would recommend for larger Go projects?

[1]

https://github.com/whatl3y/argv

https://github.com/whatl3y/cdd

https://github.com/whatl3y/odds

whatl3y··on Show HN: A renderless and extendable rich-text editor for Vue.js
At a quick glance tiptap looks great and I don't want to derail the thread mentioning another solution, but after admittedly struggling longer than I'd hoped to implement mentions into a Vue-compatible RTE I got it working fine using modules (NPM) `vue-quill-editor` and `quill-mention`.

Since this is the first public thread I've ready of at least one other person struggling with this (I'm sure there are others), I created this gist of my Vue component in case it helps anyone who want to use Quill instead of tiptap: https://gist.github.com/whatl3y/d1a9fb7bab75c2188b226e902c6f...

whatl3y··on New, portable, open source password manager for Windows
I unfortunately agree with the sentiment of others from this only being supported on windows. I built a CLI password manager[1] sort of as a learning exercise, but to this day I use it daily and have over 250 accounts managed in it. I temporarily back up the encrypted file to S3 in case my computer blows up, but for some reason I have a small sense of satisfaction that my passwords don’t live in a 3rd party like LastPass, even though I’m aware of the auditing and scrutiny they go through consistently to maintain credibility for what they do.

[1] https://github.com/whatl3y/hide

whatl3y··on Show HN: Create Chart Images from a URL
Nice! I built the following a year or two ago and it's currently running on AWS Lambda. It uses Highcharts to generate charts.

https://api.restcharts.com/

https://github.com/whatl3y/restcharts

A competitor that appears to be profitable and doing well is https://charturl.com/.

whatl3y··on Termgraph: Python CLI Tool to Draw Graphs
Although the image would open separately from the terminal window, Termgraph is cool and I might extend RESTcharts (https://github.com/whatl3y/restcharts) to support a CLI mode that would generate an image of a chart based on an input file, then open the image after it's created on the file system.
whatl3y··on Launch HN: Slite (YC W18) – Note App for Teams
I realize this can be a little bit (sometimes more than a little bit) of a development overhead to manage, but isn't the right way to do this is to only require the minimum oauth scopes upon signing up, then add additional scopes and re-auth at the time it's needed (i.e. when someone wants to perform an import)?
whatl3y··on Show HN: Txr – Transfer files/directories to others with WebSocket streams
Thanks for the feedback and recommendations. I agree I could add support for an SSL cert to be used within the express server (today the Heroku dyno is just using Let's Encrypt, which is abstracted from the app itself). I imagine I could add this over a weekend that I have time in the near future.

> Interresting but it really doesn't seem that simple...

Thanks for the feedback, but can you elaborate on how you feel it's not? I'm not sure it could get any simpler to send files than `txr listen username` and `txr send -u username -f filepath`, but I'm willing to listen. Maybe you mean setting up the server isn't simple? Even that is as easy as `txr-server` from the command line though with the package installed...

> I can't really take your word for it that you won't store any files...

I appreciate this sentiment, but that's why the server component is included in the package. If you don't trust the default server on Heroku (which is primarily just for someone to quickly gain an understanding of how to use it, not to actually use permanently moving forward), set up a server on your machine or local network and use it instead :)

whatl3y··on Show HN: Txr – Transfer files/directories to others with WebSocket streams
Thanks for the heads up on the name clash (obviously never heard of the TXR language before this). I named it based on a couple of factors being 1. something that's easy to remember and makes sense (txr ~ transfer) and 2. the NPM module name wasn't taken yet :)

I can change the name, but our projects are pretty much totally different and I'm not trying to make any money off this tool so would prefer to just leave it as is if it won't confuse too many people.

whatl3y··on Show HN: Txr – Transfer files/directories to others with WebSocket streams
Thanks! Yeah nodejs streams and async IO seemed like an ideal use case for this type of tool, plus I wanted to have the easiest approach to passing files between 2 people as possible (we use it at work all the time). Obv a lot has happened in 5 years with nodejs, so I realize it was likely an order of magnitude easier for me to get up-and-running in the last couple months with this tool than it would've been for you 5 years ago haha.
whatl3y··on Show HN: RESTCharts – Generate charts quickly and easily through a REST-like API
Thanks for the feedback! You can use `raw` parameter to configure any type of Highcharts chart you want (review GH for more info: https://github.com/whatl3y/restcharts).

It looks like Highcharts already supports a semicircle donut, so you could take the entire config object, `encodeURI(JSON.parse([config]))` it, and add it to the &raw= parameter to draw a semi-circle donut: https://www.highcharts.com/demo/pie-semi-circle

A working use-case within RESTCharts is as follows (shortened with google so the link doesn't break): http://goo.gl/NbJtqX

whatl3y··on Show HN: RESTCharts – Generate charts quickly and easily through a REST-like API
Great question, and the answer is yes it will (this is one of the most useful features I feel). I encourage you to try and test an image with your email :). The chart endpoint responds with a raw PNG buffer and a Content-type header of image/png, so it would act just the same as if it were a static asset image in a public folder or CDN.
whatl3y··on Show HN: RESTCharts – Generate charts quickly and easily through a REST-like API
Update: You can now see examples with axes shown in the Advanced Section: https://www.restcharts.com/#Advanced%20Configuration
whatl3y··on Show HN: RESTCharts – Generate charts quickly and easily through a REST-like API
EDIT: HN is doing some escaping to my example URL, so I adjusted it a little below.

Author here, thanks for the feedback!

My default use case was to use these images as background-images (via CSS) in dashboard widgets that show an accurate trend for how data has changed over time. Therefore my defaults were to hide to x and y-axis and make the chart margin 0 to fit in the widget and look "nice" across the entire thing.

But if you are or become familiar with the Highcharts chart config options, you can update any option you want for the axis via the `raw` param (see more detailed info on the params in github: https://github.com/whatl3y/restcharts). One thing you could do to one of the simple charts provided on the landing page to show the axes is override the default margin values (which is margin: [0, 0, 0, 0]) and make the x-axis and y-axis visible like so:

where [raw]={"xAxis":{"visible":true},"yAxis":{"visible":true},"chart":{"margin":null}}

your URL would become

https://localhost/chart/line?data=5,1,2,9,8,3,0,0,4&raw=[raw...

You can obviously continue to add config to adjust the language on the axes among other things. I realize this could get a little verbose quick, but again the idea was to make a simple, quick view of data, even though you could technically get as complicated as you want with the `raw` param.

whatl3y··on Explaining React's license
I made the same decision about 1-2 months ago for the same reason, and after scaffolding my project from the CLI, creating some components, and adding additional pieces I needed (vue-router, vuex, dev server proxying to my backend, etc.), Vue has been an absolute pleasure to work with.
← PreviousPage 3 of 3