While looking through my timeline in Tweetbot, occasionally a tweet will be marked as a favorite even though I'm sure I'm seeing it for the first time. (I can't resist taking the time to unfavorite it.) I don't see any mention of this in http://tapbots.com/support/tweetbot/. Is this a bug, or a "feature" (where perhaps Twitter's API is doing this)?
Tweets in the Tweetbot timeline are occasionally marked as a favorite when I see them for the first time. Is that a bug or a feature
bugtweetbottwitter
Related Solutions
FileVault 2 uses the GeneratedUID user attribute to save who is permitted to unlock an encrypted volume. If the GeneratedUID of a user differs from what was generated (or pulled from LDAP) when FileVault 2 was enabled, the user will not be permitted to unlock the machine, as their account will appear to be unavailable at the EFI menu. Also, this causes the crash of System Preferences on their Mac whenever they try to access the Security & Privacy prefpane.
This problem arises when /usr/bin/mcxrefresh runs and pulls a null value or a value different than what is stored locally from LDAP (if the attribute isn't defined for the user in question or is defined incorrectly, respectively), overwriting the GeneratedUID stored locally (which is generated and only stored locally when FileVault 2 is enabled without a matching LDAP attribute).
In other words, if an apple-generateduid value exists in LDAP for a user and is mapped properly on the users Mac to the GeneratedUID attribute, FileVault 2 will not generate a new value, but will instead use the value stored in LDAP.
I was able to resolve this issue by adding an attribute called apple-generateduid to the LDAP entry of any user experiencing this issue. I could generate a random value for this attribute in Python by running the following one-liner from my terminal:
python -c 'import uuid; print str(uuid.uuid4()).upper();'
This isn't the only step, however. You must also add a mapping for this attribute on the client side. This is easily done using the following steps:
- Open System Preferences.
- Click Users & Groups.
- Click Login Options.
- Click on the Unlock Icon.
- Under Network Account Server, click Edit.
- Click to highlight your directory server.
- Under Services, double-click on your directory service (in my case, it was LDAPv3)
- In the window that slides open, highlight your configuration name, and then click the Edit... button.
- Under Search & Mappings scroll down and single-click on Users to highlight it.
- Click the Add button (the left one).
- Choose GeneratedUID from the list of available Attribute Types.
- In the right column, click the Add button, and type
apple-generateduid. Click OK to save the changes until you're back at the main System Preferences dialog. - At this point a mapping from GeneratedUID to
apple-generateduidhas been created. Now when OS X looks up the GeneratedUID value it will get the value of apple-generateduid from the user in questions LDAP entry.
Finally, it's important that the locally stored value of GeneratedUID and value stored on LDAP match. Run the following command and make sure the two GeneratedUID values match:
dscl /Search search /Users GeneratedUID $(dscl . read /Users/$(echo $USER) GeneratedUID | cut -d " " -f2)
Does it run with gatekeeper disabled? If so it can be a codesigning issue. There is a terminal command 'codesign': You'd want to look at the hashes and and certs auths in the output.
codesign -d --verbose=4 /Path/Application.app
Documentation regarding codesigning is here
Best Answer
It's a bug with Twitter, not Tweetbot.
I've seen people ask @tweetbot about it several times now. The answer and response generally look like this exchange:
That particular exchange happened just yesterday.
Twitter's REST API bug list has this bug still open where the API may erroneously report a tweet as favorited when in fact it is not.