Hacker News new | past | comments | ask | show | jobs | submit | dang's comments login

Recent and related:

IMG_0416 - https://news.ycombinator.com/item?id=42102506 - Nov 2024 (324 comments)


Not recent (http only): http://astronaut.io

YouTube videos that have almost zero previous views

- https://news.ycombinator.com/item?id=20432772 - Jul 2019 (239 comments)

- https://news.ycombinator.com/item?id=13413225 - Jan 2017 (140 comments)


This comment breaks the site guidelines and especially the Show HN guidelines (https://news.ycombinator.com/showhn.html). Please don't do that.

This is especially important when kids or students are presenting their work. The last thing they need is to run into a bunch of internet jerks—and it's not who we want this community to be, either.

If you wouldn't mind reviewing https://news.ycombinator.com/newsguidelines.html and taking the rules more to heart, we'd be grateful. You've unfortunately been breaking them in other places too (e.g. https://news.ycombinator.com/item?id=42285885).


Related. Others?

The Last Viridian Note (2008) - https://news.ycombinator.com/item?id=33674735 - Nov 2022 (5 comments)

Bruce Sterling: The Last Viridian Note - https://news.ycombinator.com/item?id=383591 - Dec 2008 (1 comment)


We changed the inflammatory title to something more neutral, in keeping with the site guidelines (https://news.ycombinator.com/newsguidelines.html).

If anyone can think of a better title (i.e. more accurate and neutral, preferably using representative language from the article), we can change it again.


We've moved the comments moved to https://news.ycombinator.com/item?id=42309429, which has that URL.

(404media.co is banned on HN because its articles are behind a signup wall.)


Why are other news sources which also have paywalls not banned? (nytimes, wsj, bloomberg, financial times, etc)

Paywalls are fine on HN as long as there's a reliable linkable bypass.

Related:

Text editing hates you too (2019) - https://news.ycombinator.com/item?id=27236874 - May 2021 (182 comments)

Text Editing Hates You Too - https://news.ycombinator.com/item?id=21384158 - Oct 2019 (282 comments)


Related related:

Text rendering hates you (2019) - https://news.ycombinator.com/item?id=36478892 - June 2023 (119 comments)

Text Rendering Hates You (2019) - https://news.ycombinator.com/item?id=30330144 - Feb 2022 (154 comments)

Text Rendering Hates You - https://news.ycombinator.com/item?id=21105625 - May 2019 (170 comments)


"Eschew flamebait. Avoid generic tangents." - https://news.ycombinator.com/newsguidelines.html

[stub for offtopicness]

Redacted/updated repo with BSD 3-Clause license:

https://github.com/asfarley/vtc_opensource

Sorry for the confusion


Ok, we've changed the URL to that from https://github.com/asfarley/vtc_lfs above. Thanks!

your github repo link is broken, perhaps you forgot to unprivate it.

Whoops, thank you. Fixed now.

404?

I accidentally linked the wrong repo (it was original/unredacted with API keys, etc). The correct repo is: https://github.com/asfarley/vtc_opensource

Assume someone grabbed the API keys. Change them as soon as possible.

Changed now. Thanks!

From the EULA.txt [0]:

""" ...

DESCRIPTION OF OTHER RIGHTS AND LIMITATIONS

You may not reverse engineer, decompile, or disassemble the SOFTWARE PRODUCT, except and only to the extent that such activity is expressly permitted by applicable law notwithstanding this limitation.

...

COPYRIGHT

All title and copyrights in and to the SOFTWARE PRODUCT (including but not limited to any images, photographs, clipart, libraries, and examples incorporated into the SOFTWARE PRODUCT), the accompanying printed materials, and any copies of the SOFTWARE PRODUCT are owned by the Author of this Software. The SOFTWARE PRODUCT is protected by copyright laws and international treaty provisions. Therefore, you must treat the SOFTWARE PRODUCT like any other copyrighted material. The licensed users or licensed company can use all functions, example, templates, clipart, libraries and symbols in the SOFTWARE PRODUCT to create new diagrams and distribute the diagrams.

... """

At the bottom of the README:

""" © Roadometry 2018 """

Maybe I missed something but this seems pretty closed source to me.

"Source available" would be a more appropriate term for this project.

[0] https://github.com/asfarley/vtc_lfs/blob/master/EULA.txt


I botched the open-sourcing, I intended to post this one: https://github.com/asfarley/vtc_opensource

I've updated the license to BSD 3-Clause and deleted the EULA.txt.


In that repo, the default branch 'main' has only a licence file. Perhaps you meant to make the 'master' branch the default?

Yes, done now

Comments moved thither. Thanks!

"Please don't post shallow dismissals, especially of other people's work. A good critical comment teaches us something."

https://news.ycombinator.com/newsguidelines.html


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

Search: