@prologic@twtxt.net Itâs called âcgodâ and it isnât written in C or Go? I want my money backâŠ
I also like Gopher more than Gemini. The problem Gemini is trying to solve is better solved by just writing static HTML 4.01 pages.
TenĂa un rato sin escribir acĂĄ en el Log/twtxt
Ha sido una semana un poco extraña aunque empieza a verse que irå todo mejor!
TenĂa un rato sin escribir acĂĄ en el Log/twtxt
Ha sido una semana un poco extraña aunque empieza a verse que irå todo mejor!
Bueno, siento que este twtxt ha sido como un micro-journaling para pensamientos personales, aunque quizĂĄs te guste o inspire algo de lo que cuento por acĂĄ.
Este pensamiento me vino inspirado por https://josias.dev/posts/justwrite/
@lyse@lyse.isobeef.org, fixed. đ
Last-Modified header for your feed, so the official twtxt client complains not to cache it. I just fixed that, so that tt shows your feed (of course no progress has been made in the meantime). And the Date header of your server seems to be quite funny, too. ;-)
@lyse@lyse.isobeef.org, hey, thank you! :-) Yeah, I am abusing the headers on ferengi.one, sorry about that. Will change it. You know, because Lyse.
yarns will get reused directly into yarnd, except that I'll use the bluge indexer instead.
@prologic@twtxt.net, search for âquarkâ and you will get quack, quart, quirk, and all possible iterations. Not too helpful.
@movq@www.uninformativ.de, well, yes, that has always been the case. Not just on jenny, but on Yarn. I canât follow everything, and everyone. To see whether is a reply, a simple h on mutt shows the headers, and there you have it. That is not too convoluted, is it? I mean, if you really want to knowâbut why?âit is a simple key press. If I donât see a context on something as obvious as the example you used, it is simply a reply to someone I donât follow, and pretty much ignore. End of story. đ
Welcome back, @quark@ferengi.one! Your web server doesnât send back a Last-Modified header for your feed, so the official twtxt client complains not to cache it. I just fixed that, so that tt shows your feed (of course no progress has been made in the meantime). And the Date header of your server seems to be quite funny, too. ;-)
@prologic@twtxt.net, business is slow (I also just got off that hyoo-mĂ€n illness that is going around named COVID), so that leaves me some free time on my entrepreneurial hands. đ I have always lurked every couple of weeks or so. I see yarn has regressed on the UI! đŹđ©
@quark@ferengi.one Hey đ Nice to see you around again đ€
@movq@www.uninformativ.de, any plans still to clean up the hash from the twtxtâs body? Maybe a Festivus gift? You know, âfor the rest of usâ. :-D
đŁ NEW: Announcing the new and improved Yarns search engine and crawler! search.twtxt.net â Example search for âHello Worldâ Enjoy! đ€ â @darch@neotxt.dk When you have this, this is what we need to work on in terms of improving the UI/UX. As a first step you should probably try to apply the same SimpleCSS to this codebase and go from there. â In the end (didnât happen yet, time/effort) most of the code here in yarns will get reused directly into yarnd, except that Iâll use the bluge indexer instead.
SMTP_PORT to be set (used to default toi 25) ooops đ
Ahora estoy pensando en hacer una versiĂłn como Progressive Web App, aunque ahora este twtxt es mĂĄs como un log. Me gustarĂa ver si desde Web podrĂamos hacer una interfaz mĂĄs social (en el espĂritu de microblogging cĂłmo Twitter)
@prologic@twtxt.net Liberaâs insistence on giving them an e-mail and my real IP address makes me really not want to give them either one. Otherwise, Iâd probably talk in IRC regularly.
@abucci@anthony.buc.ci Do you happen to use Signal btw? đ€ If you do, it would be great if you could join the Yarn.social Signal Group (_at least until we have Group support and better apps for Salty.im đ )
I think Email has been broken on my Pod since some time now since @lyse@lyse.isobeef.org made this commit the default behaviour of the flags/env had changed requiring SMTP_PORT to be set (used to default toi 25) ooops đ
@eaplmx@twtxt.net CSS Battle has a passwordless login, I donât know the implementation but it basically send you and email where you click a link and youâre in.
Bueno, despuĂ©s de algunas horas de estarle entendiendo a WebAuthn, ahora puedes ver una prueba de concepto en https://eapl.mx/twtxt/ (TodavĂa en Alpha, pues no soporta mĂĄs de una Passkey todavĂa)
@xuu@txt.sour.is proof of stake = people with money get more money. It accelerates the wealth inequality problems that are already plaguing us. Crypto has even worse wealth inequality than fiat currency systems, which is 100% predictable.
ÂżCuĂĄl podrĂa ser la forma mĂĄs conveniente de escribir en un archivo de texto plano como twtxt sin entrar a una consola SSH? Estoy pensando en un bot de correo o de Telegram. TambiĂ©n en una pĂĄgina Web simple.
@brasshopper@twtxt.net bitcoin đ€ź thatâs a hard no from me
Got an acknowledgement of our Salty.im funding proposal to NLnet this evening. I look forward to the outcome đ€ #Salty.im
Estoy viendo que si me respondes y no te sigo, no podré ver tu respuesta, måndame un mensaje para empezar a ver tu twtxt!
@eapl.mx@eapl.mx Hola amigo, it seems to work :)
Se me estå ocurriendo hacer una visualización de twtxt.txt en HTML para que sea mås fåcil de observar⊠pensando
Se me estå ocurriendo hacer una visualización de twtxt.txt en HTML para que sea mås fåcil de observar⊠pensando
Desde aquà estaré twiteando en español. Para twitts en inglés me puedes seguir en https://twtxt.net/~eaplmx (o busca ahà el link al .txt)
ÂĄHola mundo de twtxt!
@prologic@twtxt.net what Content-Security-Policy should I have on my web server for salty? the frontend ainât reacting well to my global config lol
evalerror: refused to create a webassembly object because âunsafe-evalâ is not an allowed source of script in the following content security policy directive: âdefault-src âselfââ.
<<
@jason@jasonsanta.xyz Hey Jason! Welcome to the twtxtverse!
@mckinley@twtxt.net really the language authors should have added those to the standard spec by now. That is just obscene.
@abucci@anthony.buc.ci Dependendies suck đ
Too many moving parts đ€Šââïž
@abucci@anthony.buc.ci Its not better than a Cat5e. I have had two versions of the device. The old ones were only 200Mbps i didnât have the MAC issue but its like using an old 10baseT. The newer model can support 1Gbps on each port for a total bandwidth of 2Gbps.. i typically would see 400-500Mbps from my Wifi6 router. I am not sure if it was some type of internal timeout or being confused by switching between different wifi access points and seeing the mac on different sides.
Right now I have my wifi connected directly with a cat6e this gets me just under my providers 1.3G downlink. the only thing faster is plugging in directly.
MoCA is a good option, they have 2.5G models in the same price range as the 1G Powerline models BUT, only if you have the coax in wall already.. which puts you in the same spot if you donât. You are for sure going to have an outlet in every room of the house by code.
Does anyone of you use PGP encrypted mail, or any kind or email encryption? Why? Why not?
looking at my crawlerâs log scrolling on the screen, randomly copying feeds with an interesting-looking name into my browser. what a nice way to discover new things #twtxt
started writing a small crawler to find keywords and mentions, should now be able to see if youâre mentioning me :)) #twtxt #community #coding
@prologic@twtxt.net odd is it maybe a wrong mime type thing? Should be text/calendar. Some http servers can mistakenly mark them application/octet-stream
@movq@www.uninformativ.de the real question is⊠Can it ScreamTracker3?
@lyse@lyse.isobeef.org hah! I cut some out to fit into my pods 4k limit.
Yeah that does studder a bit. To be honest I have no idea what I was thinking there. This excerpt was written a good year ago.
@prologic@twtxt.net I think we could use deltachats new decentralising app format for it: https://delta.chat/en/2022-06-14-webxdcintro
@lyse@lyse.isobeef.org I do wonder how we could build a decentralized way to do this đ€
@prologic@twtxt.net and others, video call tomorrow/tonight?
đ Hello @burglar@txt.sour.is, welcome to txt.sour.is, a Yarn.social Pod! To get started you may want to check out the podâs Discover feed to find users to follow and interact with. To follow new users, use the âš Follow button on their profile page or use the Follow form and enter a Twtxt URL. You may also find other feeds of interest via Feeds. Welcome! đ€
@prologic@twtxt.net correct type parameters. đ
@mckinley@twtxt.net Haha, while composing I was wondering two or three times whether I should throw my thoughts in an HTML page instead. But out of utter laziness I discarded that idea. ÂŻ_(ă)_/ÂŻ
@prologic@twtxt.net Error handling especially in Go is very tricky I think. Even though the idea is simple, itâs fairly hard to actually implement and use in a meaningful way in my opinion. All this error wrapping or the lack of it and checking whether some specific error occurred is a mess. errors.As(âŠ) just doesnât feel natural. errors.Is(âŠ) only just. I mainly avoided it. Yesterday evening I actually researched a bit about that and found this article on errors with Go 1.13. It shed a little bit of light, but I still have a long way to go, I reckon.
We tried several things but havenât found the holy grail. Currently, we have a mix of different styles, but nothing feels really right. And having plenty of different approaches also doesnât help, thatâs right. I agree, error messages often end up getting wrapped way too much with useless information. We havenât found a solution yet. We just noticed that it kind of depends on the exact circumstances, sometimes the caller should add more information, sometimes itâs better if the callee already includes what it was supposed to do.
To experiment and get a feel for yesterdayâs research results I tried myself on the combined log parser and how to signal three different errors. Iâm not happy with it. Any feedback is highly appreciated. The idea is to let the caller check (not implemented yet) whether a specific error occurred. That means I have to define some dedicated errors upfront (ErrInvalidFormat, ErrInvalidStatusCode, ErrInvalidSentBytes) that can be used in the err == ErrInvalidFormat or probably more correct errors.Is(err, ErrInvalidFormat) check at the caller.
All three errors define separate error categories and are created using errors.New(âŠ). But for the invalid status code and invalid sent bytes cases I want to include more detail, the actual invalid number that is. Since these errors are already predefined, I cannot add this dynamic information to them. So I would need to wrap them Ă la fmt.Errorf("invalid sent bytes '%s': %w", sentBytes, ErrInvalidSentBytes"). Yet, the ErrInvalidSentBytes is wrapped and can be asserted later on using errors.Is(err, ErrInvalidSentBytes), but the big problem is that the message is repeated. I donât want that!
Having a Python and Java background, exception hierarchies are a well understood concept Iâm trying to use here. While typing this long message it occurs to me that this is probably the issue here. Anyways, I thought, I just create a ParseError type, that can hold a custom message and some causing error (one of the three ErrInvalid* above). The custom message is then returned at Error() and the wrapped cause will be matched in Is(âŠ). I then just return a ParseError{fmt.Sprintf("invalid sent bytes '%s'", sentBytes), ErrInvalidSentBytes}, but that looks super weird.
I probably need to scrap the âparent errorâ ParseError and make all three âsuberrorsâ three dedicated error types implementing Error() string methods where I create a useful error messages. Then the caller probably could just errors.Is(err, InvalidSentBytesError{}). But creating an instance of the InvalidSentBytesError type only to check for such an error category just does feel wrong to me. However, it might be the way to do this. I donât know. To be tried. Opinions, anyone? Implementing a whole new type is some effort, that I want to avoid.
Alternatively just one ParseError containing an error kind enumeration for InvalidFormat and friends could be used. Also seen that pattern before. But that would then require the much more verbose var parseError ParseError; if errors.As(err, &parseError) && parseError.Kind == InvalidSentBytes { ⊠} or something like that. Far from elegant in my eyes.
@prologic@twtxt.net can Yarn pods be consumers to other yarn pods?
@abucci@anthony.buc.ci I think so. IndieAuth is what Iâm a big fan of. All Yarn pods are IndieAuth providers for example (if there are any concumsers out there, we have to work on a consumer ourselvesâŠ)