I noticed this about a year ago, but I recently saw it again and wanted to look into it more.
Theres an old Roblox account made in 2010 (which I remember having never been active from before roblox stopped tracking last activity) called “imleavingforever”. They appeared in my audit log editing a place I made for a game called “i hate roblox” (lol).
I’d normally write this off as some old admin account thats still being used as a moderation bot (and I’m still assuming thats what it is) but I found the username eerie and odd, especially considering that I follow them on my main account, but when I view their profile it says they follow one person (assuming builderman?) and 10 follow them. It doesnt let you view any of their friends/following/follower lists, and when I view their profile in a browser with no 3rd party roblox extentions it shows 0 followers/following.
Has anyone else seen similar ghost/abandoned accounts show up in their group audit logs before? Just need to know if this is anything I should care about.
Yeah I have, I made a support ticket about it around a year ago, it was a random account that looked similar to that of your one, appeared in my audits, I reported the account. Roblox’s response to my ticket was something to do with clearing your browser cache or something, I think it worked. It’s very weird though, it can’t be a problem on our end if it’s to do with accounts…
Anyhow, I haven’t dealt with the issue for quite some time now so…
That’s just do with regulation in some countries (for example, the UK). For accounts from these countries, you can’t view the friends, followers, followings, and a few other things about the user.
Very likely a moderation account of some sorts, maybe for some random automated action which is quite likely considering the TOS was updated on the day those logs were made or close to it (October 19th 2022) as why you are following it, you mightve just followed it when you saw it at first.
I wouldnt think too much about it, i have had a random account like this but it was clearly an internal account (being called test account or something like that)
Sorry to ruin the fun, but this is simply a re-occuring bug with the website treating a group ID as a user ID, and that ID coinciding with a valid user (using the same id of the account but under /communities/:groupId/ gives your group)
