@carsten@yarn.zn80.net yeesh, itâs a for-pay company I wouldnât give them the output of your mind for free and train their AI for them.
@xuu@txt.sour.is this is alarmingly catchy
@xuu@txt.sour.is everyoneâs moving to gated communities!
@prologic@twtxt.net ack, I didnât see this before. Get well soon!
twtxt, as I believe it was originally intended, are short little status updates â thatâs it.
So, basically a .plan file for finger. But, on the web. like a *web*finger. We have come full circle on this loop!
@prologic@twtxt.net Iâm a bit of a GPU junkie (đł) and I have 3, 2019-era GPUs lying around. One of these days when I have Free Timeâą Iâll put those together into some kind of clusterâŠ.
@xuu@txt.sour.is @prologic@twtxt.net Yarn.social without threading (as it would be the case in a âtruncatedâ feed) does not make sense to me.
Put another way: Yarn.social is not twtxt. The content that we all have in our feeds really is much closer to a web forum or usenet or whatever. Itâs threaded conversations. twtxt, as I believe it was originally intended, are short little status updates â thatâs it. The formats of Yarn.social and twtxt might be very similar, but the content is vastly different and, in a way, incompatible. (As such, I think I understand very well that the original twtxt crowd is disgruntled.)
That proposed truncated feed doesnât really provide any value, if you ask me. đ€ Itâd just be chaotic.
yarnd, tt, jenny, twtr and other clients? đ€ Thinking about (and talking with @xuu on IRC) about the possibility of rewriting a completely new spec (no extensions). Proposed name yarn.txt or "Yarn". Compatibility would remain with Twtxt in the sense that we wouldn't break anything per se, but we'd divorce ourselves from Twtxt and be free to improve based on the needs of the community and not the ideals of those that don't use, contribute in the first place or fixate on nostalgia (which doesn't really help anyone).
@darch@neotxt.dk yes!
@prologic@twtxt.net yeah. Iâd add âBig Dataâ to that hype list, and Iâm sure there are a bunch more that Iâm forgetting.
On the topic of a GPU cluster, the optimal design is going to depend a lot on what workloads you intend to run on it. The weakest link in these things is the data transfer rate, but that wonât matter too much for compute-heavy workloads. If your workloads are going to involve a lot of data, though, youâd be better off with a smaller number of high-VRAM cards than with a larger number of interconnected cards. I guess thatâs hardware engineering 101 stuff, but stillâŠ
yarnd, tt, jenny, twtr and other clients? đ€ Thinking about (and talking with @xuu on IRC) about the possibility of rewriting a completely new spec (no extensions). Proposed name yarn.txt or "Yarn". Compatibility would remain with Twtxt in the sense that we wouldn't break anything per se, but we'd divorce ourselves from Twtxt and be free to improve based on the needs of the community and not the ideals of those that don't use, contribute in the first place or fixate on nostalgia (which doesn't really help anyone).
@prologic@twtxt.net I would politely suggest again that we not react to people with bad attitudes who talk shit about yarn. If twt is forked, it should be forked to add features that are otherwise not possible. Not to appease people who will probably never be appeased.
đ Q: How do we feel about forking the Twtxt spec into what we love and use today in Yarn.social in yarnd, tt, jenny, twtr and other clients? đ€ Thinking about (and talking with @xuu@txt.sour.is on IRC) about the possibility of rewriting a completely new spec (no extensions). Proposed name yarn.txt or âYarnâ. Compatibility would remain with Twtxt in the sense that we wouldnât break anything per se, but weâd divorce ourselves from Twtxt and be free to improve based on the needs of the community and not the ideals of those that donât use, contribute in the first place or fixate on nostalgia (which doesnât really help anyone).
We could ask them? But on the counter would bukket or jan6 follow the pure twtxt feeds? Probably not either way⊠We could use content negotiation as well. text/plain for basic and text/yarn for enhanced.
An option would be to have /twtxt.txt be the base functionality as bukket intended without subject tags, markdown, images and such truncated to 140 chars. a /yarn.txt that has all the extentions as we know and love. and maybe a /.well-known/webfinger + (TBD endpoint) that adds on the crypto enhancements that further extend things.
@darch@neotxt.dk I think having a way to layer on features so those who can support/desire them can. It would be best for the community to be able to layer on (or off) the features.
@movq@www.uninformativ.de Cheers! Iâm happy to agree to disagree too of course! Thanks for engaging!
@xuu@txt.sour.is That has no relevance to the point!
@abucci@anthony.buc.ci that is an ironic example. Since the inventor of the seatbelt gave rights to use the technology freely.
@logout@i-logout.cz well done on 1337 days of gopher server uptime
go mills() đ
@chunkimo@twtxt.net lol. go walrus!!
@prologic@twtxt.net I always liked bit.
I am disappointed that a GUI app would not at least have screenshots.
@kindrobot@tilde.town Iâm totally joining it
@prologic@twtxt.net it is from the generator. But in the actual go implementation methods are represented with a unsigned short. So 65k is the hard limit in go.
@eldersnake@we.loveprivacy.club apparently someone that generates graphql endpoints for a biiiig app
@prologic@twtxt.net @prologic@twtxt.net this description is applicable. As with PH.D so with this hyper focus.

