iskin

8 ms·

1.
Multiocular: Review changes in node_modules to prevent supply chain attacks(github.com)
6 points by iskin 1y ago|0 comments
2.
The checklist of 11 best HTML practices for forms for pull request review(evilmartians.com)
1 points by iskin 3y ago|0 comments
3.
Color picker for OKLCH–the new better color format for CSS and JavaScript(oklch.com)
6 points by iskin 4y ago|0 comments
4.
CSS Color 4 adds oklch(): get wide-gamut colors including P3 (and beyond)(evilmartians.com)
15 points by iskin 4y ago|1 comments
5.
Test automation for ws servers with human-readable scenarios in YAML/JSON(evilmartians.com)
9 points by iskin 4y ago|0 comments
6.
by iskin 5y ago
I started to mention Colorette when author asked me. First mention (it was changed later) was added 6 days ago (threat was created 2 days ago): https://www.npmjs.com/package/nanocolors/v/0.1.2 Webpack team as
7.
by iskin 5y ago
In my PRs I replace chalk to nanocolors
8.
by iskin 5y ago
I copied one file and I didn't know a way to keep the history of this file. When people later explained how to keep the history of single file I tried to restored it.
9.
by iskin 5y ago
This is Nano Colors author. Even before this Twitter thread we had talk with Colorette author and I added mention to the docs, his name to LICENSE and promised him to not replace Colorette by Nano Colors. The Colorette mention was there 5 d
10.
by iskin 5y ago
Sure. The first note was added 5 days ago https://www.npmjs.com/package/nanocolors/v/0.1.2 Seems like people are confused by git rebase which change commit time in GitHub.
11.
by iskin 5y ago
As I mention here, because Nano Colors it's not just fork of Colorette. It was created as a mix of Colorette and kleur. https://twitter.com/sitnikcode/status/1441827379454746637?s=... Fork button will not wor
12.
by iskin 5y ago
I mentioned Colorette in docs and license even before this Twitter thread. Why is it a stealing?
13.
by iskin 5y ago
When was another time?
14.
by iskin 5y ago
> albeit after being called out Nano Colors mentioned Colorette in docs and Colorette author in LICENSE before Twitter thread. Colorette’s author asked m and I add the mention and agreed on the text.
15.
by iskin 5y ago
I am mentioning it in Babel PRs: > It will have a good support. My other projects from nano-series like very popular Nano ID shows a minimal number of bugs and excellent response time.
16.
by iskin 5y ago
I added Colorette mention before the Twitter thread. Just after Colorette’s author asked me. We even agreed on text form of this mention. He started Twitter thread because of my PRs to Babel. After Twitter thread I just copied git commits (
17.
by iskin 5y ago
Check project’s history. I added Colorette mention in docs and LICENSE just after Colorette’s author asked me (before the Twitter thread). We even agreed on the text. Colorette’s author created this thread because of my PR to Babel.
18.
by iskin 5y ago
Nano Colors is mentioning Colorette in docs, COPYRIGHT and keep git history. If Nano Colors are following all Colorette’s author asks, why he didn’t do it in return?
19.
by iskin 5y ago
It was added in the first day, when Colorette author wrote me. We even agreed on the attribute text.
20.
by iskin 5y ago
I completely agree with it. This is why I used Colorette for a year, promote it and send PRs there. https://twitter.com/sitnikcode/status/1441824191624486924 For for created because Colorette changed API and autho
21.
by iskin 5y ago
I mentioned him in docs, COPYRIGHT and keep the origin history? I clearly explain the reasons of fork creation and the changes https://github.com/ai/nanocolors/wiki/Colorette-Changes What “fork rules” did I v
22.
by iskin 5y ago
Why it is a unattributed fork if Colorette is mentioned in docs, COPYRIGHT and origin commits are in history?
23.
by iskin 5y ago
Any ANSI color library is a very simple thing. Nano Colors mentioned Colorette in docs, COPYRIGHT and keep origin git history. If Nano Colors was open about credits, why Colorette’s author should not do the same?
24.
by iskin 5y ago
You have a new benchmark results after you backported Nano Colors optimizations and refused to mentioned it https://github.com/jorgebucaran/colorette/issues/78 Just look at performance changes history,
25.
by iskin 5y ago
I promote PostCSS alternatives in PostCSS twitter account https://twitter.com/PostCSS/status/777344095748579328
26.
by iskin 5y ago
the mantion of colorette is on top of Nano Colors docs with clear list of why fork was created and the changes https://github.com/ai/nanocolors#nano-colors
27.
by iskin 5y ago
Another side of this story https://twitter.com/sitnikcode/status/1441824191624486924 Also at the end Colorette’s author back-ported Nano Colors performance optimizations, but this time he refuse to mention another
28.
by iskin 6y ago
Completely agree! I believe that op-log sync with CRDT-based atomic operations are a better solution. Logux is one of the example of this approach: https://logux.io/
29.
by iskin 6y ago
This is why there is “With just three PNG images in this minimum set, you can use advanced tools to optimize their size. It solves a problem for Internet users that don’t have unlimited data plans.” note later in the article
30.
by iskin 6y ago
Fair point. I replaced 48 → 32 in the article.

More ›