i really like this idea, and i can't believe it doesnt exist.
it sounds like it did exist, but for some technical reason it was removed.. it could be something very innocuous like the code was terrible, and needed a rewrite, or a library was used that needed to no longer be used and it has not yet been replaced.
i agree, i think your argument is 'why arent my own posts automatically liked by me'
call me a pedant but it hurts me to hear a category labeled hot, that has not had literally any user related activity. those 2 things are incompatible. just swap hot for new and call it day
hot to me is an 'activity over time' metric, and zero doesnt play nice
if its a chore you shouldnt be doing it. it should be fun!
for me its a bursting outlet for my nonsense.. not reeallly considering the audience when im creating stuff. i just need to get it out of my brain before it burns a hole.
ive also been surprised by some of the easiest stuff garnering the most attention.
alllllsoo.. ive noticed in the verse this kinda of delayed reaction. ive gotten posts that suddenly gain attention months later as the fediverse does its thing, and the content gets refreshed out there..somewhere.
your thought process isnt completely off. if my server product was detecting the failures correctly, these resources wouldnt pile up.
i dont think people really understand just how brand new all this stuff is. 'the fediverse' is under active development. they call it the 'bleed edge' of technology because its painful. most fediverse servers are experiencing growing pains of some sort.
the Lemmy/kbin sides are still wet behind the ears. i just hope people dont give up!
the lemmy changes are causing excessive resource use on my 'bin instance. so yeah, not using lemmy, but being directly affected by the lemmy snafu.
my failed messaging queue is filling, which has its own retry logic.. that queue buildup also takes disk space.... extra processing, extra disk space.. this leads to 'worker' slowdown and then system failures and timeouts.
the lemmy changes are causing excessive resource use on my 'bin instance. so yeah, not using lemmy, but being directly affected by the lemmy snafu.
my failed messaging queue is filling, which has its own retry logic.. that queue buildup also takes disk space.... extra processing, extra disk space.. this leads to 'worker' slowdown and then system failures and timeouts.
there is indeed something weird going on with lemmy. i noticed some feeds from lemm.ee are down, and the logs from my instance are filling up with bot rejections from lemmy.world, ie they are blocking bot traffic. i thought i read something about the new version of lemmy breaking some inter-lemmy fed traffic.
the error messages piling up are bad for my 'bin instance due to the retry methods used... extra processing, disk space starts to fill up.. resources just start piling up so i'm having to manually dump things regularly for the last 24-36 hours.
feasible kbin.social is also having some of the same problems i am
whatever. i hate facebook, i dont use their crap. but im not going out of my way to block their AP protocol any more than i would their SMTP protocol.
when their activity in a specific context demonstrably, negatively affects my system, ill take action as i would any negative impact from any protocol on any of my services.
when i get a spammer, i block them. but again, im not going out of my way to spite some big asshole company, and potentially lose out on coordinating an offramp for those trapped in its walls.
everyone here as proven one thing: there is no technical reason to block threads. its entirely political/moral/spite and a lot of 'maybes'.
this is just not true, sorry. instances only retrieve/pushed specified actions/actors. . pretending it is is ridiculous. this is now a new unknown, this is how the ap protocol works.
and your shit is already public, if they want to suck it all in there is literally nothing stopping them right now. federation or not.