movq @www.uninformativ.de

Follow

Block / Report User

If this user/feed is violating this Pod's (twtxt.net) community guidelines as set out in the Abuse Policy, please report them immediately!

You are also free to Unfollow or Mute this user or feed. Muting will also remove that user/feed's content from your view and you will no longer see content from that user/feed anywhere.

@movq does not follow you (they may not see your replies!)

Recent Twts

Recent twts from movq

I love how my Android phone unironically tells me: “Please restart your device. Your device has not been restarted for 28 days. We e …” (Yes, it ends with “we e …” and I have no idea how to show the full message.) Really? So they haven given up and don’t even try anymore to make software that, well, works?


#jqcatmq

@prologic (#wkjlotq) Oh, the URL part is being dropped? I missed that. It makes a lot of sense to do that, so I’ll make the change in jenny soon. 👌

Right now, jenny sometimes has to make up those URLs, because there simply is no cross-platform way of creating them. URLs like https://twtxt.net/search?tag=gjt7pqa only exist on yarn.social, but there’s no equivalent on my web site … so, yeah, that’s probably where those bad links are coming from.

I guess we should update https://dev.twtxt.net/doc/twtsubjectextension.html accordingly. (Or maybe there’s a PR already, haven’t checked.)


#23h7xtq

@jlj@twt.nfld.uk (#rpg63yq)

Interesting idea. 🤔

This is a key factor:

Such an upcycling will be possible with the manufacturers obligation to publish a device’s underlying source code under a Free Software licence at the end of support for any software necessary to run or modify the initial functioning of the device.

A device’s source code isn’t worth anything if it depends on, say, a proprietary compiler.

A similar loop hole for manufacturers: They could add pointless complexity to their build system. “Sure, here’s the source code for iOS. Have fun building it! You only need to perform these 13 million steps: …”

Or design the build system in such a way that it’s impossible for most people to perform because of their hardware: Just put it enough effort for the build to require 128 GB of RAM and you’re good.


#qxvruwq

(#vbhvpda)

Speaking of Vim: It might be a good idea to write a twtxt syntax highlighting file, which extends the markdown one. 🤔 But then again, the currently used “mail” syntax highlighting is not that bad either, and it get’s nested quoting right:


#gapukea

Experimenting with “replace all newlines by U+2028 when writing twts”.

Foo!
Bar!

  • This is a list.
  • This is another item on the list.

And then she said:

Look, a tree!

It’s not that bad. 🤔 I just have to set my Vim to not do hard line-wrapping in jenny postings (which it does by default for all plain text files). So I now have this in my ~/.vimrc:

au BufRead,BufNewFile jenny-posting.eml call SetForumWrapping()

#vbhvpda

@prologic (#7exlyga)
At first, there was only “reply” in jenny. Then you introduced “fork”, so I added that method. 😁 But there is no default, really. The example mutt config just installs two hotkeys and it’s up to the user which one to press.

I’m not sure which model is better, to be honest. 🤔

btw, jenny does not pre-fill mentions of all the people in the conversation. When you hit “reply” (or “fork”), you only get a mention of the person you’re replying to. I think that’s actually a little bit better, because those “mass-mentions” can get a bit noisy. 🤔 I regularly see mentions of my nick, but the person really was talking to someone else. I just happened to be “in the loop”. (Reminds me a bit of business e-mail. 🤣)


#luxu23a

@quark@ferengi.one (#44nacmq) Not a bug. All lines starting with “> ” are stripped. (This is done to remove the quoted stuff that is initially appended at the bottom when you reply to a twt.) What you’re writing here is not Markdown, it’s just “text”. The only special processing that jenny does now is that multi-paragraph thingy. (This is in contrast with yarn.social, which renders everything as Markdown, I think?)


#74lxfha

@quark@ferengi.one (#juoezea) There was a time (after the Perl era) when everbody built their own web site … in PHP, with MySQL. 🤣 What a mess. The good thing about static web site generators is that they’re harmless. You can’t screw this up. You can’t accidentally introduce SQL injections or make PHP read sensitive files or whatever. I love static web stuff. 👌


#eqcx57q

(#zrg4luq) … hmmm. I can force everything to be UTF-8, that’s not a problem. But that means that your entire software stack must be capable of handling UTF-8 (editor, terminal, …). And at that point why not just require the user to use an UTF-8 locale? 🤔


#7wz6xyq

@quark@ferengi.one (#zrg4luq) Gah, I finally understood what’s going on here. The point is that you were using a non-UTF-8 locale (one with latin1, apparently) – I kept trying to reproduce it with LANG unset or LANG=C, which is different. And that made Python decode strings using latin1, which of course results in garbage. This is clearly a bug, jenny shouldn’t break with non-UTF-8 locales.


#swtynfq

@quark@ferengi.one (#pe5ymoa) Alright, I can’t tell when I’ll be able to do a screen sharing thingy. So let’s try this the old-fashioned way first. Please try to reproduce the issue with the branch quark-trace that I pushed recently. It’ll create a /tmp/jenny.log file (it will get large). When you see duplicate twts, try to find them in that log.

Reasons, in theory, why we could see dups:

1) jenny doesn’t detect your feed’s URL correctly.

2) python-dateutil doesn’t parse your twt’s timestamp correctly. Or rather, it parses it differently depending on some env vars? Cronjobs often have this pitfall where some env var is different than your normal environment.

Actually … I can’t think of anything else. 🤔 You don’t see dups all the time, it only happens for your own twts, and you said that the twt hash mismatches. That already narrows it down to something in make_twt_hash(). 🤔

Let’s see if that trace file helps. If it doesn’t, we can add more trace() calls.


#dr2jfzq