win0err

kolesnikov.se

I'm a software engineer, photographer, and professional procrastinator.

In-reply-to » @prologic: Reduced refresh interval to 7200 seconds :-)

@prologic@twtxt.net I guess that refresh field could be easily replaced with Expires HTTP header (I realize that users on neocities.org cannot control this header, for example). And clients should also respect headers like Last-Modified/If-Modified-Since (304), you’re right about that. P.S. twtwt doens’t have a caching mechanism for now, but I plan to implement it in generic way using HTTP headers.

⤋ Read More
In-reply-to » I decided to become popular in decentralized social networks. 1. Pixelfed: https://pixelfed.social/win0err — mostly landscape photography; 2. Mastodon: https://mastodon.online/@win0err — software engineering content

@lyse@lyse.isobeef.org: Thank you, it’s really nice to hear that! Sometimes I think I’m a moss, because I really love northern nature :D Pixelfed is very slow indeed, and also buggy. @prologic@twtxt.net: I plan to add an RSS feed for the photography page instead of cross-posting to twtxt.txt. Maybe I should post updates of my website here? For example, I made a fancy New Year’s design of https://kolesnikov.se (which makes @lyse@lyse.isobeef.org’s eyes hurt, haha)

⤋ Read More
In-reply-to » @prologic (re: Just discovered ...) On the one hand, twtxt has become more popular thanks to Yarn.social. On the other hand, subject and hashtag extensions took away the simplicity of the protocol. For example, it is impossible to understand which conversation (#base32hash) a tweet refers to or to reply to a tweet without going to a yarn.social pod. Compare with re: in this tweet which can be written without using any client at all

@prologic@twtxt.net: I understand the benefits of using hashes, it’s much easier to implement client applications (at the expense of ease of use without the proper client). I must say that I like the way the metadata extension is done. Simple and elegant! It’s hard to design simple things!

⤋ Read More

@prologic@twtxt.net On the one hand, twtxt has become more popular thanks to Yarn.social. On the other hand, subject and hashtag extensions took away the simplicity of the protocol. For example, it is impossible to understand which conversation (#base32hash) a tweet refers to or to reply to a tweet without going to a yarn.social pod. Compare with re: in this tweet which can be written without using any client at all

⤋ Read More
In-reply-to » I switched from twtxt client to twtwt (https://github.com/win0err/twtwt). It's a pre-alpha version now, but it works pretty well and so much faster than the official twtxt client by @buckket. Feel free to check it out :-)

@prologic@twtxt.net: Hmm, I just checked, it should work. Anyway, I will post updates about the project. First of all, I want to complete some features and create packages with pre-compiled binaries

⤋ Read More

Thanks for the feedback! This site was designed to look perfect on good old 800x600 monitors (I even left a comment next to the meta tag). Maybe I’ll add a mobile-friendly version someday :-) P.S. Nice try with SQL injection, haha. Do you have any plans for XSS attacks? :D

⤋ Read More