Timeline for Now live: A fully responsive profile
Current License: CC BY-SA 4.0
22 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 3, 2021 at 15:27 | comment | added | Makoto | @AaronShekey: I'm just getting a wicked sense of deja-vu, that's all. But I think I've said enough about this. While I'm not satisfied with this compromise, this is all I'm going to get. | |
| Nov 3, 2021 at 14:13 | comment | added | Aaron Shekey StaffMod | @TylerH Mods can see what you see when you view your own profile. We discussed putting things behind rep and potential preferences, but this is the cheapest way to make the profile a bit safer, beyond the cheapest solution, which was to remove it altogether. | |
| Nov 3, 2021 at 14:11 | comment | added | Aaron Shekey StaffMod | @Makoto The thing that's tricky from the outside is understanding that the profile has seen little to no investment over the years. No one quite "owns" that part of the site. My team has the mandate to make things responsive. While we're there, we can do things that have often been discussed, but weren't justified because of this lack of ownership/governance. I believe we're leaving the profile a more responsive, safer place. | |
| Nov 3, 2021 at 13:46 | comment | added | TylerH | @AaronShekey 1) Do mods still see the original granularity of seconds/is that still exposed via the API? 2) It would be nice if we could at least see down to the day. Hell, hide it behind a 10k privilege to massively reduce the surface area for that theoretical risk for abuse. The ability to know a user has been on the site is really useful when trying to engage with people at an individual question level. We can sort of approximate this in the positive by checking "recent activity" (if there has been some, we know they've been active), but obviously isn't possible in the negative. | |
| Nov 3, 2021 at 4:10 | comment | added | Makoto | @AaronShekey: Okay, I suppose then if this were explained or communicated to us in a way that didn't bundle it into a feature like this, I could've supported the rationale. In that framework, we could've had a conversation on what granularity makes the most sense with the people that use it for non-abusive reasons. But I get the distinct impression that we're either stuck with this compromise or nothing at all. | |
| Nov 3, 2021 at 1:54 | comment | added | Ekadh Singh | @AaronShekey out of curiosity, is the “last seen” method calculated the same way still, or is it calculated differently? | |
| Nov 3, 2021 at 1:53 | comment | added | Aaron Shekey StaffMod |
Last seen, in its original granularity of seconds, is a potential vector for abuse. When discussing with our trust & safety team, we determined that knowing someone used the site within a week is plenty of granularity and should satisfy existing use cases. Now, public users can see if the user has participated this week, more than a week ago, more than a month ago, and more than x years ago.
|
|
| Nov 2, 2021 at 20:59 | comment | added | Kevin B | It would be nice for a post to exist that actually explained the way it is rather than having to figure it out | |
| Nov 2, 2021 at 20:58 | comment | added | Makoto | @KevinB: I found one too. That took some digging. Well...that's still less than useful in my case anyway... | |
| Nov 2, 2021 at 20:56 | comment | added | Kevin B | I just found a "last seen more than 2 years ago" | |
| Nov 2, 2021 at 20:55 | comment | added | Makoto | @KevinB: The furthest it goes back is "more than a month". For my use case, that's as granular as I can get. Even if they did add one more order of magnitude (maybe two), it still doesn't explain why that decision was made or what it had to do with making the profile responsive in the first place. | |
| Nov 2, 2021 at 20:43 | comment | added | Kevin B | I don't disagree with you at all, this pattern has been repeating for years (Overcorrect, then 6-8 arbitrary units later half-revert)... I more wanted to point out that it's per week, not month as you stated. I'd certainly prefer what we had, or at least reasoning for why it needed to change that goes into more detail than "privacy", but also... as i said, it does at least resolve the issue for me, personally, ;) | |
| Nov 2, 2021 at 20:39 | comment | added | Makoto | @KevinB: It breaks the small-site use case entirely. It also defies the sentiment of what I hoped was the outcome; either a reversion of the change or a firm decision on why they went the way they did. I'm really not trying to be a jerk about this. I'm hoping that I'm sounding level-headed about this whole thing, but I vehemently hate this pattern of breaking things within the community and then offering an olive branch in the form of something we didn't ask for as a "compromise". That doesn't feel like a "community" engagement to me. | |
| Nov 2, 2021 at 20:33 | comment | added | Kevin B | @Makoto i see "this week" for both me and you. good enough for what i use it for, | |
| Nov 2, 2021 at 20:15 | comment | added | Makoto | @AaronShekey: And the rationale for reducing the granularity to a month was...? | |
| Nov 2, 2021 at 19:55 | comment | added | Aaron Shekey StaffMod | We’ve restored "last seen" to all users, but with less granularity. | |
| Nov 2, 2021 at 19:54 | history | edited | Aaron ShekeyStaffMod | CC BY-SA 4.0 |
added 3 characters in body
|
| Oct 26, 2021 at 17:39 | history | edited | Aaron ShekeyStaffMod | CC BY-SA 4.0 |
added 25 characters in body
|
| Oct 25, 2021 at 13:46 | comment | added | jrh | I'm generally against duplicate answers and retreading old ground, but this isn't one of those cases. I think it's good to repeatedly keep poking this. It can't be a real privacy concern if it's still available to the API and still stored in SE's databases under user ID. | |
| Oct 22, 2021 at 19:39 | comment | added | Makoto | @EkadhSingh-ReinstateMonica: Measured and restrained impatience on my part, while explicitly stating two desired outcomes? :D Probably isn't different, to be honest. | |
| Oct 22, 2021 at 19:33 | comment | added | Ekadh Singh | How is this different from this? | |
| Oct 22, 2021 at 19:32 | history | answered | Makoto | CC BY-SA 4.0 |