Return to Answer

For the same reasons I lay out here it can't really appear here.

It has none of the aggregation code in place for reputation, "posts", etc. If it did then we'd have to keep it in sync 2 places (things would break everywhere otherwise since it's serialization pain). In the user profile we one-off fetch it in the cache load since that fetches from a similar cache as the site switcher does for rep. However, since the site switcher is included on every page we can't have any delay.

For reputation specifically, we would have to aggregate every reputation change, merge, deletion, etc., clear several caches when that happens, and also mix concepts of what the schema means (Area 51 isn't Q&A, some things don't translate). It adds complexity to the dropdown as well since the links aren't to the same place or format, but that's a different can of worms.

Adding it adds pain, decreases performance, and means a whole set of APIs to keep in sync. Given that we don't know what will happen with Area 51 a year from now, this implementation is not something we want to spend a great deal of time (and continued maintenance) on.

For the same reasons I lay out here it can't really appear here.

It has none of the aggregation code in place for reputation, "posts", etc. If it did then we'd have to keep it in sync 2 places (things would break everywhere otherwise since it's serialization pain). In the user profile we one-off fetch it in the cache load since that fetches from a similar cache as the site switcher does for rep. However, since the site switcher is included on every page we can't have any delay.

For reputation specifically, we would have to aggregate every reputation change, merge, deletion, etc., clear several caches when that happens, and also mix concepts of what the schema means (Area 51 isn't Q&A, some things don't translate). It adds complexity to the dropdown as well since the links aren't to the same place or format, but that's a different can of worms.

Adding it adds pain, decreases performance, and means a whole set of APIs to keep in sync. Given that we don't know what will happen with Area 51 a year from now, this implementation is not something we want to spend a great deal of time (and continued maintenance) on.

For the same reasons I lay out here it can't really appear here.

It has none of the aggregation code in place for repution, "posts", etc. If it did then we'd have to keep it in sync 2 places (things would break everywhere otherwise since it's serialization pain). In the user profile we one-off fetch it in the cache load since that fetches from a similar cache as the site switcher does for rep. However, since the site switcher is included on every page we can't have any delay.

For reputation specifically, we would have to aggregate every rep change, merge, deletion, etc., clear several caches when that happens, and also mix concepts of what the schema means (Area 51 isn't Q&A, some things don't translate). It adds complexity to the dropdown as well since the links aren't to the same place or format, but that's a different can of worms.

Adding it adds pain, decreases performance, and means a whole set of APIs to keep in sync. Given that we don't know what will happen with Area 51 a year from now, this implementation is not something we want to spend a great deal of time (and continued maintenance) on.

For the same reasons I lay out here it can't really appear here.

It has none of the aggregation code in place for reputation, "posts", etc. If it did then we'd have to keep it in sync 2 places (things would break everywhere otherwise since it's serialization pain). In the user profile we one-off fetch it in the cache load since that fetches from a similar cache as the site switcher does for rep. However, since the site switcher is included on every page we can't have any delay.

For reputation specifically, we would have to aggregate every reputation change, merge, deletion, etc., clear several caches when that happens, and also mix concepts of what the schema means (Area 51 isn't Q&A, some things don't translate). It adds complexity to the dropdown as well since the links aren't to the same place or format, but that's a different can of worms.

Adding it adds pain, decreases performance, and means a whole set of APIs to keep in sync. Given that we don't know what will happen with Area 51 a year from now, this implementation is not something we want to spend a great deal of time (and continued maintenance) on.

For the same reasons I lay out here it can't really appear here.

It has none of the aggregation code in place for repution, "posts", etc. If it did then we'd have to keep it in sync 2 places (things would break everywhere otherwise since it's serialization pain). In the user profile we one-off fetch it in the cache load since that fetches from a similar cache as the site switcher does for rep. However, since the site switcher is included on every page we can't have any delay.

For reputation specifically, we would have to aggregate every rep change, merge, deletion, etc., clear several caches when that happens, and also mix concepts of what the schema means (Area 51 isn't Q&A, some things don't translate). It adds complexity to the dropdown as well since the links aren't to the same place or format, but that's a different can of worms.

Adding it adds pain, decreases performance, and means a whole set of APIs to keep in sync. Given that we don't know what will happen with Area 51 a year from now, this implementation is not something we want to spend a great deal of time (and continued maintenance) on.

For the same reasons I lay out here it can't really appear here.

It has none of the aggregation code in place for repution, "posts", etc. If it did then we'd have to keep it in sync 2 places (things would break everywhere otherwise since it's serialization pain). In the user profile we one-off fetch it in the cache load since that fetches from a similar cache as the site switcher does for rep. However, since the site switcher is included on every page we can't have any delay.

For reputation specifically, we would have to aggregate every rep change, merge, deletion, etc., clear several caches when that happens, and also mix concepts of what the schema means (Area 51 isn't Q&A, some things don't translate). It adds complexity to the dropdown as well since the links aren't to the same place or format, but that's a different can of worms.

Adding it adds pain, decreases performance, and means a whole set of APIs to keep in sync. Given that we don't know what will happen with Area 51 a year from now, this implementation is not something we want to spend a great deal of time (and continued maintenance) on.