@prologic@twtxt.net yes, I agree. Itâs bizarre to me that people use the thing at all let alone pay for it.
It feels like every time I come across a Gemini capsule I find interesting, the owner suddenly stops posting and leaves the protocol. Maybe thatâs a lesson for me: if I like their content, reach out to them and let them know.
Iâll let the head of the bird site comment on that:

Progress! so i have moved into working on aggregates. Which are a grouping of events that replayed on an object set the current state of the object. I came up with this little bit of generic wonder.
type PA[T any] interface {
event.Aggregate
*T
}
// Create uses fn to create a new aggregate and store in db.
func Create[A any, T PA[A]](ctx context.Context, es *EventStore, streamID string, fn func(context.Context, T) error) (agg T, err error) {
ctx, span := logz.Span(ctx)
defer span.End()
agg = new(A)
agg.SetStreamID(streamID)
if err = es.Load(ctx, agg); err != nil {
return
}
if err = event.NotExists(agg); err != nil {
return
}
if err = fn(ctx, agg); err != nil {
return
}
var i uint64
if i, err = es.Save(ctx, agg); err != nil {
return
}
span.AddEvent(fmt.Sprint("wrote events = ", i))
return
}
This lets me do something like this:
a, err := es.Create(ctx, r.es, streamID, func(ctx context.Context, agg *domain.SaltyUser) error {
return agg.OnUserRegister(nick, key)
})
I can tell the function the type being modified and returned using the function argument that is passed in. pretty cray cray.
Itâll track a bunch of finger(1) endpoints and let you see whatâs new. Very early draft. Not actually a social network, more an anti-social network for â80s CompSci transplants. :-)
One year ago to the date I made the lastest update for #phpub2twtxt to github and now 365 days later I have published #pixelblog as its successor - lets see where things are going for trip around the sun
@prologic@twtxt.net let us take the path of less resistance, that is, less effort, for now. I am going to be a great-grandfather before search ever get implemented locally, least one to search on âall podsâ. In other words, let us donât bite more than we can chew. đš Neep-gren!
@prologic@twtxt.net I fully agree with making it a pod-level setting (forget about user-level, let us not complicate things too much; we all know users know nothing). Should I send a latinum over for this, or will an issue just suffice? Neep-gren!
@fastidious@arrakis.netbros.com, I am sure profitâor the search for itâwas involved. Most likely that pilot was a Ferengi in disguise. We are known to visit lesser planets seeking to exploit. Sometimes it works out, sometimes it doesnât. Hoping my fellow Ferengi fares well or, at the very least, lets me know where his Latinum is.
The complexity is a feature. It means standards can be replaced with products that let providers get their cut. It means putting data into the slowest most expensive database in cost and enviromnmental impact.
@fastidious@arrakis.netbros.com
I hit RETURN after the subject, and nick [âŚ]
I shows fine on jenny. Letâs see how Yarn renders mine above.
@fastidious@arrakis.netbros.com
I see it, but can you see my reply? Letâs find out!
@prologic@twtxt.net
BEGIN SALTPACK ENCRYPTED MESSAGE. kiNJamlTJ29ZvW4 RHAOg9hm6h0OwKt iMGN9pY3oc5peJE UcRA8ysyQ7e8co9 shMfScCFgmQgU5Q 6w6XD2FT6szO1i1 N8qWqFRwJcHliqp hlaSvsTNhuwe1Fs KESywjL8ZvxNeyb ro0RVcRIip4Itpv NKvFZ822RoDR6pb hVvSqgubr3IanFT 6VAGQe2mYvErE7i G0O284HNvj0tcbC qzY0uB3ZFePu2fp l8nHOeEm9QLkH4Y PNKY2bXjqtblDGq 7pNiNHXtNJDjrpG nUoEXK9CaB6DGe7 oaF1P9sTz7fFrUo qwIgzw4Z1yqULQW 6dcFgsGwQEMc6bV mXuJHkrDWbfw35o 2Lpevp4PAVw884t 5Jf4cDLAe3QfRjG 4y6uwJg8BwIr2Lb 2pCX23ffwJ0yjGs Ptyzuaq2Alfl3QX AcMNGFzTNHjHfqY cvsoTrSMbyE3ssS A0k0zeRJQLoGOK4 DGkdltMXaQyXq9d zzbueCXCsIM1vYG vcy85vKuqM0ikoG caUNUuIVCc6FMs5 2JtadCtbVKyG8Wx Z4R672Fd71eDjCc lEtCdJlEAmEJePw ThkxVJutJt2R2Ce lKp9tEKmrx1jMWW V8hJNTaQGAfFDEB Unh8YasaV24NqAi GKSnstFWk3DYCxC lvws9js2jJ9OKeq 2mMgFmzEmCr99RW 2CrxZStPpB1iEDU d0Un7W7bnyo2KpV xqe8rCeHA6CUwVs 0XMmxPvU1Q0wp9A 0Jwxo5CY9QF5EJl yVwaXiVP2CKw2aH tqEE5yTp9OmpNF0 jFqgr8vHOjosPyL c3nke0S9QFjAxjt Dr6xwYpnASDr1l1 N96G3FB5iVYLFaz FkXGm7oQNTaDY8e OtHXQiXRhQY3PCi VIYYVhc9RExVnfX fvzgfgc5uSxUynD sPp4eq2rJXkX5. END SALTPACK ENCRYPTED MESSAGE.
Letâs see how resilient this is, or if it breaks.
If
Subjectcontains the full twt, then you can skim over conversations just by reading those lines in muttâs index pager
Yes, I do the same, true.
So I decided: Okay, letâs have mutt do it.
And Mutt does it well. I agree it was/is a good idea.
The subject lines are already âcompressedâ
I noticed, yes.
I am not sure why I asked to begin with; in retrospect, in was a silly request. Perhaps the OCD in me got triggered while viewing rich headers, on a specific twt, when I saw the huge subject line that is, otherwise, always hidden.
Anyway, donât mind me, move along. đ
@eldersnake@yarn.andrewjvpowell.com
Google or (insert your favourite search engine here) have never let me down. Also, Youtube has repair guides, and HOWTOs for just about anything, and everything.
Now, letâs talk about the Mac.
- [x] Lawn mowed, edged, trimmed, and blown.
- [x] Driveway and sidewalks pressured washed.
- [x] Weed killer sprayed.
Mission accomplished. I feel like watching âThe Hijacker Guide to the Galaxyâ. Letâs see which streaming service is offering it for free, or for rent.
On the blog: Letâs FixâŚFacebook https://john.colagioia.net/blog/2021/10/17/facebook.html #lets-#fix #facebook #socialmedia
@prologic@twtxt.net
Letâs make it four! đ
@lyse@lyse.isobeef.org I think that was it, mate! đ I was calling . $HOME/.bashrc on the cron job line, but was missing some extra LANG ones. Letâs see how it goes now.
How would jenny handle multiline twts? Letâs find out! - One - Two - Three And: 1. One 2. Two 3. Three
@quark@twtxt.netbros.com I have removed the cron job, and added jenny -f to the small script that starts mutt with the .muttrc-jenny file. That way when I open, it refresh the feed before. Letâs see how it goes.
I might have figure out what was causing duplicated entries here. I think running jenny -f while mutt is open was causing it. I have disabled the cron job, and it doesnât seem to be happening anymore. Letâs see how accurate my theory is. đ
On the blog: Real Life in Star Trek, Let That Be Your Last Battlefield https://john.colagioia.net/blog/2021/05/27/battle.html #scifi #startrek #closereading
@prologic@twtxt.netYes, I think tags should just be #foo, and let the client figure out searching if it cares.
@prologic@twtxt.net in theory shouldnât need to let users add feeds.. if they get mentioned by a tracked feed they will get added automagically. on a pod it would just need to scan the twtxt feed to know about everyone.
NO MORE TESTING - LETS GET REAL - Its now possible to post to this twtxt from irc://irc.maddshark.com:7029/discord