sticky bit only has an effect on directories and not on files. If sticky bit is set on a folder, only the owner of a specific file, folder, or subfolder created in that directory is allowed to delete it. There are some special cases where this is useful, for example, in the /tmp directory, where anybody should be allowed to see anything, but quite often processes create and rely on data stored in that folder, so it would be very bad if someone other than the creator of the process could be able to delete files from other users.
So let's test this out:
As you can see, sticky bit has been set on the /tmp directory, so let's create a new file with the olip user in the /tmp directory. Now, let's look in with awesome_user. As no password has been set, let's set one for it. Now, awesome_user will also create a new file in the /tmp directory. Now, let's try to delete our own file, which works. Now, let's try to delete the file of the olip user; this does not work, so sticky bit is working as expected:
