@bender Haha 🤣

yep, it looks nice! How could add my URL? Is it following the same endpoints than https://registry.twtxt.org/swagger-ui/#/users/addUser ?

BTW, I think that the usage section has a wrong base URL or something.

For example if you enter here: https://watcher.sour.is/conv/4rx5iyq It says to look for this URL: https://watcher.sour.is/conv/4rx5iyq/api/plain/users

Which seems to return the content from https://watcher.sour.is

@eapl.me awesome, and thank you! Sorry I missed all that in the noise. I truly am a TL;DR fan! 😂

In Mexico you couldn't register the word Sonora (state), nor Taqueria (kind of restaurant) as there are two common words, but perhaps the combination of both is trademarkable, I'm not sure, so many 'taquerias' here don't file a trademark request. It's usually "Taquería [LAST_NAME]" or "Taquería [PLACE]".

At the same time, the word "taqueria" was trademarked in UK, like it would be "Paris" or "Pub" I guess, so basically Sonora Taqueria didn't reply to the cease and desist, based on:

[Lizbeth García]: A brand may not use a word that is generic or descriptive of the products or services it is putting into circulation on the market.

Since he (Ismael, Taqueria's representative) didn’t get any response, he decided to leave it in the hands of his law firm.

In early 2023, after all the noise on the internet and the mobilization caused by this case, an agreement was finally reached with Taquería to settle the matter peaceably.

In March 2023, Michelle and Sam decided to register the Sonora Taquería brand and logo with the UK Intellectual Property Office.

I am confused (maybe I missed what they said, or didn't read well). What was "Sonora Taqueria" answer to the cease and desist demand letter[1]? Did the accusers simply dropped their suit efford, or was "Sonora Taqueria" able to make their case (see [1])?

An interesting episode about naming stuff, and some implications of the "Trademarks"

https://radioambulante.org/en/translation/who-owns-the-taqueria-translation

https://github.com/sorenpeter/timeline

well, there is a whole book about piracy, DRM and selling stuff on the internet. https://en.m.wikipedia.org/wiki/Information_Doesn%27t_Want_to_Be_Free

So I won't add much to the topic, what I can say is that this is about being pragmatic. There is some people who's gonna spend their money on books but it requires publicity (polemic topic) and subsidizing creativity with our own money (another controversial one).

Otherwise it's a difficult discipline /profession /industry

@prologic you mean, "I'll ix this oon 😂" ™

I'll fix this soon 😂

@andros DRM is a solution to the wrong problem.

@eapl.me a “minimalistic” one too, just like Yarnd. 😅

yay! A new client 😀

definitely 1e100 superiorer

Now I'm looking forward to see the next version using MessagePack

@lyse 1000% superior!

Are you all forgetting today’s April’s Fool? 🤣

@bender So true 😥

@javivf Welcome indeed 🤗

that's certainty an interesting idea.

Building on top of that, I'm thinking of https://eapl.me/yatwt.yaml

well, that leads to a long conversation.

Piracy is a difficult topic which is very personal, so I won't say much about it.

On writing books, I've tried along with other digital products such as courses and videogames, and I got to confess that it has been hard for me.

If it helps, I think it all reaches our expectations on the activity and the result. If royalties is the expectation, it's going to be slow. By 5% of royalties, for a rough example, a huge amount of sales will be required to get a decent "wage", so I've understood of doing it by the side of a normal employment although it has been discouraging and a bit sad.

I have reflected about it in Spanish here: https://sembrandojuegos.substack.com/p/sobre-expectativas-al-crear-juegos

@prologic that's you, and me, and some others. Sadly, though, a huge majority (I don't have sources, or numbers, but "trust me, bro" :-P) will simply, gladly, and unapologetically, pirate.

@eldersnake Same!

@andros That's a shame. But here's the thing about piracy. If I could download a PDF or MP3/OGG of a Book I'd happily pay for this. If I could download an MP3/OGG of some Music I would pay for this. If I could download an MP4 of a Movie I would pay for this.

The reason piracy exists at all is economics and greed. If you make something affordable and convenient, there's no need to steal.

nice!

@lyse 🤣🤣🤣

@xuu 👍🏻

@prologic is it up? How can we tell?

Okay trying SqliteCache again with a slight tweak. I might have to rethink the hard-coded LIMIT 50.

Going back to old MemoryCache for now and going to bed 🛌

Hmmm this needs a bit more work.

And we're back. On the new Sqlitecache 🥳

Ooops I ran a docker build on one of my production nodes (the ingress node) 😱

@bender Okay 👌

👋 Folks that use this pod, I'll be rolling out an experimental new caching backend to this pod shortly. Stay tuned. Please provide feedback either here via Twtxt or on IRC. Thanks! 🙏

I see nothing wrong with the "implications". I would call them features. I think this will be the best thing that happened to Yarn since the subject extension.

There are however a few implications to note:

• It will be possibly to page through much larger quantities of twts per feed, this is potentially unlimited (depends on disk space)
• Automated Feeds (bots) like @tiktok will now behave/display very differently. You will see all it's historical Twts, whereas before you'd only see the one because the MemoryCache's behavior was to "replace" Twts.

I'm hoping everything else remains the same and true to what we've collectively built and to spec. Replies work, Forks work, various views, filters and so on still work. I'm developing this new cache in a way that uses a "delegate" pattern and a double read / double write with metrics so I can over time see that none of the "old cache" is used anymore.

I think my new SqliteCache is almost ready for prime time 🤞

This is why I blocked entire ASN(s) 🤣

@bender Soon 🤣

@bender Yeah me too hmm 🧐

@prologic I noticed that the hash also shows (as in clearly visible) on the “in-reply-to”. That doesn’t happen with any other client—well, at least not with Yarn, nor jenny.

@prologic show, or it didn’t happen. 😜

@eapl.me@eapl.me Ahh I see 😅

@xuu Got the most basic view working 😅

thanks for sharing @xuu!

Checking for example https://watcher.sour.is/api/plain/twt or https://registry.twtxt.org/api/plain/tweets, I don't know whether this syntax is being used by clients or by people. Is it integrated on Yarn in any way? Genuinely asking to know more about it.

If I might throw a quick thought to those working on the registries, it would be nice to have an endpoint with a valid twtxt output (perhaps cached or dumped to a static file) which a client could point to, helping to discover it's content in a way which is compatible with the twtxt spec.

Taking the first twt I found in https://watcher.sour.is/api/plain/twt as an example: `reddit_world_news

sorry @prologic, timeline doesn't autocomplete the mentions yet, and it was 'difficult' to look for your URL from the phone.

@xuu Actually... I'm working on a new Sqlite backend/cache for yarnd 🤣 I might revive yarns (the crawler / search engine) one day 🤞

@eapl.me@eapl.me What's with your client not using the proper syntax for mentions?

$ bat 'https://twtxt.net/twt/lnrgahq' | jq '.text'
"(<a href="?search=4xaabhq" class="tag">#4xaabhq</a>) thanks @prologic! 
@bender the idea of the RFC was to reach an agreement on a difficult problem, receiving proposals, and the voting is a simple count to gauge the sentiment of \"is this a problem worth to be fixed?, are we committed to implement a change in our clients?\" 

But that's a fair point. What do the community expect? What do y'all expect?"

🤔

somehow I forgot that existed.

Perhaps it was its mention of being a demo implementation here: https://twtxt.readthedocs.io/en/latest/user/registry.html#registry So I though it wasn't really active.

Anyway, I think that's a good idea.

Is there something similar available on Yarn? Sorry for for asking if that was mentioned recently.

I think that the clients may help you to submit your URL to these directories, and also to get a view of the twts in them.

thanks @prologic! @bender the idea of the RFC was to reach an agreement on a difficult problem, receiving proposals, and the voting is a simple count to gauge the sentiment of "is this a problem worth to be fixed?, are we committed to implement a change in our clients?"

But that's a fair point. What do the community expect? What do y'all expect?