Cada vez que veo proyectos donde hay algĂșn reto en el âonboardingâ de autenticaciĂłn, recuerdo que implementĂ© una prueba de concepto en https://eapl.mx/twtxt/
Y me dan ganas de ver que tanto podrĂamos pasarlo a producciĂłn con algĂșn proyecto pĂșblico
Cada vez que utilizo los 2FA/TOTP recuerdo que este twt se alimenta con la pĂĄgina que fue una prueba para WebAuthn. Me sorprende que sigue sin usarse como una forma masiva de password-less auth.
Si quieres probar la implementaciĂłn acĂĄ: https://eapl.mx/twtxt
@prologic@twtxt.net I get the worry of privacy. But I think there is some value in the data being collected. Do I think that Russ is up there scheming new ways to discover what packages you use in internal projects for targeting ads?? Probably not.
Go has always been driven by usage data. Look at modules. There was need for having repeatable builds so various package tool chains were made and evolved into what we have today. Generics took time and seeing pain points where they would provide value. They werenât done just so it could be checked off on a box of features. Some languages seem to do that to the extreme.
Whenever changes are made to the language there are extensive searches across public modules for where the change might cause issues or could be improved with the change. The fs embed and strings.Cut come to mind.
I think its good that the language maintainers are using what metrics they have to guide where to focus time and energy. Some of the other languages could use it. So time and effort isnât wasted in maintaining something that has little impact.
The economics of the âspyingâ are to improve the product and ecosystem. Is it âspyingâ when a municipality uses water usage metrics in neighborhoods to forecast need of new water projects? Or is it to discover your shower habits for nefarious reasons?
@prologic@twtxt.net short version: context is a linked list that is passed down a call stack that can share timeout, cancellation, or other data as needed by lower functions in the call stack.
@prologic@twtxt.net the rm -rf is basically what go clean -modcache does.
I think you can use another form that will remove just the deps for a specific module. go clean -r
@pbatch@pbat.ch not sure youâre reading this, how come youâre ditching twtxt?
@prologic@twtxt.net aha, a hater! Just the kind I was looking for some serious business that requires some fervent hating. Pay is good, you up to? :-D :-P
interesting that in my pod this is showing in reply to something.. but in the twtxt is has no subject.

