If this was happening to me, Iād be laying down a few false trails just for fun.
Not that Iām suggesting that.
2 Likes
Thatās the thing, I suspect this already lol
We know that
He knows that we know,
1 Like
Yup, thatās when it gets fun. Start telling the truth while everyone thinks your fibbing. Then switch.
Be Mysterious.
A.K.A. āIf you canāt dazzle them with brilliance, baffle them with bullshit!ā
1 Like
Iām not gonna start that videoā¦ even just reading the title makes me remember that melody, and that means I will have it in my mind for the next week at least. Damn you! 
I just knew āyou touch my tralalaā from that āartistā, didnāt know he had more songsā¦ and Iām not sure if Iām happy about it 
Hah, and Basshunter in the recommendations, thatās a nice one too (at least his old gaming-related songsā¦)
Soooā¦ now, since @Pilgrimsmaster asked for it, a very recent picture of my scars:
It starts to āfadeā, at least in colour (which it should do, so, all fine), but it keeps the 3D-effect and, of course, a different skin texture. It is less irregular than it looks like on the picture, but there are some little spots that need reworking - my artist is aware of that, but I donāt know when we will find the time for it (like, when lockdown is overā¦).
But itās a really interesting mod, I think - one would think that those thicker lines are all the ones where he cut a bit deeper, but thatās not always the case. I compared it to the first picture, and some cuts of the same depth have developed very different scars. My artist told me that this was very likely to happen, so Iām fine with it, but itās still pretty interesting to see what my body decides to do
Oh, pain is completely gone, from time to time there is a slight itching, like in all bigger scars.
Really looking forward to get more of that 
5 Likes
Is it just me or the forum is acting up?
I get 403 errors
1 Like
I have never had any errorsā¦Browsing on Chrome
No itās okay. Well, thereās a bug somewhere, but itās not a forum issue.
I was trying to paste some Python code in a post, and apparently that triggers something in Discourse. It says āDraft offlineā and throws a 403 error when I try to post it.
1 Like
Will this work for you?
No no it was preformatted. As soon as whateverās in the code is in the post, it triggers the error.
You can try it yourself, itās the script in the ZIP I posted in Amalās LUA script thread.
1 Like
Roger Dodger, I just tried it and Yeah,
I am now apart of the club
Yeah and look, as soon as you plug the code in the post, at the bottom of the editor, it says āDraft offlineā. Really oddā¦ Maybe itās trying to protect against code injection or something.
1 Like
So if you remove this line and all after, It will allow you to post ( I all the lines I have just pasted below, it had no issues with as you can seeā¦
So you could post in 2 posts
Weird
Process the lines from the client
for l in rlines:
if args.verbose:
print(" PM3>PC: {}".format(l))
# We got a prompt
if pm3_prompts_regex.match(l):
if state in (WAIT_PROMPT1, WAIT_FINAL_EM_CHECK):
if state == WAIT_FINAL_EM_CHECK:
# No reply from the final EM check
print("No reply from {} programmed as EM chip. Press ENTER".format(
chip_type))
input()
print("Probing for T55xx...")
# Send the command to detect a T55xx in the field
os.write(pty_master, b"lf t55xx detect\r")
if args.verbose:
print(" PC>PM3: lf t55xx detect")
state = WAIT_T55XX_PROBE
elif state == WAIT_PROMPT2:
# Send the command to program the T55xx as an EM with the current UID
print("lf em 410x_write {} {}\r".format(
hex(uid)[2:].upper(),
1 if chip_type == "T55x7" else 0)
)
write_cmd = "rem Pretend writing {} tag with UID {}: Done" \
if args.dryrun else "lf em 410x_write {} {}"
os.write(pty_master, write_cmd.format(hex(uid)[2:].upper(),
1 if chip_type == "T55x7" else 0).
encode("ascii") + b"\r")
if args.verbose:
print(" PC>PM3: {}".format(write_cmd))
state = WAIT_WRITTEN
elif state == WAIT_PROMPT3:
# Send the command to read back the EM
os.write(pty_master, b"lf em 410x_read\r")
if args.verbose:
print(" PC>PM3: lf em 410x read")
state = WAIT_FINAL_EM_CHECK
else:
# We shouldn't have gotten a prompt in another state
print("Unexpected reply from Proxmark3 client: {} - stop".format(l))
return -1
# We got a regular line (i.e. not a prompt)
else:
if state == WAIT_T55XX_PROBE:
# Did we detect a T55xx, and if so, which type?
m = re.findall("(Could not detect|Chip Type\s*:\s*([a-zA-Z0-9]+))", l)
if m:
chip_type = m[0][1]
if not chip_type:
state = WAIT_PROMPT1
else:
print("{} detected. Program with UID {}? [ENTER=Y / N]".format(
chip_type, hex(uid)))
state = WAIT_PROMPT1 if input() else WAIT_PROMPT2
elif state == WAIT_FINAL_EM_CHECK:
# Did we detect an EM in the field, and does the UID match what we
# programmed in?
m = re.findall("EM TAG ID\s*:\s*([a-fA-f0-9]+)", l)
if m:
if int(m[0], 16) == uid:
uid += 1
print("{} programmed correctly. Press ENTER".format(chip_type))
else:
print("EM UID mismatch. Press ENTER")
input()
state = WAIT_PROMPT1
elif state == WAIT_WRITTEN and re.search("Done", l):
state = WAIT_PROMPT3
Jump to the main routine
if name == āmainā:
sys.exit(main())
eyyy
Do you have a spare Titan laying around to compare to the Xg3s?
I woke up from a dream about magnets and then i wondered about the Titan compared to the Xg2 V2 in terms of lifting strenght 
1 Like
Hmm yeah, but it works better with all the lines in it 
1 Like
Haha, Yeah, I just updated my post as you replied
So if you remove this line and all after, It will allow you to post ( I all the lines I have just pasted below, it had no issues with as you can seeā¦
So you could post in 2 posts
Weird
Yeah, or I could post a ZIP 
1 Like
Good idea, you should just do thatā¦Much easier 
you are welcome!
He has soooo many more!
Hits like āThe Ding Dong Songā, āTouch meā and āNo Pantalonesāā¦
Truly a modern day āgeniusā, right? 
Looking great!!! 
Can picture it though!
I have the same issues when trying to get a good healing pic.
Keep us posted! 
That one is developing very well!!
2 Likes
I am not surprised at all that Discourse would prevent you from uploading thisā¦
seen far too many systems falling for both that and droptablesā¦ Canāt blame the devs from preventing against that even if we believe it should be captured elsewhere.
Posting ANY content should never be a problem, be it the complete works Shakespeare, movies, /dev/random or binaries of any kind. Bad coders who canāt handle their inputs properly try to secure their shit by preventing you from entering ābadā input - despite the fact that it is only bad because they canāt code properly.
If this is whatās happening here, itās disappointing, but hardly surprising.
1 Like