🖥️| Digital dreamer, coder | Cruising between bytes and bits | AI-generated visions with a side of tech talk | Debugging is my cardio, pixels are my palette | Where algorithms and imagination entwine
You could use something like https://huggingface.co/defog/sqlcoder-34b-alpha / https://github.com/defog-ai/sqlcoder however I haven’t used this one myself but it builds up on CodeLlama model so the quality should be good. I haven’t seen other models specifically for SQL queries yet.
Edit: it includes all the hardware requirements and some demo examples in the links
I stopped first in the lower floors checking out the fancy talk meme :D was wondering what tea post and few memes higher found it
I would definitely suggest to put a reverse proxy like nginx or Apache in front of it. It will make your life easier in the future regarding scaling. It’s also good to protect your Django app by masking it. Use nginx, setup TLS, proxy traffic to your Django app and be happy.
What’s exactly the issue tho? Like are you looking for technical help? Moderation and community help? Starting a media wiki instance isn’t the hardest part especially if you plan on to scale out later. There are multiple one click Hosters who take care of the setup and you’re just free to fill in the rest, ofc costs money for quality hosting.
VR depicted in different centuries
I still prefer the foxy look tho
deleted by creator
When it’s your first day at the new office, but you didn’t read the fine print about “team-building exercises”
Just want to add you’re right but what pisses me off is that they still can influence decisions based on this. Let’s say his shares are sold at x day, just do some decisions before that and boom your auto sell share price is now either higher or lower. Only because it’s predetermined they still influence it and SEC now can’t do shit.
Living paycheck to paycheck is a valid reason how one can’t even save up to consider even buying a house. Soon with the rising prices it will even be living on borrowed time.
Asked GPT about that after skimming through the wiki to confirm if it’s also comes to the same conclusion that the keys are periodically changed and yeah it did confirm it:
The “Double Ratchet Algorithm” used by Signal provides both forward and future secrecy for messages. Here’s a basic breakdown of how this works:
The Double Ratchet Algorithm:
Initialization Phase: The two communicating parties (let’s call them Alice and Bob) establish a shared secret using the Diffie-Hellman key exchange. Ratcheting Phase: After the shared secret is established, every message is encrypted using a new symmetric key. Keys are derived in a chain where the next key is a function of the previous key. This is the “symmetric-key ratchet”. After sending or receiving a message, Alice and Bob independently update their chain keys, which helps ensure forward secrecy. Diffie-Hellman Ratchet: Periodically, Alice and Bob also update their Diffie-Hellman key pairs, exchange the public components, and derive a new shared secret. This helps provide future secrecy. Example:
Let’s consider a simple conversation between Alice and Bob.
Initialization: Alice and Bob meet in person and exchange public keys. They generate a shared secret that only they know using these keys. First Message (from Alice to Bob): Alice derives an encryption key from the shared secret. Alice sends “Hello, Bob!” encrypted with this key. After sending the message, Alice updates her chain key. Bob’s Reply: Bob derives the same encryption key from the shared secret, decrypts Alice’s message, and reads “Hello, Bob!”. Bob then derives a new encryption key from his updated chain and sends “Hi, Alice!” encrypted with this new key. After sending the message, Bob updates his chain key. Diffie-Hellman Ratchet: After a few messages or after a certain period, Alice decides to perform a Diffie-Hellman ratchet. She generates a new key pair. Alice sends her new public key to Bob along with her next message. Both derive a new shared secret using Alice’s new public key and Bob’s current private key. This new shared secret is used to start a new chain of symmetric keys. Continued Conversation: Alice sends another message: “How are you?” with a key derived from the new shared secret. After every message, sender and receiver update their chain keys. Periodically, they will also perform the Diffie-Hellman ratchet to refresh the shared secret. The benefit of this mechanism is that even if an attacker compromises a single message key, they cannot decrypt past messages (forward secrecy) or future messages (future secrecy). Even if they compromise a current Diffie-Hellman private key, they can’t decrypt messages that were sent before the compromise (because of the symmetric ratchet) or messages sent after the next Diffie-Hellman ratchet (because a new shared secret will be established).
As once a great man said: “Anyway, like I was sayin’, shrimp is the fruit of the sea. You can barbecue it, boil it, broil it, bake it, saute it. Dey’s uh, shrimp-kabobs, shrimp creole, shrimp gumbo. Pan fried, deep fried, stir-fried. There’s pineapple shrimp, lemon shrimp, coconut shrimp, pepper shrimp, shrimp soup, shrimp stew, shrimp salad, shrimp and potatoes, shrimp burger, shrimp sandwich. That- that’s about it.” ~Bubba
Yeah I would also suggest to stick with 1g switches and if the need for bandwidth is required then create a LAG. 2.5g is currently just finding adoption at this point.