Howto find blogs from email addresses? [closed] - email

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 13 years ago.
Improve this question
I know many folks try to find emails form blogs but, I'd like to do the opposite.
For example, if I have someone's gmail email address, could I find out if they have a blogger account? a word press account?

No, and maybe.
While Blogger makes it possible to go from a profile page to an email address (example 1, example 2), there's no public index of those pages.
Wordpress.com doesn't have those type of standardized profile pages, so your chances of getting something there are zero.
If you have Yahoo IDs, you may be able to look up users' Yahoo profiles, which can either reference websites the user's associated with (example 1, example 2), or contain a Yahoo blog (example).

Get name portion of email address (everything before #), say "foobar"
Create URL "http://foobar.wordpress.com" and execute it with you preferred server technology (say HttpClient in Java)
Check response code - for the existing site it will be 200, for non-existing it will be 302 (redirect) and you can also check that you are not redirected to en.wordpress.com
You can do similar things with other type of sites that support naming conventions of user.site.com or www.site.com/user.
Of course there's no guarantee that based on the name that blog will belong to the same person, and there's plenty of blogs that have custom URLs all together
Alternatively use Google and parse results

Thats doubtful. You might be able to crawl those sites and see if you can find a matching email address inside the blog. Services don't generally allow anonymous lookups of their users info, for obvious reasons.

Related

Email address as resource identifier in a REST API [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
Say my application has users, and each user is uniquely identified by their email address. In that case, it makes sense to use the natural key of email rather than using an auto incrementing ID as the primary key, which is common in most systems.
Then, in my REST API, would it be okay to access a particular user like this?
https://api.whatever.com/v1/users/john#smith.com
Traditionally, you'd use the user ID in place of john#smith.com, but in my application the email address is the unique identifier for user accounts.
What would you pick? Using email as a natural key in REST URLs or create a user ID field to use instead?
I would use a user id. A person and their email address don't have a 1 to 1 relationship and they don't have the same life cycle, so using one as the identifier for the other is a bad idea.
People may have more than one email. Maybe they don't have an email account (it happens). Maybe they change their email. If you use the email address as the key, you might run into problems later on.
Should be url encoded
https://api.whatever.com/v1/users/john%40smith%2Ecom
Else fetching by id could by faster than by mail, and maybe you want to open the API to another application person, that should get the knowledge of the E-Mail address

my security q in Facebook does not exist [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 9 years ago.
Improve this question
i searched many times but all of sites says that it will be in settings / security tab, but it's not there! why?
i just created my Facebook account.
It looks like FB is not currently using security questions. This is from FB:
If there ever comes a time where you can’t log into your Facebook account, we need ways to get in touch with you and make sure the account is yours. Here are some things you can do to help make sure you never get locked out of your account:
Add another email address to your account so you always have a
backup.
Make sure you and only you can access the email addresses listed on your Facebook account. Anyone with access to one of the email
addresses listed on your account can request a new password for your
Facebook account. If you lose access to one of your extra email
addresses, be sure to remove it from your Facebook account.
Add your mobile number to your account. We can also send things (ex: a code to reset your password) to your mobile phone.
Use your real name and date of birth on your account so we can find your timeline if you ever loose access to it.
You can find more details on this security features page.
facebook now does not offer any security questions for account safety. It uses now two-factor security model and sms authentication code. Don't go in that deeply.

Are there any ways to track : Visitors of my site are come from which site? [closed]

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
This is a problem because when I do email campaign, There is a link on the email, that link to my company homepage, I would like to differentiate between the visitor come from another way (e.g. search on google) or the visitor come from the email I have sent.
Notice that they should come form a email instead of a website,
Is it able to check such kind of information ? And is it possible to differentiate between campaign 1 and campagin 2 with same link? Thankyou
You cannot differentiate between an email vs web campaign link unless that link is tagged for campaign tracking. Campaign link tracking requires that you append additional data to the query params of a link according to specific conventions required by GA in order to differentiate between different campaigns.
Other wise, Google Analytics would not be able to differentiate between the same links from email vs banner links on a very granular level.
http://support.google.com/googleanalytics/bin/answer.py?hl=en&answer=55540
Google Analytics is the easiest way to do this. get an account, copy and paste the code they give you and they keep track of all of this for you in the traffic sources tab under the referrals traffic and even give you the exact url of the site your visitors are coming from. including emails and yes I believe you can differentiate between campaigns.
here is the url
http://www.google.com/analytics/
Google Analytic is perfect, just what you need.

What is the point of the Remember Me option on website logins? What is stopping developers from ALWAYS remembering the user? [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
Is it simply an artifact of the old fear (still around in some places) of cookies?
I also would like to know if it is bad practice to simply pass in user names from an outbound email.
Nothing is stopping the web app from always remembering the user for as long as they want on particular computer without asking explicit permission from the user. However, doing so has security and privacy implications on shared computers.
Imagine you go to a cyber-cafe or a library, sit on a shared computer and login to your bank website (which you shouldn't do from such places anyway :-)). The bank website tries to be "smart" and persists a cookie with a ticket based on your credentials. When you're done, you close the browser without logging off. Next person sits down, opens the browser, looks at the history and goes to the bank site. And now they have magically access to all your money.
That would probably be the last time you use that bank for anything.
Update: To answer the second part of the question (and the comment below)
If you are afraid of URL injection, you should probably not specify the username in the email URL itself. Instead, generate a one-time token (you could use a one-way hash of the user name and a website secret for example), which wouldn't mean anything to an external site, but would allow you to extract the user identity and prepopulate the field on the page.
Keep in mind that you should not include in the URL in the email enough information, so that clicking on that link would authenticate the user to your site. You still want the user to prove their identity.

Protect Email on Web Site From Robots and Crawlers [duplicate]

This question already has answers here:
Closed 14 years ago.
Closed as duplicate of What are some ways to protect emails on websites from spambots?
I am finally puting up my personal web site. I want to publish a webmaster/feedback email on every page, but I am concerned about SPAM crawlers extracting the email address and bombarding me. This is especially true because I can't use my normal whitelist oriented filtering in this case. Are there effective ways to communicate an email address to people which are hard for crawlers to extract?
My long term plan is to allow feedback via posted forms (and then I will have questions about captcha for y'all), but I don't have time for that now (it's not an immediate priority), and I don't want to go live with no means of feedback at all.
when you get to the forms perspective then look at something free like recaptcha.net
As for now, simply obfuscating the email address in some form should help. I would consider the common [my email (AT) some domain dot com] type of writeout. You could also add another layer of defense by doing that in an email using various fonts and sizes and other effects to beat very sophisticated crawlers with OCR abilities
See this Stackoverflow thread
I'm partial to using javascript to construct the mailto URL on the client side.
Some alternatives to the JavaScript method.
Spell out your address and avoid making it a link.
Example: someone (at) somewhere (dot) com.
HTML encode the email address in the href attribute and inside the anchor tag.