kv109

Hyphens are typically not allowed in hashtags due to a combination of technical, usability, and design considerations. Here's a breakdown of why most social platforms and systems exclude hyphens from hashtags:

---

1. Ambiguity in Parsing

• Problem: Hyphens (-) can conflict with other uses in text:
  • In natural language: "Check out #throw-back Thursday!" → Is it #throw or #throw-back?
  • In code/URLs: Hyphens are often used to separate words (e.g., my-project), which could clash with hashtag parsing.
• Solution: Restricting hyphens avoids confusion, ensuring hashtags are unambiguous and self-contained.

kv109

TEMPLATE 1 (LANGUAGE CODE: CS):
Vítejte v Motimate!
Kliknutím sem můžeš začít: https://motimateapp.com/go?id=%{identifier_name}
Následovat budou přihlašovací údaje.

TEMPLATE 2 (LANGUAGE CODE: CS):
Ahoj, jen přátelské připomenutí od společnosti  :)
Kliknutím sem můžeš začít: https://motimateapp.com/go?id=%{identifier_name}
Následovat budou přihlašovací údaje.

kv109

1. Create a export-pod-name.sh file with the following content:

POD_NAME=$(kubectl get pods --sort-by=.metadata.creationTimestamp --selector=YOUR-SELECTOR-KEY=YOUR-SELECTOR-VALUE -o go-template --template '{{range .items}}{{.metadata.name}}{{"\n"}}{{end}}' | tail -n1)
# Example:
# POD_NAME=$(kubectl get pods --sort-by=.metadata.creationTimestamp --selector=app=nginx -o go-template --template '{{range .items}}{{.metadata.name}}{{"\n"}}{{end}}' | tail -n1)

export POD_NAME=$POD_NAME

kv109

Marketplace KIT authorization flow is gonna change very soon.

Please help with testing the new flow!

(Yes, QA guys, I'm hoping that you'll help ;))

• Uninstall your mp-kit:

npm uninstall -g @platform-os/marketplace-kit

Verify that you don't have marketplace-kit:

kv109

Diff Challenge

Concept

Good codebase is easily modifiable. Diff Challenge verifies how easy is to add a new feature to your application or change its existing behavior. This process is done in two steps.

In the first step you write code according to a provided specification.

In the second step, you receive a new version of the spec, which contains some new requirements.

kv109

"pa".hex #=> 0
"ss".hex #=> 0
"wo".hex #=> 0
"rd".hex #=> 0
"".hex   #=> 0

"password".unpack("a2"*32).map { |x| x.hex } 
#=> [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]
"totally wrong password".unpack("a2"*32).map { |x| x.hex } 
#=> [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]

kv109

"password".unpack("a2"*32)
 => ["pa", "ss", "wo", "rd", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", ""]

kv109

'9'.hex   #=> 9
'a'.hex   #=> 10
'10'.hex  #=> 16
'ff'.hex  #=> 255
# zero is returned on error:
'foobar'.hex  #=> 0
'zz'.hex      #=> 0

kv109

@cipher.key = @key.unpack('a2'*32).map{|x| x.hex}.pack('c'*32)

kv109

encrypted = AES.encrypt("Super secret message", "password")
decrypted = AES.decrypt(encrypted, "totally wrong password")
decrypted  #=> Super secret message