Short form content - waves, snaps, threads is not included, as that is considered a reply to the overarching post container that is rendered by the respective front end. I'm interested in long form content :)
There is no good or "bad", just "easy to understand", or "difficult to understand" - but that depends on the reader's educational level.
The formula used here is one that has existed for a very long time to analyse how easy it is to read text.
People write however they write, and the score is just derived from sentence length, structure, and the number of syllables in words.
And on a personal note: Many thanks for your recent support of my witness, I hope it was this tool that helped you with that decision!
It includes short form post to D.Buzz
I will need to filter that out. Do you have an example (ie, an account) so I can put that on my list? I think the /app in the API return should enable me to filter that out, but I want to double check with an existing, known post. Please gimme a link and I'll add it to my tomorrow list. About to watch the Formula 1 qualifying , then go to bed after :)
Here's a link to one...
https://peakd.com/hive-193084/@oldsoulnewb/gk0ix6ebitv1o9y4gfbjaf
Here's a link to one on the D.Buzz frontend...
https://d.buzz/@oldsoulnewb/4l5u0n8sco10w372rd1ukp
I did some further testing, I think I have resolved the issue with the release I put out before I went to bed last night. Just catching up on all the comments now.
i realized some interesting stats - major long break and that my frequency posting was declining and in 2025 picked up a bit.
Also last 100 posts readability was nothing for elementary at all while before it was more - i might write more basic it seems :-).
One catch was that one here - a post that seems to be hardly readable / complex (grade 35) while the post was pretty short and easy but full of many links/tags :-):
https://peakd.com/@uwelang/dance-sounds-from-scandinavia
Yes - maybe not the tool only - I was not aware you are running a witness at all before :-)
I am working on fixing this by excluding markdown and html syntax from posts. I think those users who have long signatures with lots of these present will be pushed to "professional" on the basis of the existing logic.
I am working a few other bits and pieces, new version will be deployed to github link soon.
I think my witness is only about three weeks old. I am hoping I get full-time work soon so I can buy a mini-pc so I have a backup node on site (and another one off site) at the home of another hive witness in my city who also runs a witness, and then he can have a backup node at my house as well.
good luck - I am also searching for a new job, pretty difficult these days here - 5 years ago you 20 to apply for that one job, now it seems you have 1000 that want the same one :-)
The local job boards publish those numbers now, its a bit demoralising. I am looking for something that is going to be the right fit for me, as I think we have discussed before. Since April, my application volume has only been about ~40 roles, but I have had about 6 interviews in that time, then been ghosted :P
(A hard no from 2 of them)
being ghosted is one issue - most annoying to get always the same AI answer where you can see no one ever reads that application at all (one case was hard as it was a total 100% fit) - but that is life right now
Same experience down here. It sucks, but my life force sustains me :)
In my last post I include some code enclosed in
<backticks>as actual text. I thought to point out that it may not be always best to exclude code, as some posts discuss coding and may use backticks or other mechanisms to display it as text rather than execute it.The filtering is searching for stuff that begins with http and image or video extensions - and other common markdown. It will still look inside of code blocks.The Flesch Kincaid level of code vs non code, I do not want to consider! (But it would be an interesting linguistics exercise)