prologic @twtxt.net

Follow

Problems are Solved by Method\" 🇦🇺👨‍💻👨‍🦯🏹♔ 🏓⚯ 👨‍👩‍👧‍👧🛥 -- James Mills (operator of twtxt.net / creator of Yarn.social 🧶)

Block / Report User

If this user/feed is violating this Pod's (yarn.meff.me) community guidelines as set out in the Abuse Policy, please report them immediately!

You are also free to Unfollow or Mute this user or feed. Muting will also remove that user/feed's content from your view and you will no longer see content from that user/feed anywhere.

@prologic does not follow you (they may not see your replies!)

Recent Twts

Recent twts from prologic

prologic @twtxt.net
 (4d ago)

(#xzrz2ya) My Hypothesis for why registries didn’t work and why they still won’t really work today is because the bend the rules of “true” decentralization a bit. Users have to pick one or more registries to “register” to. Why would they want to do this? What is their incentive to do so? Then on the other hand, users need a client that has registry support, but now which registry or sets of registries do you choose?

#g7clyxa
prologic @twtxt.net
 (4d ago)

(#z4hlt4a) @bender@twtxt.net I can fix and make that work in the parser too. But I’m no longer sure how to cater for the general case. It’s too much to support all punctuation whilst at the same time as other contradicting rules. For example you cannot both support . in nicknames and then expect to be able to to end a mention with a . 🤦‍♂️

#uojqh5a
prologic @twtxt.net
 (4d ago)

(#z4hlt4a) There are 5 of such “Twters” on this pod that have periods in their nick 😢

sqlite> select count(distinct(nick)) from twters where nick like '%.%';
count(distinct(nick)) = 5
sqlite> select distinct(nick) from twters where nick like '%.%';
 nick = @marado@ciberlandia.pt

 nick = eapl.me

 nick = eapl.mx

 nick = grumpygordie.great-site.net

 nick = @chyrp.doesnm.cc
#s75rgmq
prologic @twtxt.net
 (4d ago)

(#z4hlt4a) I’ll see if I can fix this and write a test case for what’s going on here. I think this is made difficult now because folks like @eapl.me@eapl.me decide that it’s okay to have a . (period) in their # nick 🤣 tbh I think nick(s) should have rules of what they can and cannot be comprised of. i.e: no punctuation 🤦‍♂️

#p5lnz5q
prologic @twtxt.net
 (4d ago)

(#uluw5lq) @bender@twtxt.net This story just reminds me of the couple of times we’ve paid for things in cash 💰 💲 and the stupid banks with the ridiculous “scam alert policy” ask you all kind of dumb ass questions about what you need the cash for 🤦‍♂️ One of these days I need an excuse to buy something that costs a few $k just so I can answer when asked, “what do you need the cash for?” to which my response will be “drugs and hookers of course!” 🤣

#6w7s3gq
prologic @twtxt.net
 (5d ago)

(#4kymicq) @bender@twtxt.net You said:

as long as those working on clients can reach an agreement on how to move forward. That has proven, though, to be a pickle in the past.

I think this is because we probably need to start thinking about three different aspects to the ecosystem and document them out:

  • Specifications (as they are now)
  • Server recommendations (e.g: Timeline, yarnd, etc)
  • Client recommendations (e.g: jenny, tt, tt2, twet, etc)
#xwbiwqa
prologic @twtxt.net
 (5d ago)

(#4rln6eq) @andros@twtxt.andros.dev Haha 🤣 We’ve explored this idea in the past and we decided that it’s actually a good idea to have an “append-only” feed for various reasons. We’ve also explored the idea of using Range requests, but opted instead to just archive/rotate our feeds periodically 😅 There really isn’t much point in having a feed in reverse chronological order, except (maybe?) so a human read view the new twts at the top of the file?! 🤣

#y7ufoiq
prologic @twtxt.net
 (5d ago)

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

#r2hdu6q