Quote from: Xal0lex on Today at 09:08:36 AM

Quote from: Issa56 on July 05, 2023, 10:56:31 PM

3 Accounts Connected: (Note: Banned shown in red / Inactive in Blue / Active profile (in ordinary link colour))

If the author of the topic does not mind, I would like to comment on this post.

Not at all - I've been on the road for the last week and haven't been able to give this thread my full attention.

Quote

First, you are misquoting the posts. Quotes should contain a link to the post you are quoting, so that anyone who wants to can go and see the post.

For example (quote from your post):

Quote from: Mix$$01 on February 26, 2023, 02:20:12 PM

#PROOF OF REGISTRATION
Forum Username:Mix$$01
Forum Profile Link:https://bitcointalk.org/index.php?action=profile;u=3531525
Telegram Username:@
Participated Campaigns:Twitter, telegram, Tiktok
BSC Wallet Address:0xe94a3a7f6603b2D72c352581bb7bBbBCFe4399B8

As you can see, the post you quoted is different from the one currently on the forum. Thus, you are misleading forum users.

I had a similar thought, but was wondering perhaps they don't have the BPIP extension to enable them to copy to clipboard from locked threads.

Quote

Second, ninjastic links are not suitable as an archive. The link to the actual post, not the ninjastic post, should be as an archive. You can archive a post (topic) using well-known archivers such as archive.is or web.archive.org

The correct link for the first is archive.today which will take you to a mirror in differing regions e.g ".is" but there are others.

I prefer to archive via both of these services and cite both in my posts.

Quote

Well, thirdly, I once wrote that:

Quote from: Xal0lex on September 24, 2022, 08:28:41 PM

In bounty, some users use previous posts as a sample, they copy that post and then edit it to suit themselves. Ninjastic remembers the post in its original form, which is why such mishaps occur.

Maybe this is just such a case

Yes, I agree and this issue does come up from time to time. I encourage anyone citing such connections to investigate a user's *entire* post history to ensure such a mistaken connection does not occur.

As I wrote yesterday:

Quote from: Timelord2067 on July 06, 2023, 12:27:50 PM

I'm not convinced.

Thanks for stopping by and providing some insight so we can all improve our reports.

Regards,