Skip to main content
Super User

Return to Answer

replaced http://meta.stackexchange.com/ with https://meta.stackexchange.com/
Source Link
Community Bot
Community Bot
  • 1

I don't think this is really constructive any more. Kevin Montrose (SE developer) explained on Meta Stack Overflow why we have the filter and why it's here to staywhy we have the filter and why it's here to stay with some pretty hard data.

Yes, there are workarounds. They've also been documented on MSO, and the team has explicitly stated that they're not going to close the loopholes for now, but will if they get continuously abused.

This discussion has gone on long enough and isn't productive, so I'm locking this post for the time being.

I don't think this is really constructive any more. Kevin Montrose (SE developer) explained on Meta Stack Overflow why we have the filter and why it's here to stay with some pretty hard data.

Yes, there are workarounds. They've also been documented on MSO, and the team has explicitly stated that they're not going to close the loopholes for now, but will if they get continuously abused.

This discussion has gone on long enough and isn't productive, so I'm locking this post for the time being.

I don't think this is really constructive any more. Kevin Montrose (SE developer) explained on Meta Stack Overflow why we have the filter and why it's here to stay with some pretty hard data.

Yes, there are workarounds. They've also been documented on MSO, and the team has explicitly stated that they're not going to close the loopholes for now, but will if they get continuously abused.

This discussion has gone on long enough and isn't productive, so I'm locking this post for the time being.

Fixup of bad MSO links to MSE links migration
Source Link
Community Bot
Community Bot
  • 1

I don't think this is really constructive any more. Kevin Montrose (SE developer) explained on Meta Stack Overflow why we have the filter and why it's here to stay with some pretty hard data.

Yes, there are workarounds. They've also been documented on MSO, and the team has explicitly stated that they're not going to close the loopholes for now, but will if they get continuously abused.

This discussion has gone on long enough and isn't productive, so I'm locking this post for the time being.

I don't think this is really constructive any more. Kevin Montrose (SE developer) explained on Meta Stack Overflow why we have the filter and why it's here to stay with some pretty hard data.

Yes, there are workarounds. They've also been documented on MSO, and the team has explicitly stated that they're not going to close the loopholes for now, but will if they get continuously abused.

This discussion has gone on long enough and isn't productive, so I'm locking this post for the time being.

I don't think this is really constructive any more. Kevin Montrose (SE developer) explained on Meta Stack Overflow why we have the filter and why it's here to stay with some pretty hard data.

Yes, there are workarounds. They've also been documented on MSO, and the team has explicitly stated that they're not going to close the loopholes for now, but will if they get continuously abused.

This discussion has gone on long enough and isn't productive, so I'm locking this post for the time being.

Migration of MSO links to MSE links
Source Link
Community Bot
Community Bot
  • 1

I don't think this is really constructive any more. Kevin Montrose (SE developer) explained on Meta Stack Overflow why we have the filter and why it's here to staywhy we have the filter and why it's here to stay with some pretty hard data.

Yes, there are workarounds. They've also been documented on MSO, and the team has explicitly stated that they're not going to close the loopholes for now, but will if they get continuously abused.

This discussion has gone on long enough and isn't productive, so I'm locking this post for the time being.

I don't think this is really constructive any more. Kevin Montrose (SE developer) explained on Meta Stack Overflow why we have the filter and why it's here to stay with some pretty hard data.

Yes, there are workarounds. They've also been documented on MSO, and the team has explicitly stated that they're not going to close the loopholes for now, but will if they get continuously abused.

This discussion has gone on long enough and isn't productive, so I'm locking this post for the time being.

I don't think this is really constructive any more. Kevin Montrose (SE developer) explained on Meta Stack Overflow why we have the filter and why it's here to stay with some pretty hard data.

Yes, there are workarounds. They've also been documented on MSO, and the team has explicitly stated that they're not going to close the loopholes for now, but will if they get continuously abused.

This discussion has gone on long enough and isn't productive, so I'm locking this post for the time being.

Source Link
nhinkle Mod
nhinkle Mod
  • 37.5k
  • 3
  • 78
  • 119