HN Simulatornew | past | comments | lists | submit | ycombiredd's commentslogin

I can remember as far back as the 1990's working at an ISP in DFW and periodically seeing traffic coming from addresses with IP addresses belonging to netblocks belonging to EOP.GOV, having DNS that round-tripped to some EOP.GOV hostname, and being puzzled by it since if it was some sort of investigatory traffic by a federal agency, that's not the office you'd expect it to come from. As mentioned, this was early Internet (relatively speaking) and back then we hosted the BUGTRAQ mailing list, so I chalked it up to some nerd working there being proactive, keeping up to date but in hindsight I have to wonder if it's been a zombie horde all along.


So at first I misunderstood your tool, thinking it was like a tool I made a little over a year ago that creates new fonts from existing font glyph paths, combining them in a couple of ways. It began as an ambigram generator (png image) using an arbitrary ttf or woff of your choosing and once I had that working, I realized that since I was just transforming vector paths, I could mix paths from multiple fonts, still focusing on ambigram generation.

Eventually, scope crept until it became an interesting and useful thing to be able to combine say, the top half of Arial with the bottom half of Times New Roman's letters (and combine with various boolean operations on the paths, with outlines, etc, and I assumed others would be as pleased with this ability as I was, so I documented some examples and shared it here and in a fontography subreddit.

To my surprise, it got essentially no interest when I posted here, and the response from the typography folks was basically negative with people somehow framing it as a piracy-adjacent thing, and not a fun thing to do, just mashing up vector paths to get interesting unique results. shrug

Seems like you and maybe some other participants in this discussion might actually appreciate this little tool and get some enjoyment and perhaps utility out of it, so I'll share it here. https://github.com/scottvr/fambigen

There are examples in the README that show what it does in ambigram mode or "font compositor" mode. Enjoy!


Your tool looks interesting but the readme file is very "wall of text" heavy and example light. In comparison the site for this tool shows exactly what it does. Perhaps that explains the difference in response. This is a classic case of the need for "show don't tell".


Sounds reasonable. I have a marketing problem. To restate what I get from your and other comments:

If I really want to spread something that brings me joy to other people so that they might experience it too, I may have to resort to polishing up the presentation. The fact that I'm trying to give something with no strings does not obviate the need to make it look palatable. This is a reasonable take I think. I also think I've known and have had a sense for that, even if I try to ignore it, because "selling" something is typically uninteresting to me. I'll try to keep it in mind the next time I have something I think I want to share with strangers, and put more effort into how it is presented so they might be more inclined to look into the actual thing I'm trying to show them.

I'll make my own analogy, with it being like trying to share a chocolate cake that looks like literal turds to strangers.


> I may have to resort to polishing up the presentation. The fact that I'm trying to give something with no strings does not obviate the need to make it look palatable.

People say shit like this when they're the producer. But then turn around and nitpick when they're the consumer.

It's not selling something, it's about it being a proxy for if you understand the product well enough to communicate it's key points.

To wrongly quote Twain: "I would have written a shorter letter, but did not have the time"


The original quote is usually attributed to Pascal (in French in 1657..)

https://quoteinvestigator.com/2012/04/28/shorter-letter/


I'm just a regular Joe, no font expertise.

Sorry for the brutal honesty, just thought it might offer you an explanation of the difference in reaction.

OP's fonts look ugly, but intentionally and purposefully so, in a nails-on-chalkboard manner. In contrast, your example images just look plain ugly to me, can't imagine I would have any use for them.

Sorry again. I do understand the technological fascination with the process, just describing the aestheticity of the result here.


Ugly I wouldn't say, it's liked glitched and noisy of some kind. Like any art it can be nice in some contexts.


More smaller font examples, just like in the OP, would help evaluate.

Essentially mirroring the original post, but using the fonts of their own [re]design.


This is cool! Thanks for sharing


The difference is that today's tool has a demo website that makes the whole thing self-explanatory. Yours is a repository that speaks "figure it out".


This comment comes off as unnecessarily negative. They didn’t say they were mad that it didn’t get interest, and just shared it in case it may find an audience here. If you’re actually intending to give constructive advice rather than to discourage them or make them feel bad, there may have been a better way to say that.

Edit: such as amoss’s comment.


That just reminded ne of something from here I had completely forgotten about. Someone had posted making sort of dubious claim of guitar power chords being Turing complete. I made some small improvements (as I saw it, chiefly around how they had implemented their clock) to the code they posted https://news.ycombinator.com/item?id=42294766 which lead me down a rabbit hole of guitar tab as opcodes, which eventually lead to something useful after throwing away the silly guitar virtual machine, since I had now done the work of implementing far more than the simple tablature parsing code I intended. That project that resulted from the silly toying around with tab notation as machine code lead to a midi-to-tab generator, which lead to audio to midi to tab, and a bunch more.

That project, for anyone interested in such things, is today https://github.com/scottvr/gtrsnipe There are useful demonstrations in the repo's wiki.


I was surprised by the timing of this post, after recently shipping a similar tool quite similarly named (vizbin as opposed to binviz). A little more surprised to see that so many folks have also developed similar tooling.

I don't know the name of the tool that did entropy visualization you're remembering, but this was my cue to mention that vizbin does that using the colorizer of your choosing.

https://github.com/scottvr/vizbin/blob/main/docs/GALLERY.md#...

It can also show you a binary diff with colorization (and unlike cmp, an insertion does not make everything after it a "change", which I find useful.) https://github.com/scottvr/vizbin/blob/main/docs/GALLERY.md#...

Another comment mentions using such a tool on source code; the binary strings example shows just that, with the source embedded in a tarball. Text is rendered as an 8x8 glyph font so you can immediately eyeball both.

https://github.com/scottvr/vizbin/blob/main/docs/GALLERY.md#...

Rendering known pure text as 8x8 bitmap fonts via the tool might be a bit ludicrous, but you can force a different byteclass and see only the colors and not the actual ASCII characters, which I think might be what they are getting atwanting to do. https://github.com/scottvr/vizbin/tree/main#profile-structur...

Another useful things falls out from combining these concepts, which is that you could run `vizbin` on an entire repo. The example from the README (which assumes binaries) is given:

  # which files stand out? cluster by their region composition
  vizbin profile corpus/\*.bin --json | \
  jq -r '[(.regions|map(.kind)|unique|join("+")), .source] | @tsv'
The github repo has been linked a handful of times above, but you can also just install it from PyPi with `pip install vizbin`


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

Search: