Over the past few weeks I've been experimenting with and doing some deep learning and researching into neutral networks and evolutionary adaptation of them. The thing is I haven't gotten very far. I've been able to build two different approaches so far with limited results. The frustrating part is that these things are so "random" it isn't even funny. Like I can't even get a basic ANN + GA to evolve a network that solves the XOR pattern every time with high levels of accuracy. 😞

fit 1 $ spin (saw 0.1 * sign fxy) $ rect 0 1 - rect 0 0.99 >> add; #punctual #livecoding #creativecoding #videoart

@javivf Sorry. 😂 Meet me on IRC at irc.mills.io in #edgeguard 👌 I'm @james there 😅

Farrrk me Google search is and these days. Will they please "fuck off" with this Gemini AI garbage at the top that takes forever and is distracting as shit™ 💩 Fark me 🤦‍♂️ #Google #Search #Sucks #AI #Gemini

@movq Yeah I actually use sift a lot these days for most "searching" -- at least code and text searching. For finding files by name I still use find | grep.

Move beyond basic threshold alerts! Define clear Service Level Objectives (SLOs) and measure Service Level Indicators (SLIs) to track real user impact. Use Prometheus to alert when your SLOs are at risk, ensuring you focus on what truly matters to your users. #Monitoring #SRE #Prometheus

@andros what makes Kagi "the best search engine"? It is premium, alright. Allegedly you don't get ads, but pay up-front for it, monthly.

@thecanine Yeah this is where I think all the hype really falls down. It's all just a really really expensive search engine and auto-complete 🤦‍♂️ That's it!

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

Finally I propose that we increase the Twt Hash length from 7 to 12 and use the first 12 characters of the base32 encoded blake2b hash. This will solve two problems, the fact that all hashes today either end in q or a (oops) 😅 And increasing the Twt Hash size will ensure that we never run into the chance of collision for ions to come. Chances of a 50% collision with 64 bits / 12 characters is roughly ~12.44B Twts. That ought to be enough! -- I also propose that we modify all our clients and make this change from the 1st July 2025, which will be Yarn.social's 5th birthday and 5 years since I started this whole project and endeavour! 😱 #Twtxt #Update

And speaking of Twtxt (See: #xushlda, feeds should be treated as append-only. Your client(s) should be appending Twts to the bottom of the file. Edits should never modify the timestamp of the Twt being edited, nor should a Twt that was edited by deleted, unless you actually intended to delete it (but that's more complicated as it's very hard to control or tell clients what to do in a truely decentralised ecosystem for the deletion case). #Twtxt #Client #Recommendations

Just like we don't write emails by hand anymore (See: #a3adoka), we don’t manually write Twts or update our twtxt.txt feeds. Instead, we use modern Twtxt clients that conform to the specifications at Twtxt.dev for a seamless, automated experience. #Twtxt #Twt #UserExperience

Nobody writes emails by hand using RFC 5322 anymore, nor do we manually send them through telnet and SMTP commands. The days of crafting emails in raw format and dialing into servers are long gone. Modern email clients and services handle it all seamlessly in the background, making email easier than ever to send and receive—without needing to understand the protocols or formats behind it! #Email #SMTP #RFC #Automation

First draft of yarnd 0.16 release notes. 📝 -- Probably needs some tweaking and fixing, but it's sounding alright so far 👌 #yarnd

by commenting out DMs are you giving up on simplicity? See the Metadata extension holding the data inside comments, as the client doesn't need to show it inside the timeline.

I don't think that commenting out DMs as we are doing for metadata is giving up on simplicity (it's a feature already), and it helps to hide unwanted DMs to clients that will take months to add it's support to something named... an extension.

For some other extensions in https://twtxt.dev/extensions.html (for example the reply-to hash <a href="?search=abcdfeg" class="tag">#abcdfeg</a> or the mention @ < example http://example.org/twtxt.txt >) is not a big deal. The twt is still understandable in plain text. For DM, it's only interesting for you if you are the recipient, otherwise you see an scrambled message like 1234567890abcdef=. Even if you see it, you'll need some decryption to read it. I've said before that DMs shouldn't be in the same section that the timeline as it's confusing.

So my point stands, and as I've said before, we are discussing it as a community, so let's see what other maintainers add to the convo.

Regex Isn't Hard - Tim Kellogg 👈 this is a pretty good conscience article on regexes, and I agree, regex isn't that hard™ -- However I think I can make the TL;DR even shorter 😅

Regex core subset (portable across languages):

Character sets • a matches “a” • [a-z] any lowercase • [a-zA-Z0-9] alphanumeric • [^ab] any char but a or b

