#hilbertcurve — Public Fediverse posts

Command-and-control IPv4 map, 2026-03-08 to 2026-03-21 #HilbertCurve
https://abjuri5t.github.io/SarlackLab/

156.234.56[.]0/23
156.234.208[.]0/20
156.234.160[.]0/21
156.234.188[.]0/22
156.234.204[.]0/22
156.234.224[.]0/22
156.234.232[.]0/22
178.16.52[.]0/22
43.243.188[.]0/23

Command-and-control IPv4 map, 2026-02-04 to 2026-02-17 #HilbertCurve
https://abjuri5t.github.io/SarlackLab/

148.178.64[.]0/19
148.178.32[.]0/19
207.56.192[.]0/19
178.16.52[.]0/22
158.94.208[.]0/22
91.92.240[.]0/22
102.117.128[.]0/18
45.114.106[.]0/24
156.234.94[.]0/24

Command-and-control IPv4 map, 2026-01-19 to 2026-02-01 #HilbertCurve
https://abjuri5t.github.io/SarlackLab/

148.178.64[.]0/19
148.178.32[.]0/19
156.234.208[.]0/20
207.56.192[.]0/19
178.16.52[.]0/22
23.226.52[.]0/22
74.119.149[.]0/24
23.226.51[.]0/24
45.114.106[.]0/24

Big Hilbert Curves with Rainbow Confetti colour. :blobhaj_witch: (Terminal Render)

#HilbertCurve #SpaceFillingCurves #ProceduralGeneration #Procedural #ProceduralArt

I found myself poking once again at Hilbert Curves tonight. But this time without recursion (rewrite systems).

I tried implementing the Skilling Transform (which is quite a lot of bit flippin). It goes from a distance to a N dimension position.

I got there in the end after I noticed I had one of my operations mirrored. 😅

I'll have to see how large I can draw one tomorrow. :blobhaj_witch: (which being able to choose any position to render will make this easy).

#HilbertCurve

Command-and-control IPv4 map, 2025-11-04 to 2025-11-17 #HilbertCurve
https://abjuri5t.github.io/SarlackLab/

208.87.200[.]0/21
104.140.144[.]0/20
154.89.184[.]0/21
149.30.224[.]0/19
91.92.240[.]0/22
45.153.34[.]0/24
38.128.0[.]0/9
124.220.0[.]0/14
104.206.234[.]0/23

Command-and-control IPv4 map, 2025-09-21 to 2025-10-04 #HilbertCurve
https://abjuri5t.github.io/SarlackLab/

104.140.144[.]0/20
104.206.234[.]0/23
154.89.186[.]0/23
38.128.0[.]0/9
154.89.190[.]0/23
154.89.184[.]0/24
154.89.185[.]0/24
154.89.189[.]0/24
38.32.0[.]0/11

Command-and-control IPv4 map, 2025-06-09 to 2025-06-22 #HilbertCurve
https://abjuri5t.github.io/SarlackLab/

38.128.0[.]0/9
43.136.0[.]0/13
124.220.0[.]0/14
1.94.0[.]0/15
47.92.0[.]0/14
39.104.0[.]0/14
111.229.0[.]0/16
101.42.0[.]0/15
106.52.0[.]0/14
47.100.0[.]0/14

Command-and-control IPv4 map, 2025-05-10 to 2025-05-23 #HilbertCurve
https://abjuri5t.github.io/SarlackLab/

38.128.0[.]0/9
124.220.0[.]0/14
43.136.0[.]0/13
1.94.0[.]0/15
196.251.116[.]0/23
176.65.140[.]0/23
47.92.0[.]0/14
39.104.0[.]0/14
196.251.84[.]0/22
176.65.142[.]0/24

The previous demo made me dig deeper into dithering algorithms. It's something I should have done years ago, as I've been using simple random dithering now and then, and I hadn't even thought of gamma correction. One algorithm in particular caught my eye: Riemersma dithering, which uses the Hilbert curve. Compared to the usual matrices for error diffusion, the curve approach seemed easier to implement in some ways, as it has fewer edge issues.

More interestingly, it struck a chord with my earlier experiments with space-filling curves in image processing. So it was a kind of familiar territory, but it also seemed esoteric enough that I could imagine making some new discoveries. For example, play with other plane-filling curves besides the Hilbert.

The first image uses the boustrophedon curve, which makes the vertical wave patterns I recall from a number of non-dithering demos. The second curve is what I call the diagstrophedon, a diagonal zig-zag starting from the top left corner, and I think its wavy artefacts make a nice match for Venus's hair.

