xodn348

9 ms·

1.
by xodn348 4mo ago
I had unused token in claude code so that I wanted burn that overnight. Three agents were writing the future with 3 different perspective. It turned out that human kind did not perish but still had same problem between humans again for 200
2.
by xodn348 4mo ago
yes, it was flagged to LLM writing somehow. I wonder if this post can be seen others after the flag. Thank you for letting me know!
3.
by xodn348 4mo ago
Thanks for the info!
4.
by xodn348 4mo ago
haha thanks
5.
Can you see my post?
4 points by xodn348 4mo ago|7 comments
6.
by xodn348 5mo ago
Let me have fun with it. Thanks
7.
by xodn348 5mo ago
Hope you enjoy your life and time.
8.
by xodn348 5mo ago
I did not understood the meaning of your words.
9.
by xodn348 5mo ago
This was what I was targeting. Thanks
10.
by xodn348 5mo ago
haha great prose
11.
by xodn348 5mo ago
I'm doing what people wants. Thanks!
12.
by xodn348 5mo ago
/destiny compat <partner birth> <city> <m|f> do it now.
13.
by xodn348 5mo ago
Auto-run on session start (optional) added. Please check it out!
14.
by xodn348 5mo ago
I actually did not use prompts here. It is actual calculation from the python lunar and it cast the result to LLM which you use. The LLM has the old books such as giving you your fortune following lunar year calculation. Have a fun with it!
15.
by xodn348 5mo ago
fair points. I will take a look at it
16.
by xodn348 5mo ago
This is my fun project! Not a profitable entity. Thanks
17.
by xodn348 5mo ago
Just edited readme as well
18.
Show HN: Destiny – Claude Code's fortune Teller skill(github.com)
41 points by xodn348 5mo ago|41 comments
19.
by xodn348 6mo ago
That's a fascinating idea! Hangul is indeed compositional — 한 = ㅎ + ㅏ + ㄴ — so in theory you could assign meaning to individual jamo components. But in practice, breaking syllables into jamo would make keywords less readable, which goe
20.
by xodn348 6mo ago
I agree with your opinion and I was wonder how the Korean could be used in the world with full of Eng. Thanks for your feedback!
21.
by xodn348 6mo ago
That is a fair feedback and I have known those languages which are very reasonable and fairly designed language. But I wanted to more focused on translated into rust for english speakers first, which would make bigger user for this language
22.
by xodn348 6mo ago
I personally don't know Hanja at all, and I think that's common for most younger Koreans. Korean did borrow from Chinese characters historically, but it's similar to how English was influenced by Dutch, German, French, and La
23.
by xodn348 6mo ago
Honest answer: right now it's mostly a keyword translation with English-like syntax order. Korean is SOV (subject-object-verb) but Han follows English SVO order — 목록.추가(값) reads like "list.add(value)" not the Korean natural o
24.
by xodn348 6mo ago
This tons of Eng documents and contents cannot be translated once but this project is trying to use another language for future use. Thanks for the comment, though.
25.
by xodn348 6mo ago
Haha, using Eng has been reasonable for decades. Thank you very much of your comments.
26.
by xodn348 6mo ago
Thank you for your empathy. English has been the one of the most frequent languages for globe so that it is reasonable to Eng in many coding project, though.
27.
by xodn348 6mo ago
Ha, neat trick. But macro substitution and a purpose-built language are very different — Han has a full pipeline (lexer → parser → AST → interpreter + LLVM codegen) designed around Korean from the ground up. Error messages, REPL, LSP hover
28.
by xodn348 6mo ago
Force for good be with you
29.
by xodn348 6mo ago
funny examples, though.
30.
by xodn348 6mo ago
Good point about compactness — 실명인증계정생성 vs AbstractVerifiedIdentityAccountFactory is a real example where Korean shines. One distinction though: Han uses actual Korean words, not transliterations. 함수 means "function" in Korean, 만약

More ›