Repetition (applies to the preceding atom) • ? zero or one • * zero or more • + one or more

Groups • (ab)+ matches “ab”, “abab”, … • Capture for extract/substitute via $1 or \1

Operators • foo|bar = foo or bar • ^ start anchor • $ end anchor

Ignore non‑portable shortcuts: \w, ., {n}, *?, lookarounds.

#regex101

#event:abc123 RSVP: yes +1

#event:abc123 Go Meetup – Sat Apr 27, 3pm @ Darling Harbour

#poll:xyz123 Vote: None

#poll:xyz123 Favorite Go framework?

• Gin
• Echo
• Chi

Hmmm there's a bug somewhere in the way I'm ingesting archived feeds 🤔

sqlite> select * from twts where content like 'The web is such garbage these days%';
      hash = 37sjhla
  feed_url = https://twtxt.net/user/prologic/twtxt.txt/1
   content = The web is such garbage these days 😔 Or is it the garbage search engines? 🤔
   created = 2024-11-14T01:53:46Z
created_dt = 2024-11-14 01:53:46
   subject = <a href="?search=37sjhla" class="tag">#37sjhla</a>
  mentions = []
      tags = []
     links = []
sqlite>

Timeline of Evolution of Twtxt/Yarn.social:

• 2016 – Twtxt created by John Downey: plain text + HTTP = minimalist microblogging
• 2017–2019 – Community builds CLI tools, but adoption remains niche
• 2020 – Yarn.social launched by @prologic with federation, threading, UI
• 2021–2023 – Pods sync, user mentions, blocking, search, and media support added
• 2024+ – Yarn.social becomes the reference Twtxt platform, with active federated pods

@andros Curious where this root twt is?! 🤣 Apparently my pod doesn't have it and I can't find it anywhere. It's suppose to be <a href="?search=l4doaxa" class="tag">#l4doaxa</a>

This on vp-compact.css:

.avatar:not(<a href="?search=profile" class="tag">#profile</a>-avatar .avatar) {
    width: 2rem !important;
    height: 2rem !important;
    margin-top: -0.25rem !important;

}

Is colliding with yarn.min.css:

.avatar, .avatar-full {
    width: 3.5rem;
    height: 3.5rem;
    object-fit: cover;
    border-radius:var(--border-radius)
}

Dam the search here is sooo good now 😅

Anyway. this was a good use for search btw. I couldn't find my Twt, so I just quickly searched for it, snap, bingo I found it in a snap! 🫰

Doesn't look like it Hmmm

sqlite> select * from twts where content LIKE '%Linux installation%';
    hash = znf6csa
feed_url = https://www.uninformativ.de/twtxt.txt
 content = I wonder if my current Linux installation will actually make it to 20 years:

    $ head -n 1 /var/log/pacman.log
    [2011-07-07 11:19] installed filesystem (2011.04-1)

It’s not toooo far into the future.

