TheVillageGuy
TheVillageGuy
C: is the system drive and only SSD here as well, and the error only occurs on this drive.
It would seem the problem has been solved with the latest updates from MS.
It came back here as well. I have done a clean windows install and the problem remains. On Thu, 16 Apr 2020, 13:36 TheEqualizer, wrote: > I am still having...
It's a bug, this allows for eavesdropping On Thu, 14 Mar 2024, 19:45 e-five, ***@***.***> wrote: > Do you think this is a bug or a feature? Not to say...
Well, in real life if people mention me and everybody who shares my name (there's a lot of them) would be able to listen in without it being their business...
I see. This is a fediverse wide issue I assume? I'm going to give it some more thought, I am not sure what to think of it. On Sun, 17...
Still a feature I'd appreciate On Fri, 8 Mar 2024, 03:05 github-actions[bot], ***@***.***> wrote: > This issue is stale because it has been open 50 days with no activity. >...
This is still the case
Um, looks pretty serious, I was doing some interaction, tried replying and then after three attempts got this ```'\n \nAdd comment\n\n\n \n \n \n \n \n \n \n \n \n...
Can't the timestamp be fixed when it's in the future? Inconsistent yes, but what's the point of having a timestamp from the future. Maybe add a line to the post...