@tkanos@twtxt.net amazing!

@tkanos@twtxt.net That’s pretty impressive 👌

@lyse@lyse.isobeef.org @darch Can you look at this? 🤗

blacklisted because those are not real people? 🤔

@mckinley@twtxt.net Cool! 👌 So… Let’s nuke it? 🤔 Are you thinking of writing a new spec?

@lyse@lyse.isobeef.org Very nice photos 👌

@tkanos@twtxt.net HHahaha 🤣

@darch I’ll merge your PR today and teat 👌

Meanwhile I noticed this on your Pod

one other thing cool that you have not noticed but i want to share. Is that the first iterative version was taking 8 minutes to go on all twtxt / download/ parse. The new version using heavily go routines takes around 10 seconds.

Thanks @lyse@lyse.isobeef.org,

1. even a switch case would be better
2. done quickly
3. done quickly
4. yes BUT if I check only mentions I will loose the header following one, (that are not always in the same style: cf : https://niplav.github.io/twtxt.txt ), I can do both and only loose the redirection BUT I need to be bored again to do that change (1 hour I ll say)
5. (easy) when i will be bored again it will be on the pipe.

Thanks

I noticed some unnecessary horizontal rules being rendered at the bottom of twts in the conversation view lately with yarnd’s new design change. They can be seen at least when not being logged in. Not sure if it is the same experience with an active user session. I reckon there will be fork buttons then, so in that case they would be fine, indeed.

In fact, these lines are implemented as border-top CSS properties of twt-nav-classed <nav> containers. But the <nav>s are empty, so I would expect them not being there in the first place. Empty navigation doesn’t make much sense to me.

In any case, keep up the good work! :-)

@tkanos@twtxt.net Cool! I like your disclaimer in the readme. :-D A few things caught my eye while scrolling through the code, the ones I remember:

1. The protocol switch in lines 141ff could make use of else if.
2. There’s a superfluous space in the progress bar in line 155.
3. The User-Agent header contains a { which I reckon is a typo. Also, I reckon the URL and nick should be swapped, in case you wanted to stick to this discoverability format.
4. The feed discovery regex assumes that filenames always are twtxt.txt which will miss a few feeds, such as @anth@a.9srv.net’s and @hxii@0xff.nu’s. Parsing mentions would be more accurate. And then also parse all mentions from a twt, not just the first one.
5. If you’re still bored, adding support for archived feeds would be a thing. :-)

Anyways, nice work!

Actually I should black list search as well.

@mckinley@twtxt.net my bad, I ’ve blacklisted it in the code for next time (github-commit-fix)

A frost advisory already! I’m not ready to be inside all the time again…

Ah, cnbeta-com-rssding-yue.txt is hosted on feeds.twtxt.cc which isn’t blacklisted like feeds.twtxt.net is.

Outside of this thread, this comment syntax has been used exactly twice when searching every known, currently accessible twtxt feed on the Web.

$ grep -r '@<[^ ]*>'
buckket.org.txt:2016-02-12T18:37:00+01:00	Hey @<http://vigintitres.eu/twtxt.txt>, @<teddy https://data.trafficking.agency/twtxt.txt> und @[email protected] was geht? Ich bin’s @[email protected]!
[...]
hecanjog.com.txt:2020-09-03T17:36:00-05:00	@https://tilde.town/~lucidiot/[email protected] twtxt via DNS TXT would be insane and fun.

We checked out the routes for our scavenger hunt on Friday evening and man, did we enjoy a sunset. Bloody amazing.

Here are the top ten feeds by size. @prologic@twtxt.net is artificially low on the list because it’s separated into chunks, and @movq@www.uninformativ.de is listed twice. Once as www.uninformativ.de, once as uninformativ.de. I blame yarnd.

du -b * | sort -nr | head -n 10
5253921	www.lord-enki.net.txt
842733	cnbeta-com-rssding-yue.txt
755925	search.twtxt.net.txt
654717	prologic.txt
394380	jlj.txt
371632	assets.txt
246520	off_grid_living.txt
243953	mckinley.txt
225256	www.uninformativ.de.txt
225256	uninformativ.de.txt

cnbeta-com-rssding-yue.txt seems to be a syndication feed for https://cnbeta.com/ in twtxt format, assets.txt is @maya@maya.land, and the rest are fairly self-explanatory.

@tkanos@twtxt.net Thank you very much. I thought a collection of every twtxt feed would weigh more than 14 MiB uncompressed.

@prologic@twtxt.net you didn’t capture the best of the form :

@prologic@twtxt.net the fix is live now on neotxt.dk. let me know how it looks at your end?

@darch

@akoizumi@social.kyoko-project.wer.ee i can’t access the link…

Hmmm interesting 🤔

@darch 🤣

There is a commit now in the theme branch. See if it fixes it for you

@abucci@anthony.buc.ci Very nice thinking :D

I guess I can just look at the screenshot you posted 😂

@prologic@twtxt.net hmm maybe I have an especially rambunctious child lol

@prologic@twtxt.net

Brandolini’s law, also known as the bullshit asymmetry principle, is an internet adage that emphasizes the effort of debunking misinformation, in comparison to the relative ease of creating it in the first place. It states that “The amount of energy needed to refute bullshit is an order of magnitude bigger than that needed to produce it.”

1. Tweet bullshit
2. Countless others think hard to refute the bullshit, making countless tweets, amplifying “engagement”
3. ???
4. Profit

@abucci@anthony.buc.ci point taken 👌

@darch No it’s not too annoying. Need to get that PR finished I have in progress

Hah 😆

We never seemed to have this problem with our two kids? 🤔

@darch How do I find that out? 🤔

@tkanos@twtxt.net Really good question! I don’t honestly know 🤔

@abucci@anthony.buc.ci Explain?

My deep thought of the day is that Twitter exists to monetize Brandolini’s law.

In the time I spent thinking about it the ground started shaking, a scorpion stung me twice, and the oracle left.

crap I forget what you do when the oracle is there

@prologic@twtxt.net what is spam in twtxt ? I mean I just saw 2 hotel advertise so far.

@prologic@twtxt.net what’s the screen width of your iPhone?

@darch lol that’s what https://account.kyoko-project.wer.ee is for ;P

One of my favorite TRS-80 text adventure games, Madness And The Minotaur, running in Cool Retro Terminal.

It’s as if, in my mind, toilets are now things that should be locked. Very strange.

Long ago the baby grew mobile enough to start getting into things, especially toilets. We installed those plastic child-proof locks all over the house. Now, it feels very strange to use a toilet that does not have a lock on it.

I say that because one issue with an invite system is that it generates manual labor too. It could stop people from making spammy posts, sure. But it burdens someone with investigating potential new users, and if those new users are human and not bots, they can play nice till they get their account and then start posting spam anyway. It’s important to have layers of (semi-) automated systems so that the humans doing the ultimate moderating aren’t overwhelmed.

@prologic@twtxt.net Years ago I moderated a forum and found any and all of the following can help

• IP blacklists preventing registration
• CAPTCHA at registration time
• Email confirmation at registration time
• A “reputation” system limiting what new users can post
• Setting all links in posts nofollow (kills the benefit of SEO spam)
• Run through akismet before posts are posted (you could probably get spamassassin to do this too?)
• Extremely ruthless blocking

@prologic@twtxt.net is it getting to an annoying level?

I would rather see a lot of other features before.

What are the advantages to an invite system compares to just close registration and add a contact form for applying for an account?