As promised, here's some photos of love you!! camping trip to Canarcon George in QLD, Australia.

I'm finding this very interesting... An evolved neural network that plays the game of tic-tac-toe and so far is a pretty decent player. Here is a visualization of it's evolved "brain" that underwent GA (genetic algorithm) training with classification learning + self-play.

One of the nicest things about Go is the language itself, comparing Go to other popular languages in terms of the complexity to learn to be proficient in:

• Go: 25 keywords (Stack Overflow); CSP-style concurrency (goroutines & channels)
• Python 2: 30 keywords (TutorialsPoint); GIL-bound threads & multiprocessing (Wikipedia)
• Python 3: 35 keywords (Initial Commit); GIL-bound threads, asyncio & multiprocessing (Wikipedia, DEV Community)
• Java: 50 keywords (Stack Overflow); threads + java.util.concurrent (Wikipedia)
• C++: 82 keywords (Stack Overflow); std::thread, atomics & futures (en.cppreference.com)
• JavaScript: 38 keywords (Stack Overflow); single-threaded event loop & async/await, Web Workers (Wikipedia)
• Ruby: 42 keywords (Stack Overflow); GIL-bound threads (MRI), fibers & processes (Wikipedia)

July 1st. 63 days from now to implement a backward-incompatible change, apparently not open to other ideas like replacing blake with SHA, or discussing implementation challenges for other languages and platforms. Finally just closing #18, #19 and #20 without starting a proper discussion and ignoring a 'micro consensus' feels... not right.

I don't know what to think rather than letting it rest (May will be busy here) and focus on other stuff in the future.

twt-hash-v2.md#implementation-timeline

@andros Thanks! 🙏 Just re-followed @important_dev_news 👌

@lyse Love those green roll'n hills 👌 Btw, what's that rickety 'ol shed in 18? 🤔

@andros your feed is spitting out dupes? 🧐

Nice! 😊

And trying again.

What has been the hardest bug you got to fix? https://hackerweb.app/#/item/43461618

I always find the 'Adven of code' challenges difficult to follow. i18n-puzzles.com has been a blast, but I don't like having to think about puzzles on weekends. Like with exercise, doing it every day without rest doesn't sound healthy.

I'd rater have a weekly challenge, at most three.

Wow, this is a nice way to practice internationalization for our systems https://i18n-puzzles.com

#testing @Bob Hi Bob, nice to meet you!

Hi everyone, I've drafted a Request for Comments (RFC) to improve how threads work in twtxt: https://git.mills.io/yarnsocial/twtxt.dev/issues/18

I’d love your feedback! Please share your thoughts on anything that could be better explained, check if the proposed dates work for everyone, and I invite you to join the discussion...

I like this syntax, you have my vote, although I'd change it a bit like #<Alice https://example.com/twtxt.com#2024-12-18T14:18:26+01:00>

Hashes are not a problem on PHP, I dont know why it's slow to calculate them from your side, but I agree with your points.

BTW, did you have the chance to read my proposal on twtxt 2.0? I shared a few ideas about possible improvements to discuss: https://text.eapl.mx/a-few-ideas-for-a-next-twtxt-version https://text.eapl.mx/reply-to-lyse-about-twtxt

!<alice https://example.com/twtxt.txt> U2FsdGVkX187WpPAJXCusqEoTb3/tD62xN+TxudcTsPI+LqOJLPkl9aNE9MLg8lYRLfd9mSE33N6JeA0okLJ6Q==

@movq I'm glad you like it. A mention (<a href="/profile?url=https://www.uninformativ.de/twtxt.txt">@movq</a>) is also long, but we live with it anyway. In a way a replyto: is just a mention of a twt instead of a feed/person. Maybe we chould even model the syntax for replies on mentions: (#<2024-09-17T08:39:18Z https://www.eksempel.dk/twtxt.txt>) ?!

#processing #moire #RGB #midi #creativecoding #videoart

Playing around with #GLSL #shaders and webcam in #KodeLife