lyse @lyse.isobeef.org

Follow

Block / Report User

If this user/feed is violating this Pod's (VltraPlus) 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.

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

Recent Twts

Recent twts from lyse

(#fj6gwxq) Like @prologic@twtxt.net, I can’t give you any hints, @eaplmx@twtxt.net. Sorry. For me, a hobby project just has to be fun in some way. But I know this too well myself, over time interest is lost and thus the project never finished. But I reckon that’s fine, too. Because there was a time where I had fun and/or learned something. However, I fully agree that it doesn’t feel good to not have completed the project.


#w4bslfa

(#7ldrcdq) @eaplmx@twtxt.net You’re spot on. Making everything configurable opens a whole sea container of worms. You convinced me to make it as simple as possible. Haha, no, I do not have paying users, in fact it’s just me. Maybe up to three other mates in the future. It’s just a hobby project, so there won’t be anybody paying anything. And that’s perfectly fine for me as nobody can force me to do something. :-)

I’ll go with two predefined exercise types, that’s all that I need at the moment. Yeah, keeping extensability in mind is very important. Thank you very much for all your valuable input!

Our approaches differ in measurements, I don’t care about calories, although, that is most likely by far the best meaningful number. It’s just not something I’m interested in and I also don’t have any way to measure it. In that regard I’m like a child and want to play with counting exercises. ;-)


#ir74bza

(#7ldrcdq) @eaplmx@twtxt.net The big question is: How to deal with different sorts of exercises. Like situps and pushups require a counter, but a bike ride or hike do not. They require a distance, a route and what not. Should I go full overboard and make the exercise types completely user-configurable? Or should I just offer two different things built in with the option to expand later on in the code if necessary? Two fundamentally different solutions.


#2il6aaq

(#a32ofka) @prologic@twtxt.net Everything will be done with good old plain form requests. The only thing where JS was involved was the map of course. I think for the weight graph a mate used the <canvas> or something like that, so JS was required, too. Unfortunately. For the “Enter Exercise” form JS helped to disable the free text input field when another exercise was selected. But it also worked flawlessly with JS disabled. Or was there some CSS trickery going on? Can’t remember. Can’t remember. Would need to look into the code.

The key is to have everything working without JS. JS might only be used to add little UX benefits. But it must remain working without JS, too. That’s my fundamental rule for over a decade now.

Yes, UI and REST API are two very different things. I started with the REST API to have something very simple and functional. It’s much easier to test and I can simply have a shell script to interact with.


#aoatoja

(#zrbqxza) @abucci@anthony.buc.ci @movq@www.uninformativ.de Oh, interesting. Then I take back my critique this time. I wasn’t aware of that 1024 byte limit either. Working now. I just send it always in the Content-Type header and sometimes even omit it from the HTML altogether. But when I do, I also use the shorter and more reasonable looking HTML5 style <meta charset="UTF-8">, just like @eaplmx@twtxt.net showed. The advantage with the HTTP response header is that I just tell nginx to do it for me, so I cannot forget it in the HTML by accident. Well, in case I forgot, it’s not an issue.

But specifying it also in the HTML helps everybody who happens to download the page. Opening it locally then obviously cannot make use of the nonexisting HTTP response header. Not that I think there are a lot of people out there downloading it, but just in case. :-)

Do you happen to have all your browsers set to fall back to UTF-8 if they can’t detect the encoding, @abucci@anthony.buc.ci?


#mli63wa

(#dmkicsa) @movq@www.uninformativ.de Wait, what?! A year has already passed again? No way! Even better, it caught me by surprise, no more waiting. :-) This is an extremely lovely project, mate! Again, just like last time, suddenly: autum. Bam. Out of nowhere. Basically the same with spring, leaves are everywhere after the blink with an eye. But autum with the drop of the leaves is much more extreme. I kind of miss the orangy season, though. I had the impression it lasted longer last time. Not by much, just a little bit longer.

As predicted, I did not saw the accident where you had to re-setup the camera. I tried to spot it, no chance. Very well done!

I’m also loving your new ideas. Go for it!


#vyzga4a

We barly survived the trip outside. It was and still is just awful hot out there without any wind. Standing air. Luckily we were walking quite fast, so we had a wee bit of airflow. The sun has set for over three quarters of an hour and the thermometer still reads 27°C.

Besides this slow worm and a second, much shorter one later on, a larger frog jumped across the path in the dark. Later a mouse or something along those lines rapidly switched sides and ran over the path. Both just half a meter in front of us, quite cool. Also seen two deer.


#uxffcca

(#c2eqblq) So my local newspaper did the job for me. An article claims that in July there were 25 days with over 25°C and eight days with over 30°C in our county. On Monday two towns further up experienced 50 liters of rain per square meter in just half an hour. It’s roughly half of what a whole August will see. Their fire brigade had something to do! Luckily, lots of basements drained themselves. Also quite a lot of hail came down, partly stacked up 20 cm high. Holy fuck! O_o


#brtqizq

(#envp4vq) @prologic@twtxt.net I’d probably go with gettext here. That’s what I know and also seems to work quite well. Once I come to the web UI part. At the moment I started out with a REST API only.

We’re using Badger at work and unfortunately it’s the wrong database for us. Badger is well suited for high write workloads but we’re mostly only reading. It’s constantly reorganizing the database and wasting a lot of resources. Currently, we’re trying to understand the details to reconfigure it, but we could not achieve a lot so far. Tomorrow, I have to continue research on that topic. :-( Also with all the other trouble it had caused us so far, I’ll not use Badger in my hobby projects. We also noticed ristretto, the cache, somehow accesses /etc/passwd. No reaction from the developers. Development stalled and then lately continued in a new fork by the same guys but it’s already discontinued for another fork and a lot of stuff they don’t need anymore like vlogs, write transactions, etc. have been removed. A lot of stuff is changing at the moment.

Bolt is a candidate we even did a crude storage implementation with. The idle performance is great, basically zero, but when work has to happen, we obviously don’t hit as good numbers as with Badger. Still good enough from what we’ve seen so far without spending time analyzing it in any detail. We would also have to bolt the data encryption to Bolt ourselves. That’s where Badger really shines. But if you en-/decrypt data in the application, you’re still be able to get some metadata from Bolt, like how many records are there, how big are they etc. From my understanding Badger encrypts the whole database and derives dedicated encryption keys from the master key which are then even rotated automatically.

So Bolt could be something to try. I’ll probably also have a deeper look into Bitcask some day this week. However, with these more “esoteric” databases debugging probably gets harder. For well-hung, more traditional solutions like SQLite etc. there are lots of viewers and tools out there. Not sure if that is the case for the others, too.

Ok, I have to check out IndieAuth. Actually, I have no idea about it.


#6iaplaa

(#goes62q) @movq@www.uninformativ.de It works, thanks! I reckon Ctrl+S Ctrl+U didn’t do anything last time because it was already at the end and the command is named completely wrong in my opinion. It’s doing exactly the opposite than what I expect from this name. set_unread actually marks it read but the name suggests the exact opposite, in particular to mark the buffer unread. So I thought the line is then moved up to some previous location or even removed completely. It’s doing exactly what I want, still confused by the name. Thanks again! <3


#gsm7ykq

(#c2eqblq) @movq@www.uninformativ.de I should do the same. But I already missed a lot of 30+°C days this year. I reckon one could dig up these data if one really wants to. They should be publicly accessible, but I fear they’re quite well hidden somewhere.

I also thought a couple of times in my life to operate a small hobby weather station. In elementary school I actually started recording plenty of metrological data. But after a couple of days I lost interest. That happened a couple of times. Nowadays a lot of things could probably be automated with little maintenance. No idea.


#ccv5gcq

(#kkj2c7q) @movq@www.uninformativ.de I read the source code to discover the -o flag and then saw there’s the README-tools.md and finally noticed you even linked it.

They claim the database is free of charge, but I would have to register an account and accept some terms. I try to avoid creating accounts in the first place if possible. Luckily, I don’t need that DB. :-)


#rgrp5pq

(#c2eqblq) Außer Spesen nix gewesen. Well, it rained a tiny little bit, but really not a lot, I hoped for much more. Thunderstorm went by eventless. Even the wind speed was pretty low. Basically it dropped again after I sent the initial twt. Now it’s raining again. Until around midnight they forecast. The light pelting is super calming and relaxing in combination with old Dire Strait songs.

However, temperatures are supposed to rise, up to 36°C on Thursday. Örks.


#a3yjwcq

Still two unresolved issues with WeeChat:

  1. How can I mark the current buffer as read? There is /input set_unread to mark it as unread (although I can’t tell that it does actually anything in the TUI) but there’s no set_read command that would put my read marker below the last message. Sure I can switch buffers and then the read marker is at the bottom, but this sounds like a silly workaround. There must be something better.
  2. I want the beep trigger to also fire when a regular message is sent. But the adjusted condition ${tg_displayed} && ${tg_tags} !!- ,notify_none, with the && (${tg_highlight} || ${tg_msg_pv}) removed then also includes joins and parts, which I don’t want to be alerted by. Now fiddling around with ${tg_message_nocolor} !~ ^(-->|<--), let’s see.

How do you folks do that?


#goes62q

(#zxvfzja) @movq@www.uninformativ.de Yeah, it’s also a bit of a chicken egg problem. If you have unqualified people, they can’t do a lot of stuff but they have to do something, so then they’re shunt off to support. And there they can’t really improve because they’re always overloaded. And not getting any respect they deserve also doesn’t help their motivation, so the downwards spiral continues. There’s more to it, but in my opinion that’s one key factor.


#5e6cqxq

(#s7zkyba) @prologic@twtxt.net Well, I have to confess that whenever a Stack Overflow post pops up in the search results of my least mistrusted search engine the answer(s) there are spot on and exactly what I’m looking for most of the time. Of course there are the occasional exception, but I’m actually very happy with what I dig up there. Sometimes I need to scroll through a few answes to get what I need, but in general the first answer appearing below the question is fairly good. There are super bad answers, no doubt. But you can tell them apart immediately and just skip them right away.


#cglqucq