Then in image 3 we have Hilbert, which doesn't seem to make any particular artefacts, and I guess that's a good thing for dithering. Finally 4 uses the Peano curve, which makes some fun wiggles in light areas.

#dithering #riemersmadithering #stippling #halftoneart #raster #pixelart #hilbertcurve #peanocurve #planefillingcurve #spacefillingcurve #pythoncode #opengl #algorithmicart #algorist #mathart #laskutaide #ittaide #kuavataide #iterati

The recent stipplings and partitionings reminded me of this demo from about 2 years ago. In short, it's a Hilbert curve where the iteration level varies by the colour value. I wanted to make some small changes, but I ended up rewriting it completely. The shader approach seemed needlessly heavy and redundant for something that works more naturally on a CPU. But mostly it was just a fun exercise in looking at the same problem from a different angle.

The first picture shows the original idea. With the new idea, I wanted to get rid of the slanted lines; the result doesn't feel any better to me, but I guess it's interesting in its own way.

#hilbertcurve #planefillingcurve #spacefillingcurve #lineart #linedrawing #singlelinedrawing #pythoncode #opengl #algorithmicart #algorist #mathart #laskutaide #ittaide #kuavataide #iterati

If anyone wants to make a Half-square Hilbert I made a toy to play with patterns. (fixed a bug from the first go)

I need fabric - so I plan to start maybe later this week.

https://codepen.io/fractalkitty/live/pvoBwxv/edc44d4417167d59d8b2c1d9ad574109

#codepen #p5js #quilting #hilbertCurve #fiberArt #quilts #mathart

Command-and-control IPv4 map, 2025-02-07 to 2025-02-20 #HilbertCurve
https://abjuri5t.github.io/SarlackLab/

104.21.0[.]0/17
172.67.0[.]0/16
217.30.160[.]0/20
95.216.0[.]0/15
13.60.0[.]0/15
121.40.0[.]0/15
69.67.151[.]0/24
147.185.221[.]0/24
3.80.0[.]0/12
13.208.0[.]0/13

Command-and-control IPv4 map, 2025-01-26 to 2025-02-08 #HilbertCurve
https://abjuri5t.github.io/SarlackLab/

3.64.0[.]0/12
38.128.0[.]0/9
124.220.0[.]0/14
195.177.95[.]0/24
216.24.212[.]0/24
147.185.221[.]0/24
3.128.0[.]0/11
13.60.0[.]0/15
92.119.36[.]0/24
94.156.166[.]0/23

Command-and-control IPv4 map, 2024-12-15 to 2024-12-28 #HilbertCurve
https://abjuri5t.github.io/SarlackLab/

124.220.0[.]0/14
101.42.0[.]0/15
1.94.0[.]0/15
47.96.0[.]0/13
47.92.0[.]0/14
121.40.0[.]0/15
101.200.0[.]0/15
111.229.0[.]0/16
43.136.0[.]0/13
113.45.128[.]0/17

Shadow pattern test, thinking about enclosures, this crude test inspired me with a bunch of ideas

#lighting #led #hilbertcurve

slice through the different orders

#hilbertcurve #creativecode #3d #houdini #design

I'm doing this Coding Train tutorial on a hilbert curve today, but trying to do it in houdini https://thecodingtrain.com/challenges/c3-hilbert-curve , pretty good progress so far, bitshifting makes me a little uneasy though. I also watched the 3blue1brown video on space filling curves, so good. https://www.youtube.com/watch?v=3s7h2MHQtxc
#houdini #hilbertcurve #creativecoding

Command-and-control IPv4 map, 2023-11-25 to 2023-12-08 #HilbertCurve
https://abjuri5t.github.io/SarlackLab/

85.209.176[.]0/24
143.92.60[.]64/28
163.5.64[.]0/24
154.204.24[.]192/26
194.49.94[.]0/24
120.233.114[.]0/23
95.214.26[.]0/24
194.33.191[.]0/24
185.65.105[.]0/24

FAQ:
Are all these #CIDR blocks and #subdomains 100% malicious? - No, but they do host a SUBSTANTIAL amount of #C2 infrastructure
What’s the grid thingy? - A #HilbertCurve map of #IPv4 space
You spelled #sarlacc wrong! - The name is intentional🤓

DM @Abjuri5t for more info

My #TwitterArchive (1/n):

Here is a small Python program I wrote between 2017-2018. It generates GIF animations of various algorithms running on the square grid. It directly encodes the whole animation into an optimized byte array with a built-in GIF encoder and outputs to GIF. No coloring/drawing function call in the code. A GIF of 3000+frames has only size <1MB!

Source code: https://github.com/neozhaoliang/pywonderland/tree/master/src/gifmaze

#maze #algorithm #GIF #hilbertcurve