@prologic@twtxt.net The parse is correct. this seems to be something with the markdown render.
@abucci@anthony.buc.ci Where did I hate on SQL databases? đ€
@prologic@twtxt.net boo, boo, boooooo! :-D :-P
@lyse@lyse.isobeef.org flawed is the right word, no harsh at all. Good reading, and thanks for supporting the possibility of convincing @prologic@twtxt.net to switch to a database! :-D :-P
@eldersnake@we.loveprivacy.club Several reasons:
- Itâs another language to learn (SQL)
- It adds another dependency to your system
- Itâs another failure mode (database blows up, scheme changes, indexs, etc)
- It increases security problems (now you have to worry about being SQL-safe)
And most of all, in my experience, it doesnât actually solve any problems that a good key/value store can solve with good indexes and good data structures. Iâm just no longer a fan, I used to use MySQL, SQLite, etc back in the day, these days, nope I wouldnât even go anywhere near a database (for my own projects) if I can help it â Itâs just another thing that can fail, another operational overhead.
@bender@twtxt.net You mean @eaplmx@twtxt.netâs reply didnât show up in your mentions? đ€
@prologic@twtxt.net I am not seeing some of my previous interactions. This one is an example: https://twtxt.net/conv/svvpd3a
pass on my machine:
@abucci@anthony.buc.ci So.. The issue is that its showing the password by default? Would making an alias to always include the -c help? We can probably engage Jason with a PR to enable a more hardened approach when desired. Iâve spoken to him before and is generally a pretty open to ideas.
I found this app that was created by the gopass author that does copy by default and has a tui or GUI mode https://github.com/cortex/ripasso
@prologic@twtxt.net @movq@www.uninformativ.de this is the default behavior of pass on my machine:

I add a new password entry named example and then type pass example. The password I chose, âtestâ, is displayed in cleartext. This is very bad default behavior. I donât know about the other clis you both mentioned but Iâll check them out.
The browser plugin browserpass does the same kind of thing, though I have already removed it and Iâm not going to reinstall it to make a movie. Next to each credential thereâs an icon to copy the username to the clipboard, an icon to copy the password to the clipboard, and then an icon to view details, which shows you everything, including the password, in cleartext. The screencap in the Chrome store is out of date; it doesnât show the offending link to show all details, which I know is there because I literally installed it today and played with it.
@mckinley@twtxt.net i use pass along with the android and browser-pass clients. it is very good and keeping in sync is pretty simple.
@mckinley@twtxt.net very weird things going on for me.. i can see your twt but its not showing up as a reply or fork? 
@abucci@anthony.buc.ci i have an old copy of the 2005 version from university if you want to give it a read through. its quite dry.
@xuu@txt.sour.is yeah, I know less about ISO27k (in part because you have to pay for access to the complete standards documents!!!), but I figured it was similar.
!XO!1GcUL/ZbHj+CZnedB67ddd0tt3y1ppSLY7wbzMhraUeubCUH8LRT61pz6jPyOEa2wYYupwP7tu1cwR9mNN/k+No7PEw13kqBy6YvDU8jettw25Lkj3gZ+R4J1q6d0GWKKGx+OsYmJMPev7BL+5SCnt08qQYmgGAVhyhJZMkndIgk=!OX!
@prologic@twtxt.net yap. This was an offer message to you. rachet-over-yarn mode enabled!
@prologic@twtxt.net vultr pricing is low. But it can be lower if you shop the less fancy admin ui sites like virmarch or ovh. There are some bare metal that cost way less.. Though the experience is less than optimal.
@abucci@anthony.buc.ci ISO 27001 is basically the same. It means that there is management sign off for a process to improve security is in place. Not that the system is secure. And ITIL is that managment signs off that problems and incidents should have processes defined.
Though its a good mess of words you can throw around while saying âmanagement supports this so X needs to get doneâ
@prologic@twtxt.net !XO!1GcUL/ZbHj+CZnedB67ddd0tt3y1ppSLY7wbzMhraUeubCUH8LRT61pz6jPyOEa2wYYupwP7tu1cwR9mNN/k+No7PEw13kqBy6YvDU8jettw25Lkj3gZ+R4J1q6d0GWKKGx+OsYmJMPev7BL+5SCnt08qQYmgGAVhyhJZMkndIgk=!OX!