It would be crazy … 20 years without reinstalling once … phew. 🥴
 created = 2025-04-07T19:59:51Z
 subject = (<a href="?search=znf6csa" class="tag">#znf6csa</a>)
mentions = []
    tags = []
   links = []

@prologic, from IRC:

1. Saving preferences is failing. Specifically trying to save "Open Links" on the same window. For sure it isn't happening. Check errors on browser's console.
2. Search results pagination is broken. Search for "twtxt.net" and see it. Also, picking oldest/newest makes no difference on that search query.

Ahhh! It's all Soren's fault 🤣

commit ea9eaaf3d3977701dcb84b927c77c4f921bdbf43
Author: sorenpeter <sorenpeter@noreply@mills.io>
Date:   Sat Sep 24 23:34:07 2022 +0000

    Replacing Pico.css with Simple.css (<a href="?search=990" class="tag">#990</a>)

    Replacing pico.css with simple.css along with some small UI changes

@prologic I can live without highlights. Actually, I prefer not to have them. A good search is all I want.

Search syntax appears to be:

hello
"hello world"
hello AND world
hello OR world
hello NOT world
"this is a phrase"

@prologic pretty neat, search actually works now!

@lyse I'm open to other suggestions 🤣 But hopefully both adding the additional prompt, not allowing it to enter shell history and removing from my shell history prevents me from doing such silly things in haste by pressing ^R and using fuzzy search which if you type fast you sometimes get wrong 😑

FYI: I've re-opened up search for anonymous use. So things like this now work without having to have an account on this pod or login. 👌 #search #twtxt

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

[lang=en] @xuu gotcha! From that PR #17 I think it was reverted? We could discuss about metadata later this month, as it seems that I'm the only person using it.

I've added a [lang=en] to this twt to see current yarn behaviour.

looks good to me!

About alice's hash, using SHA256, I get 96473b4f or 96473B4F for the last 8 characters. I'll add it as an implementation example. The idea of including it besides the follow URL is to avoid calculating it every time we load the file (assuming the client did that correctly), and helps to track replies across the file with a simple search.

Also, watching your example I'm thinking now that instead of {url=96473B4F,id=1} which is ambiguous of which URL we are referring to, it could be something like: {reply_to=[URL_HASH]_[TWT_ID]} / {reply_to=96473B4F_1} That way, the 'full twt ID' could be 96473B4F_1.

Added support for uploading images to to #Timeline Right now you need to copy the markdown code yourself, but next up would be to lean some JS or use HTMX to make the process more smooth.

#genuary #genuary2025 #genuary17 Maybe related to today prompt: What happens if pi=4? https://youtu.be/tGfUaZ8hTzg

nice! would you mind elaborating a bit? Is that the scientific method? I couldn't find anything related when I searched for it.

and going back to a handle you could input in your client to look for the user/file, like @nick@domain.tls I think Webfinger is the way to go. It has enough information to know where to find that nick's URL.

@prologic does that webfinger fork made by darch work OK with yarn as it is now? (I've never used it, so I'm researching about it) https://darch.dk/.well-known/webfinger/

after thinking and researching about it, yep, I agree that WebFinger is a good idea.

For example reading here: https://bsky.social/about/blog/4-28-2023-domain-handle-tutorial I wasn't considering some scenarios, like multiple accounts for a single domain (See 'How can I set and manage multiple subdomain handles?' in the link above)

haha, that's gold xD.

#randomMemory I remember when I was starting to code, like 30 years ago, not understanding why my Basic file didn't run when I renamed it to .exe

And nowadays, I've seen a few Go apps in a single executable, so twtxt.exe could be a thing, he!

Wow, it seem my #Webmentions implementation works from Mastodon via brid.gy

@eapl.mx Yes, the idea is to add User Agent support to #Timeline. Right now it just adds every request to a growing log file, but I have also been working on a way to analyse it, so it only saves the time of the latest request. I'm not sure how to make it part of timeline itself, since it requeses that you redirect/rewrite from twtAgent.php to the acctual twtxt.txt Help with making Timeline send proper User Agents to others would be much appreciated:)

"A minimalist social network powered by plain text files" - my talk about #twtxt from #Piksel24 Festival is now on YouTube and slides can be found at http://darch.dk/twtxtalk-piksel

Great to see another user @aelaraji - And I can confirm that my #webmentions works from your server (I know, the formatting is messed up;)

Seven Bit Encoding by Dylan Beattie #music

@eapl.me here are my replies (somewhat similar to Lyse's and James')

1. Metadata in twts: Key=value is too complicated for non-hackers and hard to write by hand. So if there is a need then we should just use #NSFS or the alt-text file in markdown image syntax ![NSFW](url.to/image.jpg) if something is NSFW

2. IDs besides datetime. When you edit a twt then you should preserve the datetime if location-based addressing should have any advantages over content-based addressing. If you change the timestamp the its a new post. Just like any other blog cms.

3. Caching, Yes all good ideas, but that is more a task for the clients not the serving of the twtxt.txt files.

4. Discovery: User-agent for discovery can become better. I'm working on a wrapper script in PHP, so you don't need to go to Apaches log-files to see who fetches your feed. But for other Gemini and gopher you need to relay on something else. That could be using my webmentions for twtxt suggestion, or simply defining an email metadata field for letting a person know you follow their feed. Interesting read about why WebMetions might be a bad idea. Twtxt being much simple that a full featured IndieWeb sites, then a lot of the concerns does not apply here. But that's the issue with any open inbox. This is hard to solve without some form of (centralized or community) spam moderation.

5. Support more protocols besides http/s. Yes why not, if we can make clients that merge or diffident between the same feed server by multiples URLs

6. Languages: If the need is big then make a separate feed. I don't mind seeing stuff in other langues as it is low. You got translating tool if you need to know whats going on. And again when there is a need for easier switching between posting to several feeds, then it's about building clients with a UI that makes it easy. No something that should takes up space in the format/protocol.

7. Emojis: I'm not sure what this is about. Do you want to use emojis as avatar in CLI clients or it just about rendering emojis?

What are peoples #IRC setup? Do you have your own bouncer server or just have a you computer always on? And do you IRC on mobile?