Mods: please assist with hidden posts

[jwhendy]

Hello, I received several of these within the span of a few minutes:

Your post was flagged as spam: the community feels it is an advertisement, something that is overly promotional in nature instead of being useful or relevant to the topic as expected.

Multiple community members flagged this post before it was hidden, so please consider how you might revise your post to reflect their feedback. You can edit your post after 10 minutes, and it will be automatically unhidden.

However, if the post is hidden by the community a second time, it will remain hidden until handled by staff – and there may be further action, including the possible suspension of your account.

Is the message true? The examples below were actually flagged by multiple community members? Or is this an algorithm thing because I’m somewhat new and they include links (which aren’t below due to copy/pasting below)?

If this is an algorithm thing, here’s feedback that I don’t think it’s accurate. Alternatively, please let me know how I can better follow the community guidelines.

---

Here’s an example (contains two links to arch linux forum threads about the issue):

ST3 Screen flicker in linux

ST3 Screen flicker in linux

Grrr. So I just noticed this after not using sublime for a while. It’s great to find that others have it, but not great to find out that a possible solution might be xf86-video-intel. I had a problem with sublime and a bunch of other applications about a year ago that was fixed by removing xf86-video-intel. There was a much bigger thread that also suggested removing this driver in favor of the modesetting driver.

I’d prefer not to go back to the intel driver if I can avoid it! Any other thoughts on settings or root cause?

I’m also on arch linux, though I use bumblebee (nvidia discrete, intel integrated). Oddly, I get the artifacts when I do optirun subl3, which should be using the nvidia card, not intel).

Here’s another (contains one link to the github wiki page about the plugin I’m discussing):

Adjust versioning strings for a release vs. development plugin?

Adjust versioning strings for a release vs. development plugin?

These are the current instructions:

1. To upgrade the files open the Package Control quick panel Preferences > Package Control and select Upgrade Package. After some seconds the plugin will be updated.
2. If there is a new change in the branch and you are not receiving the update, select Upgrade/Override All Packages From the Package Control quick panel.
3. Restart Sublime Text each time a change is pushed

• is this accurate? As in, adding a repo pointing to repo/tree/branch will update with each commit? Your note about adding the prerelease and that “After that, Package Control will install the newest release” makes me think a tag is still somehow required to trigger an update?
• if it does auto-update based on a new commit, then updating (in my mind) already has the desired behavior without adding an immense amount of tags
• in that case, it’s more about finding which version one is on and since posting this I confirmed the commit date string, so perhaps that’s the way to roll. Seems pretty easy and could just be added to the wiki instructions for users wanting to check.

I am now wondering if master is the source of tagged releases; if so, perhaps the develop branch could maintain a different version string based on the commit hash or date. This would make the version more obvious in the console output.