Well, I've heard you have plenty of experience with Unit Testing and TDD. Perhaps designing a few tests before refactoring?
I've heard of Snapshot testing, but have never tried it: https://github.com/spatie/phpunit-snapshot-assertions
Also, what kind of refactor are you trying to do?
No, in all seriousness, that's a tough one. Try to figure out the requirements and write tests to cover them. In my experience, if there is no good documention, tests might also be lacking. It goes without saying that you have to understand the code segments first before you can begin to refactor them. Commit even earlier and more often than usual, this will help you bisecting potentially introduced bugs later on. Basically baby steps.
But it also depends on the amount of refactoring required. Maybe just scrap it entirely and start from scratch. This might not be feasible due to e.g. the overall project size, though.
A newsreader without read flags would be totally useless to me. But I also do not subscribe to fire hose feeds, so maybe that's a different story with these. I don't know.
To me, filtering read messages out and only showing new messages is the obvious solution. No need for notifications in my opinion.
There are different approaches with read flags. Personally, I like to explicitly mark messages read or unread. This way, I can think about something and easily come back later to reply. Of course, marking messages read could also happen automatically. All decent mail clients I've used in my life offered even more advanced features, like delayed automatic marking.
All I can say is that I'm super happy with that for years. It works absolutely great for me. The only downside is that I see heaps of new, despite years old messages when a bug causes a feed to be incorrectly updated (https://twtxt.net/twt/tnsuifa). ;-)
Perhaps, since Twitter in 2006 never implemented read flags, every derivative microblogging system never saw that as an expected feature. This is curious because Twitter started with SMS, where on our phones we can mark messages as read or unread.
I think it all comes from the difference between reading an email (directed to you) vs. reading public posts (like a blog or a 'wall,' where you don't mark posts as read). It's not necessary to mark it as 'read', you just jump over it.
Reading microblogging posts in an email program is not common, I think, and I haven't really used it, so I cannot say how it works, and whether it would be better for me or not.
However, I've used Thunderbird as a feed reader, and I understand the advantages when reading blog posts.
About read flags being simple, well... we just had a discussion this morning about how tracking read messages would require a lot of rethinking for clients such as
timeline where no state is stored. Even considering some kind of 'notification of unread messages or mentions' is not expected for those minimalist client, so it's an interesting compromise to think about.
#running #treadmill
#running #treadmill
#running #treadmill
https://tilde.town/~dzwdz/blog/feeds.html
I've polished the CSS style a bit, you can try it here: https://eapl.me/treed/
Screenshot where text in square brackets is duplicated once againJust search for
][ in https://twtxt.net/user/mckinley/twtxt.txt and you'll see.
Aqui fica o pouquíssimo conhecido projecto Brasileiro "dshock", com a música "I Want a Pizza Party":
https://archive.org/details/Dshock-BreathingsWeak/01.Dshock-BreathingsWeak-IWantAPizzaParty.mp3
Aqui fica o pouquíssimo conhecido projecto Brasileiro "dshock", com a música "I Want a Pizza Party":
https://archive.org/details/Dshock-BreathingsWeak/01.Dshock-BreathingsWeak-IWantAPizzaParty.mp3
If it's a problem that ruins your experience, don't hesitate to create an issue.
If it's a problem that ruins your experience, don't hesitate to create an issue.
#running
#running
#running
#catsoftwtxt
/https://duque-terron.cat/media/photos/IMG_3654.jpeg) #catsoftwtxt
#catsoftwtxt
" " instead of "T"
" " instead of "T"
https://git.mills.io/yarnsocial/go-lextwt/pulls/32
https://git.mills.io/yarnsocial/go-lextwt/pulls/32
and the second? i get POST errors when i try to submit the webform.
and the second? i get POST errors when i try to submit the webform.
g
twtxt---profile-layout: Wrong type argument: char-or-string-p, ("https://aelaraji.com/twtxt.txt" "gemini://box.aelaraji.com/twtxt.txt" "gopher://box.aelaraji.com/0/twtxt.txt")
g
twtxt---profile-layout: Wrong type argument: char-or-string-p, ("https://aelaraji.com/twtxt.txt" "gemini://box.aelaraji.com/twtxt.txt" "gopher://box.aelaraji.com/0/twtxt.txt")
User-agent: *
Disallow: /
now i some middleware that looks at the header, and if they are polite enough to include "bot" in the user agent, they politely get a 404 response.
User-agent: *
Disallow: /
now i some middleware that looks at the header, and if they are polite enough to include "bot" in the user agent, they politely get a 404 response.