Paths Short or Long

I am working through a problem with path names. The previous version of a site used short codes for url paths. Coming into this for a new project and the short code based paths, while deterministic, seem user-unfriendly to me.

Example current

as1/u2/m4/s7

Example longer

assume-1/unify-2/mobile-4/sturgeon-7

The words are changed so client info isn’t released. The content is linear and so numbers have meaning in context.

My question is this. Have there been any UX studies done to show whether or not this makes any difference. SEO is no consideration as all this content is behind a paywall and is internally indexed/searchable.

create 500 backlinks in short time with low budget for $5

Boost your ranking on Google within 3 DaysBoost your ranking on Google with High quality backlinks. Get increase in ranking within 3 days. No need to pay thousands of dollars to big SEO companies. We don’t waste your time and money like other SEO services. We provide real SEO that brings result.

by: fazel29
Created: —
Category: Link Development
Viewed: 279


How to generate short fixed length cryptographic hashs?

I am trying to implement a kind of email verification system with a node.js server with no state.

The strategy

  1. User sends his email to the server
  2. Server generate a 4 digits code based on the email address and sends it to the user via email.
  3. User sends back the received code via email + the email address to the server
  4. Server re-generates the 4 digits code based on the email and compares it with the code sent by the user.

My implementation to generate the 4 digits code

  1. Create a HEX digest using HMAC SHA-256 hash function
  2. Take the first 3 characters of the digest
  3. Convert them to an integer
  4. If length < 4, concatenates one or multiples 0 at the end
const crypto = require('crypto')  const get4DigitsCode = (message) => {   const hash = crypto     .createHmac('sha256', Buffer.from(SECRET_KEY, 'hex'))     .update(message)     .digest('hex')    const first3HexCharacters = hash.slice(0, 3)    const int = parseInt(first3HexCharacters, 16)    let code = int.toString()   code =     Array(4 - code.length)       .fill(0)       .join("") + code    return code } 

After generating codes for 8293 email addresses, I noticed that I had 4758 duplicates. Is it normal to have this amount of duplicates for a code as this sort ? Is my strategy and my implementation secure (ability to guess the code) ?

Onboarding with many user profile fields – lengthy and detailed vs. short and essential?

So if you can imagine a dating app, the essentials are stuff like: gender, location, age, name, a photo

Then say you have some optional fields that are pretty useful such as “looking for” – their purpose for using the app.

And then say you have 20 other fields which are nice to have, but not need to have: religion, politics, languages, diet, relationship type/status, etc.

If you make the user fill them out during onboarding, well then onboarding gets kinda long and becomes a pain. If you keep it short with the just the essentials, then you end up with many minimal profiles e.g. people who just uploaded a photo, didn’t fill out their bio, and left it at that.

What do you suggest?

Simple generator of pseudo-random permutations of variable length short sequence

The problem in front of me is to write a function (from scratch) to permute n elements, where n is an argument. I decided to break it down to applying Knuth’s shuffles algorithm, therefore I needed to write a pseudorandom number generator.

So now my task is to write a simple function F(seed,n) that will help me generate indices for the pseudorandom permutations of n elements. However, the function has to be extremely simple: My constraint is that I can only use the following operators: +,-,*,/,%, specifically, no address access, binary encoding, bits selection etc. – only arithmetic on numbers. That is fine, I went for linear congruental generators and implemented a (a*x+c)%m procedure.

As I started testing F(seed,2) it immediately went apparent that the results oscilate between zero and one with a period of two.

My problem is: how can I adjust F to avoid that behavior? Maybe I should generate the n-permutations in a different manner?

In practice, I am only interested in n=<32

Is there a way to send alert summaries after a short period of time?

The problem: an end user performs a bulk change on a large list, and those with “Send notification immediately” receive a large volume of email. Each message is regarding a different list item, although they all have in common the same change.

Those receiving these alerts want to be notified of changes as soon as possible, albeit with a single summary e-mail just like the ones generated by the “Send a daily summary” and “Send a weekly summary” alert options.

Things I’ve tried: Creating a custom workflow in SharePoint Designer 2013, creating a Microsoft Flow that sends an email when items on a SharePoint list change. The former resulted in the same as “Send notification immediately,” with an email for each list item modified in the bulk change. The latter I couldn’t get to work; I have trouble with understanding what’s happening in Microsoft Flow, or what it wants from me to succeed.

I’m not opposed to modifying the behavior of the “Send a daily summary” just for this one SP site if it meant I could force it to send a summary 5 minutes after a bulk change is made. If that’s a possibility, however, I don’t readily know how to do that. I do have farm admin support so if something needs to happen on the back end, provided it doesn’t cause problems for others that assistance is available.

If it’s plain impossible, that’s a shame but fine too.

tar using short form option versus old style

In the GNU manual for tar, there is the following example to show that the order of the options is important:

tar -cfv collection.tar blues folk jazz

In this case, because jazz v is placed after f, then the tar archive will be named “v”, and tar will try to add collection.tar to the archive if it exists in the current directory. But if I omit the - from the beginning, then the command works as we would want it to, despite v being placed after f. Why?

An effective & short 100-word product description for $1

When it comes to conversion, an effective production description is one of the most important aspects of your online sales as 50% of purchase failures are potentially as a result of unclear or missing product information. Product descriptions can make or break a sale! Here’s what we promise to deliver: You’ll get an effective &short 100-word product description that will make the maximum impact in minimum time with the power to turn a casual shopper into a revenue generator buyer. Our writers will write a sweet & short product description for a human audience rather than a long text loaded with keywords. Order now & get a powerful product description to move your clients through your sales funnel. Here’s what our writers need from you: 1. Manufacturer Name 2. Product Name 3. Ingredients 4, Basic Function 5. Price

by: mawtas
Created: —
Category: Article Writing
Viewed: 151


Is it possible to crack a CRC value for short text validation when someone tries to change a readable text?

I’d like to validate message texts with CRC-8/16/32 but I’m afraid that they could be changed to another one (for example, adding a “No” at the beginning). There will be no special characters besides the usual ones (? , . ; ª º + =…) and the number of bytes will be counted as well. The messages will not be encrypted.

Long tail keywords or short keyword? and why? For beginners

As you might already know that Google prefers long-tail keywords over short keyword but you may not know the reason behind it.
Here I will give you an example of why long-tail keywords are more preferred over short keywords.
Take example,
If you want to learn to make french fries at home,
You'll always search "How to make homemade french fries or How to make french fries at home" (Long-tail keyword)
and probably will not search "homemade french fries" (short keyword).
As you can see, in this…

Long tail keywords or short keyword? and why? For beginners