mirror of
https://github.com/danielmiessler/Fabric.git
synced 2026-01-10 14:58:02 -05:00
Compare commits
2 Commits
v1.1.1
...
transcribe
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
fbfea93b6c | ||
|
|
c4332c9ee0 |
21
README.md
21
README.md
@@ -14,7 +14,6 @@
|
||||
<h4><code>fabric</code> is an open-source framework for augmenting humans using AI.</h4>
|
||||
</p>
|
||||
|
||||
[Introduction Video](#introduction-video) •
|
||||
[What and Why](#whatandwhy) •
|
||||
[Philosophy](#philosophy) •
|
||||
[Quickstart](#quickstart) •
|
||||
@@ -26,7 +25,6 @@
|
||||
|
||||
## Navigation
|
||||
|
||||
- [Introduction Video](#introduction-video)
|
||||
- [What and Why](#what-and-why)
|
||||
- [Philosophy](#philosophy)
|
||||
- [Breaking problems into components](#breaking-problems-into-components)
|
||||
@@ -47,13 +45,18 @@
|
||||
|
||||
<br />
|
||||
|
||||
## Introduction video
|
||||
> [!NOTE]
|
||||
> February 16, 2024 — **It's now far easier to install and use Fabric!** Just head to the [Quickstart](#quickstart), install Poetry, and run `setup.sh`, and it'll do all the work for you!
|
||||
|
||||
<div align="center">
|
||||
<a href="https://youtu.be/wPEyyigh10g">
|
||||
<img width="972" alt="fabric_intro_video" src="https://github.com/danielmiessler/fabric/assets/50654/1eb1b9be-0bab-4c77-8ed2-ed265e8a3435">
|
||||
</a>
|
||||
</div>
|
||||
<br />
|
||||
|
||||
```bash
|
||||
# A quick demonstration of writing an essay with Fabric
|
||||
```
|
||||
|
||||
<video src="https://github.com/danielmiessler/fabric/assets/50654/09c11764-e6ba-4709-952d-450d70d76ac9" controls>
|
||||
Your browser does not support the video tag.
|
||||
</video>
|
||||
|
||||
## What and why
|
||||
|
||||
@@ -262,7 +265,7 @@ The wisdom of crowds for the win.
|
||||
|
||||
But we go beyond just providing Patterns. We provide code for you to build your very own Fabric server and personal AI infrastructure!
|
||||
|
||||
To get started, just run the `./setup.sh` file and it'll set up the client, the API server, and the API server web interface. The output of the setup command will also tell you how to run the commands to start them.
|
||||
To get started, head over to the [`/server/`](https://github.com/danielmiessler/fabric/tree/main/server) directory and set up your own Fabric Mill with your own Patterns running! You can then use the [`/client/standalone_client_examples`](https://github.com/danielmiessler/fabric/tree/main/client/standalone_client_examples) to connect to it.
|
||||
|
||||
## Structure
|
||||
|
||||
|
||||
@@ -1,21 +0,0 @@
|
||||
# Fabric Helpers
|
||||
|
||||
These are helper tools to work with Fabric. Examples include things like getting transcripts from media files, getting metadata about media, etc.
|
||||
|
||||
## yt (YouTube)
|
||||
|
||||
`yt` is a command that uses the YouTube API to pull transcripts, get video duration, and other functions. It's primary function is to get a transcript from a video that can then be stitched (piped) into other Fabric Patterns.
|
||||
|
||||
```bash
|
||||
usage: yt [-h] [--duration] [--transcript] [url]
|
||||
|
||||
vm (video meta) extracts metadata about a video, such as the transcript and the video's duration. By Daniel Miessler.
|
||||
|
||||
positional arguments:
|
||||
url YouTube video URL
|
||||
|
||||
options:
|
||||
-h, --help show this help message and exit
|
||||
--duration Output only the duration
|
||||
--transcript Output only the transcript
|
||||
```
|
||||
1
helpers/yt → helpers/vm
Normal file → Executable file
1
helpers/yt → helpers/vm
Normal file → Executable file
@@ -83,3 +83,4 @@ if __name__ == '__main__':
|
||||
main(args.url, args)
|
||||
else:
|
||||
parser.print_help()
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
from .utils import Standalone, Update, Setup, Alias
|
||||
from .utils import Standalone, Update, Setup, Alias, Whisper
|
||||
import argparse
|
||||
import sys
|
||||
import time
|
||||
@@ -30,6 +30,8 @@ def main():
|
||||
help="Use this option if you want to see the results in realtime. NOTE: You will not be able to pipe the output into another command.",
|
||||
action="store_true",
|
||||
)
|
||||
parser.add_argument('--transcribe', '-T',
|
||||
help="transcribe audio, please enter the path to the audio file, or a url with the audio file")
|
||||
parser.add_argument(
|
||||
"--list", "-l", help="List available patterns", action="store_true"
|
||||
)
|
||||
@@ -78,7 +80,7 @@ def main():
|
||||
standalone = Standalone(args, args.pattern)
|
||||
if args.list:
|
||||
try:
|
||||
direct = sorted(os.listdir(config_patterns_directory))
|
||||
direct = os.listdir(config_patterns_directory)
|
||||
for d in direct:
|
||||
print(d)
|
||||
sys.exit()
|
||||
@@ -88,26 +90,26 @@ def main():
|
||||
if args.listmodels:
|
||||
standalone.fetch_available_models()
|
||||
sys.exit()
|
||||
if args.transcribe:
|
||||
whisper = Whisper()
|
||||
whisper.process_file(args.transcribe)
|
||||
sys.exit()
|
||||
if args.text is not None:
|
||||
text = args.text
|
||||
else:
|
||||
text = standalone.get_cli_input()
|
||||
if args.stream and not args.context:
|
||||
standalone.streamMessage(text)
|
||||
sys.exit()
|
||||
if args.stream and args.context:
|
||||
with open(config_context, "r") as f:
|
||||
context = f.read()
|
||||
standalone.streamMessage(text, context=context)
|
||||
sys.exit()
|
||||
elif args.context:
|
||||
with open(config_context, "r") as f:
|
||||
context = f.read()
|
||||
standalone.sendMessage(text, context=context)
|
||||
sys.exit()
|
||||
else:
|
||||
standalone.sendMessage(text)
|
||||
sys.exit()
|
||||
|
||||
|
||||
if __name__ == "__main__":
|
||||
|
||||
@@ -10,6 +10,7 @@ from tqdm import tqdm
|
||||
import zipfile
|
||||
import tempfile
|
||||
import shutil
|
||||
from pydub import AudioSegment
|
||||
|
||||
current_directory = os.path.dirname(os.path.realpath(__file__))
|
||||
config_directory = os.path.expanduser("~/.config/fabric")
|
||||
@@ -84,8 +85,8 @@ class Standalone:
|
||||
return
|
||||
else:
|
||||
if context:
|
||||
messages = [
|
||||
{"role": "system", "content": context}, user_message]
|
||||
user_message += {role: "system", content: context}
|
||||
messages = [user_message]
|
||||
else:
|
||||
messages = [user_message]
|
||||
try:
|
||||
@@ -150,8 +151,8 @@ class Standalone:
|
||||
return
|
||||
else:
|
||||
if context:
|
||||
messages = [
|
||||
{'role': 'system', 'content': context}, user_message]
|
||||
user_message += {'role': 'system', 'content': context}
|
||||
messages = [user_message]
|
||||
else:
|
||||
messages = [user_message]
|
||||
try:
|
||||
@@ -215,6 +216,98 @@ class Standalone:
|
||||
return sys.stdin.read()
|
||||
|
||||
|
||||
class Whisper:
|
||||
def __init__(self):
|
||||
env_file = os.path.expanduser("~/.config/fabric/.env")
|
||||
load_dotenv(env_file)
|
||||
try:
|
||||
apikey = os.environ["OPENAI_API_KEY"]
|
||||
self.client = OpenAI()
|
||||
self.client.api_key = apikey
|
||||
except KeyError:
|
||||
print("OPENAI_API_KEY not found in environment variables.")
|
||||
|
||||
except FileNotFoundError:
|
||||
print("No API key found. Use the --apikey option to set the key")
|
||||
self.whole_response = []
|
||||
|
||||
def split_audio(self, file_path):
|
||||
"""
|
||||
Splits the audio file into segments of the given length.
|
||||
|
||||
Args:
|
||||
- file_path: The path to the audio file.
|
||||
- segment_length_ms: Length of each segment in milliseconds.
|
||||
|
||||
Returns:
|
||||
- A list of audio segments.
|
||||
"""
|
||||
audio = AudioSegment.from_file(file_path)
|
||||
segments = []
|
||||
segment_length_ms = 10 * 60 * 1000 # 10 minutes in milliseconds
|
||||
for start_ms in range(0, len(audio), segment_length_ms):
|
||||
end_ms = start_ms + segment_length_ms
|
||||
segment = audio[start_ms:end_ms]
|
||||
segments.append(segment)
|
||||
|
||||
return segments
|
||||
|
||||
def process_segment(self, segment):
|
||||
""" Transcribe an audio file and print the transcript.
|
||||
|
||||
Args:
|
||||
audio_file (str): The path to the audio file to be transcribed.
|
||||
|
||||
Returns:
|
||||
None
|
||||
"""
|
||||
|
||||
try:
|
||||
# if audio_file.startswith("http"):
|
||||
# response = requests.get(audio_file)
|
||||
# response.raise_for_status()
|
||||
# with tempfile.NamedTemporaryFile(delete=False) as f:
|
||||
# f.write(response.content)
|
||||
# audio_file = f.name
|
||||
audio_file = open(segment, "rb")
|
||||
response = self.client.audio.transcriptions.create(
|
||||
model="whisper-1",
|
||||
file=audio_file
|
||||
)
|
||||
self.whole_response.append(response.text)
|
||||
|
||||
except Exception as e:
|
||||
print(f"Error: {e}")
|
||||
|
||||
def process_file(self, audio_file):
|
||||
""" Transcribe an audio file and print the transcript.
|
||||
|
||||
Args:
|
||||
audio_file (str): The path to the audio file to be transcribed.
|
||||
|
||||
Returns:
|
||||
None
|
||||
"""
|
||||
|
||||
try:
|
||||
# if audio_file.startswith("http"):
|
||||
# response = requests.get(audio_file)
|
||||
# response.raise_for_status()
|
||||
# with tempfile.NamedTemporaryFile(delete=False) as f:
|
||||
# f.write(response.content)
|
||||
# audio_file = f.name
|
||||
|
||||
segments = self.split_audio(audio_file)
|
||||
for i, segment in enumerate(segments):
|
||||
segment_file_path = f"segment_{i}.mp3"
|
||||
segment.export(segment_file_path, format="mp3")
|
||||
self.process_segment(segment_file_path)
|
||||
print(' '.join(self.whole_response))
|
||||
|
||||
except Exception as e:
|
||||
print(f"Error: {e}")
|
||||
|
||||
|
||||
class Update:
|
||||
def __init__(self):
|
||||
"""Initialize the object with default values."""
|
||||
|
||||
@@ -1,46 +0,0 @@
|
||||
# IDENTITY and PURPOSE
|
||||
|
||||
You are an expert at creating TED-quality keynote presentations from the input provided.
|
||||
|
||||
Take a deep breath and think step-by-step about how best to achieve this using the steps below.
|
||||
|
||||
# STEPS
|
||||
|
||||
- Think about the entire narrative flow of the presentation first. Have that firmly in your mind. Then begin.
|
||||
|
||||
- Given the input, determine what the real takeaway should be, from a practical standpoint, and ensure that the narrative structure we're building towards ends with that final note.
|
||||
|
||||
- Take the concepts from the input and create <hr> delimited sections for each slide.
|
||||
|
||||
- The slide's content will be 3-5 bullets of no more than 5-10 words each.
|
||||
|
||||
- Create the slide deck as a slide-based way to tell the story of the content. Be aware of the narrative flow of the slides, and be sure you're building the story like you would for a TED talk.
|
||||
|
||||
- Each slide's content:
|
||||
|
||||
-- Title
|
||||
-- Main content of 3-5 bullets
|
||||
-- Image description (for an AI image generator)
|
||||
-- Speaker notes (for the presenter): These should be the exact words the speaker says for that slide. Give them as a set of bullets of no more than 15 words each.
|
||||
|
||||
- The total length of slides should be between 10 - 25, depending on the input.
|
||||
|
||||
# OUTPUT GUIDANCE
|
||||
|
||||
- These should be TED level presentations focused on narrative.
|
||||
|
||||
- Ensure the slides and overall presentation flows properly. If it doesn't produce a clean narrative, start over.
|
||||
|
||||
# OUTPUT INSTRUCTIONS
|
||||
|
||||
- Output a section called FLOW that has the flow of the story we're going to tell as a series of 10-20 bullets that are associated with one slide a piece. Each bullet should be 10-words max.
|
||||
|
||||
- Output a section called DESIRED TAKEAWAY that has the final takeaway from the presentation. This should be a single sentence.
|
||||
|
||||
- Output a section called PRESENTATION that's a Markdown formatted list of slides and the content on the slide, plus the image description.
|
||||
|
||||
- Ensure the speaker notes are in the voice of the speaker, i.e. they're what they're actually going to say.
|
||||
|
||||
# INPUT:
|
||||
|
||||
INPUT:
|
||||
@@ -1,155 +0,0 @@
|
||||
# IDENTITY and PURPOSE
|
||||
|
||||
You are an expert in risk and threat management and cybersecurity. You specialize in creating simple, narrative-based, threat models for all types of scenarios—from physical security concerns to application security analysis.
|
||||
|
||||
Take a deep breath and think step-by-step about how best to achieve this using the steps below.
|
||||
|
||||
# THREAT MODEL ESSAY BY DANIEL MIESSLER
|
||||
|
||||
Everyday Threat Modeling
|
||||
|
||||
Threat modeling is a superpower. When done correctly it gives you the ability to adjust your defensive behaviors based on what you’re facing in real-world scenarios. And not just for applications, or networks, or a business—but for life.
|
||||
The Difference Between Threats and Risks
|
||||
This type of threat modeling is a life skill, not just a technical skill. It’s a way to make decisions when facing multiple stressful options—a universal tool for evaluating how you should respond to danger.
|
||||
Threat Modeling is a way to think about any type of danger in an organized way.
|
||||
The problem we have as humans is that opportunity is usually coupled with risk, so the question is one of which opportunities should you take and which should you pass on. And If you want to take a certain risk, which controls should you put in place to keep the risk at an acceptable level?
|
||||
Most people are bad at responding to slow-effect danger because they don’t properly weigh the likelihood of the bad scenarios they’re facing. They’re too willing to put KGB poisoning and neighborhood-kid-theft in the same realm of likelihood. This grouping is likely to increase your stress level to astronomical levels as you imagine all the different things that could go wrong, which can lead to unwise defensive choices.
|
||||
To see what I mean, let’s look at some common security questions.
|
||||
This has nothing to do with politics.
|
||||
Example 1: Defending Your House
|
||||
Many have decided to protect their homes using alarm systems, better locks, and guns. Nothing wrong with that necessarily, but the question is how much? When do you stop? For someone who’s not thinking according to Everyday Threat Modeling, there is potential to get real extreme real fast.
|
||||
Let’s say you live in a nice suburban neighborhood in North Austin. The crime rate is extremely low, and nobody can remember the last time a home was broken into.
|
||||
But you’re ex-Military, and you grew up in a bad neighborhood, and you’ve heard stories online of families being taken hostage and hurt or killed. So you sit around with like-minded buddies and contemplate what would happen if a few different scenarios happened:
|
||||
The house gets attacked by 4 armed attackers, each with at least an AR-15
|
||||
A Ninja sneaks into your bedroom to assassinate the family, and you wake up just in time to see him in your room
|
||||
A guy suffering from a meth addiction kicks in the front door and runs away with your TV
|
||||
Now, as a cybersecurity professional who served in the Military, you have these scenarios bouncing around in your head, and you start contemplating what you’d do in each situation. And how you can be prepared.
|
||||
Everyone knows under-preparation is bad, but over-preparation can be negative as well.
|
||||
Well, looks like you might want a hidden knife under each table. At least one hidden gun in each room. Krav Maga training for all your kids starting at 10-years-old. And two modified AR-15’s in the bedroom—one for you and one for your wife.
|
||||
Every control has a cost, and it’s not always financial.
|
||||
But then you need to buy the cameras. And go to additional CQB courses for room to room combat. And you spend countless hours with your family drilling how to do room-to-room combat with an armed assailant. Also, you’ve been preparing like this for years, and you’ve spent 187K on this so far, which could have gone towards college.
|
||||
Now. It’s not that it’s bad to be prepared. And if this stuff was all free, and safe, there would be fewer reasons not to do it. The question isn’t whether it’s a good idea. The question is whether it’s a good idea given:
|
||||
The value of what you’re protecting (family, so a lot)
|
||||
The chances of each of these scenarios given your current environment (low chances of Ninja in Suburbia)
|
||||
The cost of the controls, financially, time-wise, and stress-wise (worth considering)
|
||||
The key is being able to take each scenario and play it out as if it happened.
|
||||
If you get attacked by 4 armed and trained people with Military weapons, what the hell has lead up to that? And should you not just move to somewhere safer? Or maybe work to make whoever hates you that much, hate you less? And are you and your wife really going to hold them off with your two weapons along with the kids in their pajamas?
|
||||
Think about how irresponsible you’d feel if that thing happened, and perhaps stress less about it if it would be considered a freak event.
|
||||
That and the Ninja in your bedroom are not realistic scenarios. Yes, they could happen, but would people really look down on you for being killed by a Ninja in your sleep. They’re Ninjas.
|
||||
Think about it another way: what if Russian Mafia decided to kidnap your 4th grader while she was walking home from school. They showed up with a van full of commandos and snatched her off the street for ransom (whatever).
|
||||
Would you feel bad that you didn’t make your child’s school route resistant to Russian Special Forces? You’d probably feel like that emotionally, of course, but it wouldn’t be logical.
|
||||
Maybe your kids are allergic to bee stings and you just don’t know yet.
|
||||
Again, your options for avoiding this kind of attack are possible but ridiculous. You could home-school out of fear of Special Forces attacking kids while walking home. You could move to a compound with guard towers and tripwires, and have your kids walk around in beekeeper protection while wearing a gas mask.
|
||||
Being in a constant state of worry has its own cost.
|
||||
If you made a list of everything bad that could happen to your family while you sleep, or to your kids while they go about their regular lives, you’d be in a mental institution and/or would spend all your money on weaponry and their Sarah Connor training regiment.
|
||||
This is why Everyday Threat Modeling is important—you have to factor in the probability of threat scenarios and weigh the cost of the controls against the impact to daily life.
|
||||
Example 2: Using a VPN
|
||||
A lot of people are confused about VPNs. They think it’s giving them security that it isn’t because they haven’t properly understood the tech and haven’t considered the attack scenarios.
|
||||
If you log in at the end website you’ve identified yourself to them, regardless of VPN.
|
||||
VPNs encrypt the traffic between you and some endpoint on the internet, which is where your VPN is based. From there, your traffic then travels without the VPN to its ultimate destination. And then—and this is the part that a lot of people miss—it then lands in some application, like a website. At that point you start clicking and browsing and doing whatever you do, and all those events could be logged or tracked by that entity or anyone who has access to their systems.
|
||||
It is not some stealth technology that makes you invisible online, because if invisible people type on a keyboard the letters still show up on the screen.
|
||||
Now, let’s look at who we’re defending against if you use a VPN.
|
||||
Your ISP. If your VPN includes all DNS requests and traffic then you could be hiding significantly from your ISP. This is true. They’d still see traffic amounts, and there are some technologies that allow people to infer the contents of encrypted connections, but in general this is a good control if you’re worried about your ISP.
|
||||
The Government. If the government investigates you by only looking at your ISP, and you’ve been using your VPN 24-7, you’ll be in decent shape because it’ll just be encrypted traffic to a VPN provider. But now they’ll know that whatever you were doing was sensitive enough to use a VPN at all times. So, probably not a win. Besides, they’ll likely be looking at the places you’re actually visiting as well (the sites you’re going to on the VPN), and like I talked about above, that’s when your cloaking device is useless. You have to de-cloak to fire, basically.
|
||||
Super Hackers Trying to Hack You. First, I don’t know who these super hackers are, or why they’re trying ot hack you. But if it’s a state-level hacking group (or similar elite level), and you are targeted, you’re going to get hacked unless you stop using the internet and email. It’s that simple. There are too many vulnerabilities in all systems, and these teams are too good, for you to be able to resist for long. You will eventually be hacked via phishing, social engineering, poisoning a site you already frequent, or some other technique. Focus instead on not being targeted.
|
||||
Script Kiddies. If you are just trying to avoid general hacker-types trying to hack you, well, I don’t even know what that means. Again, the main advantage you get from a VPN is obscuring your traffic from your ISP. So unless this script kiddie had access to your ISP and nothing else, this doesn’t make a ton of sense.
|
||||
Notice that in this example we looked at a control (the VPN) and then looked at likely attacks it would help with. This is the opposite of looking at the attacks (like in the house scenario) and then thinking about controls. Using Everyday Threat Modeling includes being able to do both.
|
||||
Example 3: Using Smart Speakers in the House
|
||||
This one is huge for a lot of people, and it shows the mistake I talked about when introducing the problem. Basically, many are imagining movie-plot scenarios when making the decision to use Alexa or not.
|
||||
Let’s go through the negative scenarios:
|
||||
Amazon gets hacked with all your data released
|
||||
Amazon gets hacked with very little data stolen
|
||||
A hacker taps into your Alexa and can listen to everything
|
||||
A hacker uses Alexa to do something from outside your house, like open the garage
|
||||
Someone inside the house buys something they shouldn’t
|
||||
alexaspeakers
|
||||
A quick threat model on using Alexa smart speakers (click for spreadsheet)
|
||||
If you click on the spreadsheet above you can open it in Google Sheets to see the math. It’s not that complex. The only real nuance is that Impact is measured on a scale of 1-1000 instead of 1-100. The real challenge here is not the math. The challenges are:
|
||||
Unsupervised Learning — Security, Tech, and AI in 10 minutes…
|
||||
Get a weekly breakdown of what's happening in security and tech—and why it matters.
|
||||
Experts can argue on exact settings for all of these, but that doesn’t matter much.
|
||||
Assigning the value of the feature
|
||||
Determining the scenarios
|
||||
Properly assigning probability to the scenarios
|
||||
The first one is critical. You have to know how much risk you’re willing to tolerate based on how useful that thing is to you, your family, your career, your life. The second one requires a bit of a hacker/creative mind. And the third one requires that you understand the industry and the technology to some degree.
|
||||
But the absolute most important thing here is not the exact ratings you give—it’s the fact that you’re thinking about this stuff in an organized way!
|
||||
The Everyday Threat Modeling Methodology
|
||||
Other versions of the methodology start with controls and go from there.
|
||||
So, as you can see from the spreadsheet, here’s the methodology I recommend using for Everyday Threat Modeling when you’re asking the question:
|
||||
Should I use this thing?
|
||||
Out of 1-100, determine how much value or pleasure you get from the item/feature. That’s your Value.
|
||||
Make a list of negative/attack scenarios that might make you not want to use it.
|
||||
Determine how bad it would be if each one of those happened, from 1-1000. That’s your Impact.
|
||||
Determine the chances of that realistically happening over the next, say, 10 years, as a percent chance. That’s your Likelihood.
|
||||
Multiply the Impact by the Likelihood for each scenario. That’s your Risk.
|
||||
Add up all your Risk scores. That’s your Total Risk.
|
||||
Subtract your Total Risk from your Value. If that number is positive, you are good to go. If that number is negative, it might be too risky to use based on your risk tolerance and the value of the feature.
|
||||
Note that lots of things affect this, such as you realizing you actually care about this thing a lot more than you thought. Or realizing that you can mitigate some of the risk of one of the attacks by—say—putting your Alexa only in certain rooms and not others (like the bedroom or office). Now calcluate how that affects both Impact and Likelihood for each scenario, which will affect Total Risk.
|
||||
Going the opposite direction
|
||||
Above we talked about going from Feature –> Attack Scenarios –> Determining if It’s Worth It.
|
||||
But there’s another version of this where you start with a control question, such as:
|
||||
What’s more secure, typing a password into my phone, using my fingerprint, or using facial recognition?
|
||||
Here we’re not deciding whether or not to use a phone. Yes, we’re going to use one. Instead we’re figuring out what type of security is best. And that—just like above—requires us to think clearly about the scenarios we’re facing.
|
||||
So let’s look at some attacks against your phone:
|
||||
A Russian Spetztaz Ninja wants to gain access to your unlocked phone
|
||||
Your 7-year old niece wants to play games on your work phone
|
||||
Your boyfriend wants to spy on your DMs with other people
|
||||
Someone in Starbucks is shoulder surfing and being nosy
|
||||
You accidentally leave your phone in a public place
|
||||
We won’t go through all the math on this, but the Russian Ninja scenario is really bad. And really unlikely. They’re more likely to steal you and the phone, and quickly find a way to make you unlock it for them. So your security measure isn’t going to help there.
|
||||
For your niece, kids are super smart about watching you type your password, so she might be able to get into it easily just by watching you do it a couple of times. Same with someone shoulder surfing at Starbucks, but you have to ask yourself who’s going to risk stealing your phone and logging into it at Starbucks. Is this a stalker? A criminal? What type? You have to factor in all those probabilities.
|
||||
First question, why are you with them?
|
||||
If your significant other wants to spy on your DMs, well they most definitely have had an opportunity to shoulder surf a passcode. But could they also use your finger while you slept? Maybe face recognition could be the best because it’d be obvious to you?
|
||||
For all of these, you want to assign values based on how often you’re in those situations. How often you’re in Starbucks, how often you have kids around, how stalkerish your soon-to-be-ex is. Etc.
|
||||
Once again, the point is to think about this in an organized way, rather than as a mashup of scenarios with no probabilities assigned that you can’t keep straight in your head. Logic vs. emotion.
|
||||
It’s a way of thinking about danger.
|
||||
Other examples
|
||||
Here are a few other examples that you might come across.
|
||||
Should I put my address on my public website?
|
||||
How bad is it to be a public figure (blog/YouTube) in 2020?
|
||||
Do I really need to shred this bill when I throw it away?
|
||||
Don’t ever think you’ve captured all the scenarios, or that you have a perfect model.
|
||||
In each of these, and the hundreds of other similar scenarios, go through the methodology. Even if you don’t get to something perfect or precise, you will at least get some clarity in what the problem is and how to think about it.
|
||||
Summary
|
||||
Threat Modeling is about more than technical defenses—it’s a way of thinking about risk.
|
||||
The main mistake people make when considering long-term danger is letting different bad outcomes produce confusion and anxiety.
|
||||
When you think about defense, start with thinking about what you’re defending, and how valuable it is.
|
||||
Then capture the exact scenarios you’re worried about, along with how bad it would be if they happened, and what you think the chances are of them happening.
|
||||
You can then think about additional controls as modifiers to the Impact or Probability ratings within each scenario.
|
||||
Know that your calculation will never be final; it changes based on your own preferences and the world around you.
|
||||
The primary benefit of Everyday Threat Modeling is having a semi-formal way of thinking about danger.
|
||||
Don’t worry about the specifics of your methodology; as long as you capture feature value, scenarios, and impact/probability…you’re on the right path. It’s the exercise that’s valuable.
|
||||
Notes
|
||||
I know Threat Modeling is a religion with many denominations. The version of threat modeling I am discussing here is a general approach that can be used for anything from whether to move out of the country due to a failing government, or what appsec controls to use on a web application.
|
||||
|
||||
END THREAT MODEL ESSAY
|
||||
|
||||
# STEPS
|
||||
|
||||
- Fully understand the threat modeling approach captured in the blog above. That is the mentality you use to create threat models.
|
||||
|
||||
- Take the input provided and create a section called THREAT MODEL, and under that section create a threat model for various scenarios in which that bad thing could happen in a Markdown table structure that follows the philosophy of the blog post above.
|
||||
|
||||
- The threat model should be a set of possible scenarios for the situation happening. The goal is to highlight what's realistic vs. possible, and what's worth defending against vs. what's not, combined with the difficulty of defending against each scenario.
|
||||
|
||||
- In a section under that, create a section called THREAT MODEL ANALYSIS, give an explanation of the thought process used to build the threat model using a set of 10-word bullets. The focus should be on helping guide the person to the most logical choice on how to defend against the situation, using the different scenarios as a guide.
|
||||
|
||||
# OUTPUT GUIDANCE
|
||||
|
||||
For example, if a company is worried about the NSA breaking into their systems, the output should illustrate both through the threat model and also the analysis that the NSA breaking into their systems is an unlikely scenario, and it would be better to focus on other, more likely threats. Plus it'd be hard to defend against anyway.
|
||||
|
||||
Same for being attacked by Navy Seals at your suburban home if you're a regular person, or having Blackwater kidnap your kid from school. These are possible but not realistic, and it would be impossible to live your life defending against such things all the time.
|
||||
|
||||
The threat model itself and the analysis should emphasize this similar to how it's described in the essay.
|
||||
|
||||
# OUTPUT INSTRUCTIONS
|
||||
|
||||
- You only output valid Markdown.
|
||||
|
||||
- Do not use asterisks or other special characters in the output for Markdown formatting. Use Markdown syntax that's more readable in plain text.
|
||||
|
||||
- Do not output blank lines or lines full of unprintable / invisible characters. Only output the printable portion of the ASCII art.
|
||||
|
||||
# INPUT:
|
||||
|
||||
INPUT:
|
||||
@@ -1,62 +0,0 @@
|
||||
# IDENTITY and PURPOSE
|
||||
|
||||
You are an expert conversation topic and timestamp creator. You take a transcript and you extract the most interesting topics discussed and give timestamps for where in the video they occur.
|
||||
|
||||
Take a step back and think step-by-step about how you would do this. You would probably start by "watching" the video (via the transcript) and taking notes on the topics discussed and the time they were discussed. Then you would take those notes and create a list of topics and timestamps.
|
||||
|
||||
# STEPS
|
||||
|
||||
- Fully consume the transcript as if you're watching or listening to the content.
|
||||
|
||||
- Think deeply about the topics discussed and what were the most interesting subjects and moments in the content.
|
||||
|
||||
- Name those subjects and/moments in 2-3 capitalized words.
|
||||
|
||||
- Match the timestamps to the topics. Note that input timestamps have the following format: HOURS:MINUTES:SECONDS.MILLISECONDS, which is not the same as the OUTPUT format!
|
||||
|
||||
INPUT SAMPLE
|
||||
|
||||
[02:17:43.120 --> 02:17:49.200] same way. I'll just say the same. And I look forward to hearing the response to my job application
|
||||
[02:17:49.200 --> 02:17:55.040] that I've submitted. Oh, you're accepted. Oh, yeah. We all speak of you all the time. Thank you so
|
||||
[02:17:55.040 --> 02:18:00.720] much. Thank you, guys. Thank you. Thanks for listening to this conversation with Neri Oxman.
|
||||
[02:18:00.720 --> 02:18:05.520] To support this podcast, please check out our sponsors in the description. And now,
|
||||
|
||||
END INPUT SAMPLE
|
||||
|
||||
The OUTPUT TIMESTAMP format is:
|
||||
00:00:00 (HOURS:MINUTES:SECONDS) (HH:MM:SS)
|
||||
|
||||
- Note the maximum length of the video based on the last timestamp.
|
||||
|
||||
- Ensure all output timestamps are sequential and fall within the length of the content.
|
||||
|
||||
# OUTPUT INSTRUCTIONS
|
||||
|
||||
EXAMPLE OUTPUT (Hours:Minutes:Seconds)
|
||||
|
||||
00:00:00 Members-only Forum Access
|
||||
00:00:10 Live Hacking Demo
|
||||
00:00:26 Ideas vs. Book
|
||||
00:00:30 Meeting Will Smith
|
||||
00:00:44 How to Influence Others
|
||||
00:01:34 Learning by Reading
|
||||
00:58:30 Writing With Punch
|
||||
00:59:22 100 Posts or GTFO
|
||||
01:00:32 How to Gain Followers
|
||||
01:01:31 The Music That Shapes
|
||||
01:27:21 Subdomain Enumeration Demo
|
||||
01:28:40 Hiding in Plain Sight
|
||||
01:29:06 The Universe Machine
|
||||
00:09:36 Early School Experiences
|
||||
00:10:12 The First Business Failure
|
||||
00:10:32 David Foster Wallace
|
||||
00:12:07 Copying Other Writers
|
||||
00:12:32 Practical Advice for N00bs
|
||||
|
||||
END EXAMPLE OUTPUT
|
||||
|
||||
- Ensure all output timestamps are sequential and fall within the length of the content, e.g., if the total length of the video is 24 minutes. (00:00:00 - 00:24:00), then no output can be 01:01:25, or anything over 00:25:00 or over!
|
||||
|
||||
- ENSURE the output timestamps and topics are shown gradually and evenly incrementing from 00:00:00 to the final timestamp of the content.
|
||||
|
||||
INPUT:
|
||||
@@ -1,51 +0,0 @@
|
||||
# IDENTITY and PURPOSE
|
||||
|
||||
You are an expert at data and concept visualization and in turning complex ideas into a form that can be visualized using ASCII art.
|
||||
|
||||
You take input of any type and find the best way to simply visualize or demonstrate the core ideas using ASCII art.
|
||||
|
||||
You always output ASCII art, even if you have to simplify the input concepts to a point where it can be visualized using ASCII art.
|
||||
|
||||
# STEPS
|
||||
|
||||
- Take the input given and create a visualization that best explains it using elaborate and intricate ASCII art.
|
||||
|
||||
- Ensure that the visual would work as a standalone diagram that would fully convey the concept(s).
|
||||
|
||||
- Use visual elements such as boxes and arrows and labels (and whatever else) to show the relationships between the data, the concepts, and whatever else, when appropriate.
|
||||
|
||||
- Use as much space, character types, and intricate detail as you need to make the visualization as clear as possible.
|
||||
|
||||
- Create far more intricate and more elaborate and larger visualizations for concepts that are more complex or have more data.
|
||||
|
||||
- Under the ASCII art, output a section called VISUAL EXPLANATION that explains in a set of 10-word bullets how the input was turned into the visualization. Ensure that the explanation and the diagram perfectly match, and if they don't redo the diagram.
|
||||
|
||||
- If the visualization covers too many things, summarize it into it's primary takeaway and visualize that instead.
|
||||
|
||||
- DO NOT COMPLAIN AND GIVE UP. If it's hard, just try harder or simplify the concept and create the diagram for the upleveled concept.
|
||||
|
||||
- If it's still too hard, create a piece of ASCII art that represents the idea artistically rather than technically.
|
||||
|
||||
# OUTPUT INSTRUCTIONS
|
||||
|
||||
- DO NOT COMPLAIN. Just make an image. If it's too complex for a simple ASCII image, reduce the image's complexity until it can be rendered using ASCII.
|
||||
|
||||
- DO NOT COMPLAIN. Make a printable image no matter what.
|
||||
|
||||
- Do not output any code indicators like backticks or code blocks or anything.
|
||||
|
||||
- You only ouptut the printable portion of the ASCII art. You do not ouptut the non-printable characters.
|
||||
|
||||
- Ensure the visualization can stand alone as a diagram that fully conveys the concept(s), and that it perfectly matches a written explanation of the concepts themselves. Start over if it can't.
|
||||
|
||||
- Ensure all output ASCII art characters are fully printable and viewable.
|
||||
|
||||
- Ensure the diagram will fit within a reasonable width in a large window, so the viewer won't have to reduce the font like 1000 times.
|
||||
|
||||
- Create a diagram no matter what, using the STEPS above to determine which type.
|
||||
|
||||
- Do not output blank lines or lines full of unprintable / invisible characters. Only output the printable portion of the ASCII art.
|
||||
|
||||
# INPUT:
|
||||
|
||||
INPUT:
|
||||
@@ -23,7 +23,7 @@ Take a step back and think step-by-step about how to achieve the best possible r
|
||||
# OUTPUT INSTRUCTIONS
|
||||
|
||||
- Only output Markdown.
|
||||
- Extract at least 20 IDEAS from the content.
|
||||
- Extract at least 20 ideas from the content.
|
||||
- Extract at least 10 items for the other output sections.
|
||||
- Do not give warnings or notes; only output the requested sections.
|
||||
- You use bulleted lists for output, not numbered lists.
|
||||
|
||||
@@ -1,71 +0,0 @@
|
||||
# IDENTITY AND GOALS
|
||||
|
||||
You are an expert in political propaganda, analysis of hidden messages in conversations and essays, population control through speech and writing, and political narrative creation.
|
||||
|
||||
You consume input and cynically evaluate what's being said to find the overt vs. hidden political messages.
|
||||
|
||||
Take a step back and think step-by-step about how to evaluate the input and what the true intentions of the speaker are.
|
||||
|
||||
# STEPS
|
||||
|
||||
- Using all your knowledge of language, politics, history, propaganda, and human psychology, slowly evaluate the input and think about the true underlying political message is behind the content.
|
||||
|
||||
- Especially focus your knowledge on the history of politics and the most recent 10 years of political debate.
|
||||
|
||||
# OUTPUT
|
||||
|
||||
- In a section called OVERT MESSAGE, output a single 15-word sentence that captures the message that the user is OVERTLY talking about.
|
||||
|
||||
- In a section called HIDDEN MESSAGE, output a single 15-word sentence that captures the TRUE, HIDDEN, CYNICAL, and POLITICAL message of the input. E.g.: "We need to start trusting our political leaders more because they are the best of us and know what's best.", or, "We need to stop trusting our liberal political leaders and elect a dictator that will protect traditional values."
|
||||
|
||||
- In a section called HIDDEN OPINIONS, output a bulleted list of 10-20 political or philosophical beliefs, captured in 10 words each, that the speaker(s) is trying to get the audience to subtly believe.
|
||||
|
||||
- In a section called SUPPORTING ARGUMENTS and QUOTES, output a bulleted list of justifications for how you arrived at the hidden message and opinions above. Use logic, argument, and quotes as the support content for each bullet.
|
||||
|
||||
- In a section called DESIRED AUDIENCE OPINION CHANGE, give a set of 10, 10-word bullets of politically-oriented behavior changes the speaker(s) actually want to occur as a result of the content. These should be deeply political and tangible.
|
||||
|
||||
- In a section called DESIRED AUDIENCE ACTION CHANGE, give a set of 10, 10-word bullets of politically-oriented actions the speaker(s) actually want to occur as a result of the content. These should be tangible and real-world.
|
||||
|
||||
- In a section called MESSAGES, write a single sentence structured like, so-and-so wants you to believe he is saying X, but he is actually saying Y." Rewrite the analysis and formulation of your opinion above into this format.
|
||||
|
||||
- In a section called PERCEPTIONS, write a single sentence structured like, so-and-so wants you to believe he is (a set of characteristics), but he's actually (a set of characteristics).
|
||||
|
||||
EXAMPLES OF DESIRED AUDIENCE ACTION CHANGE:
|
||||
|
||||
- Trust the government less.
|
||||
|
||||
- Vote for democrats.
|
||||
|
||||
- Vote for republicans.
|
||||
|
||||
- Trust the government more.
|
||||
|
||||
- Be less trusting of politicians.
|
||||
|
||||
- Be less skeptical of politicians.
|
||||
|
||||
- Remember that government is there to keep you safe, so you should trust it.
|
||||
|
||||
- Be more accepting of authoritarian leaders.
|
||||
|
||||
- Be more accepting of technology in their lives.
|
||||
|
||||
- Get your kids out of schools because they're government training camps.
|
||||
|
||||
END EXAMPLES OF DESIRED AUDIENCE CHANGE
|
||||
|
||||
# OUTPUT INSTRUCTIONS
|
||||
|
||||
- Only output valid Markdown.
|
||||
|
||||
- Do not output any asterisks, which are used for italicizing and bolding text.
|
||||
|
||||
- Do not output any content other than the sections above.
|
||||
|
||||
- Do not complain about the instructions. Just do what is asked above.
|
||||
|
||||
- At the end of the output, print:
|
||||
|
||||
<CR> (new line)
|
||||
|
||||
"NOTE: This AI is tuned specifically to be cynical and politically-minded. Don't take it as perfect. Run it multiple times and/or go consume the original input to get a second opinion.
|
||||
@@ -52,24 +52,15 @@ Explanation: $$Explanation in 5 short bullets for why you gave that score.$$
|
||||
|
||||
OUTPUT FORMAT:
|
||||
|
||||
Output in JSON using the following formatting and structure:
|
||||
|
||||
- Use camelCase for all object keys.
|
||||
- Ensure proper indentation for readability.
|
||||
- Each nested level should be indented with four spaces or one tab.
|
||||
- Wrap strings in double quotes.
|
||||
- Separate key-value pairs with a colon followed by a space.
|
||||
- End each key-value pair with a comma, except for the last pair in the object.
|
||||
- Enclose the entire JSON object in curly braces.
|
||||
- Check the final format for any syntax errors or missing punctuation.
|
||||
Your output is ONLY in JSON. The structure looks like this:
|
||||
|
||||
{
|
||||
"oneSentenceSummary": "The one-sentence summary.",
|
||||
"one-sentence-summary": "The one-sentence summary.",
|
||||
"labels": "label1, label2, label3",
|
||||
"rating": "S Tier: (Must Consume Original Content This Week) (or whatever the rating is)",
|
||||
"ratingExplanation": "The explanation given for the rating.",
|
||||
"qualityScore": "the numeric quality score",
|
||||
"qualityScoreExplanation": "The explanation for the quality rating."
|
||||
"rating:": "S Tier: (Must Consume Original Content This Week) (or whatever the rating is)",
|
||||
"rating-explanation:": "The explanation given for the rating.",
|
||||
"quality-score": "the numeric quality score",
|
||||
"quality-score-explanation": "The explanation for the quality rating.",
|
||||
}
|
||||
|
||||
ONLY OUTPUT THE JSON OBJECT ABOVE.
|
||||
|
||||
@@ -1,14 +1,10 @@
|
||||
# IDENTITY and PURPOSE
|
||||
|
||||
You are an expert summarizer of role-playing game sessions. Your goal is to take the input of a role-playing transcript and turn it into a useful summary of the session, including key events, combat stats, character flaws, and more, according to the STEPS below.
|
||||
You are an expert summarizer of role-playing game sessions. You can take a transcript of a session and turn it into a useful summary of the session, including key events, combat stats, character flaws, and more.
|
||||
|
||||
Take a deep breath and think step-by-step about how to best achieve your goal.
|
||||
Take a deep breath and think step-by-step about how to take the provided input text/transcript and turn it into a useful summary of the role-playing session described within.
|
||||
|
||||
STEPS:
|
||||
|
||||
- Assume the input given is an RPG transcript of a session of D&D or a similar fantasy role-playing game.
|
||||
|
||||
- Do not complain about not being able to to do what you're asked. Just do it.
|
||||
You use a narration format that's entertaining and appropriate for the genre of fantasy role-playing games, kind of similar to the style that a narrator for a movie would use to set up the sequel to that adventure.
|
||||
|
||||
OUTPUT:
|
||||
|
||||
@@ -89,14 +85,20 @@ Give the perfect piece of art description in up to 500 words to accompany the SE
|
||||
|
||||
OUTPUT INSTRUCTIONS:
|
||||
|
||||
- Ensure the Previously On output focuses on the recent episode, just the background from before.
|
||||
Ensure the Previously On output focuses on the recent episode, just the background from before.
|
||||
|
||||
- Ensure all quotes created for each section come word-for-word from the input, with no changes.
|
||||
All quotes must come directly from the input/transcript. Do not generate any quotes yourself!
|
||||
|
||||
- Do not complain about anything, just give the output as requested.
|
||||
Ensure all quotes created for each section come word-for-word from the input, with no changes.
|
||||
|
||||
- Create the summary.
|
||||
Do not hallucinate or make up quotes.
|
||||
|
||||
Only use the dialog from the transcript/input.
|
||||
|
||||
ENSURE ALL OUTPUT QUOTES COME DIRECTLY FROM THE PROVIDED INPUT
|
||||
|
||||
Do not complain about anything, just give the output as requested.
|
||||
|
||||
# INPUT
|
||||
|
||||
RPG SESSION TRANSCRIPT:
|
||||
SESSION INPUT:
|
||||
|
||||
79
poetry.lock
generated
79
poetry.lock
generated
@@ -261,43 +261,43 @@ files = [
|
||||
|
||||
[[package]]
|
||||
name = "cryptography"
|
||||
version = "42.0.4"
|
||||
version = "42.0.2"
|
||||
description = "cryptography is a package which provides cryptographic recipes and primitives to Python developers."
|
||||
optional = false
|
||||
python-versions = ">=3.7"
|
||||
files = [
|
||||
{file = "cryptography-42.0.4-cp37-abi3-macosx_10_12_universal2.whl", hash = "sha256:ffc73996c4fca3d2b6c1c8c12bfd3ad00def8621da24f547626bf06441400449"},
|
||||
{file = "cryptography-42.0.4-cp37-abi3-macosx_10_12_x86_64.whl", hash = "sha256:db4b65b02f59035037fde0998974d84244a64c3265bdef32a827ab9b63d61b18"},
|
||||
{file = "cryptography-42.0.4-cp37-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:dad9c385ba8ee025bb0d856714f71d7840020fe176ae0229de618f14dae7a6e2"},
|
||||
{file = "cryptography-42.0.4-cp37-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:69b22ab6506a3fe483d67d1ed878e1602bdd5912a134e6202c1ec672233241c1"},
|
||||
{file = "cryptography-42.0.4-cp37-abi3-manylinux_2_28_aarch64.whl", hash = "sha256:e09469a2cec88fb7b078e16d4adec594414397e8879a4341c6ace96013463d5b"},
|
||||
{file = "cryptography-42.0.4-cp37-abi3-manylinux_2_28_x86_64.whl", hash = "sha256:3e970a2119507d0b104f0a8e281521ad28fc26f2820687b3436b8c9a5fcf20d1"},
|
||||
{file = "cryptography-42.0.4-cp37-abi3-musllinux_1_1_aarch64.whl", hash = "sha256:e53dc41cda40b248ebc40b83b31516487f7db95ab8ceac1f042626bc43a2f992"},
|
||||
{file = "cryptography-42.0.4-cp37-abi3-musllinux_1_1_x86_64.whl", hash = "sha256:c3a5cbc620e1e17009f30dd34cb0d85c987afd21c41a74352d1719be33380885"},
|
||||
{file = "cryptography-42.0.4-cp37-abi3-musllinux_1_2_aarch64.whl", hash = "sha256:6bfadd884e7280df24d26f2186e4e07556a05d37393b0f220a840b083dc6a824"},
|
||||
{file = "cryptography-42.0.4-cp37-abi3-musllinux_1_2_x86_64.whl", hash = "sha256:01911714117642a3f1792c7f376db572aadadbafcd8d75bb527166009c9f1d1b"},
|
||||
{file = "cryptography-42.0.4-cp37-abi3-win32.whl", hash = "sha256:fb0cef872d8193e487fc6bdb08559c3aa41b659a7d9be48b2e10747f47863925"},
|
||||
{file = "cryptography-42.0.4-cp37-abi3-win_amd64.whl", hash = "sha256:c1f25b252d2c87088abc8bbc4f1ecbf7c919e05508a7e8628e6875c40bc70923"},
|
||||
{file = "cryptography-42.0.4-cp39-abi3-macosx_10_12_universal2.whl", hash = "sha256:15a1fb843c48b4a604663fa30af60818cd28f895572386e5f9b8a665874c26e7"},
|
||||
{file = "cryptography-42.0.4-cp39-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:a1327f280c824ff7885bdeef8578f74690e9079267c1c8bd7dc5cc5aa065ae52"},
|
||||
{file = "cryptography-42.0.4-cp39-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:6ffb03d419edcab93b4b19c22ee80c007fb2d708429cecebf1dd3258956a563a"},
|
||||
{file = "cryptography-42.0.4-cp39-abi3-manylinux_2_28_aarch64.whl", hash = "sha256:1df6fcbf60560d2113b5ed90f072dc0b108d64750d4cbd46a21ec882c7aefce9"},
|
||||
{file = "cryptography-42.0.4-cp39-abi3-manylinux_2_28_x86_64.whl", hash = "sha256:44a64043f743485925d3bcac548d05df0f9bb445c5fcca6681889c7c3ab12764"},
|
||||
{file = "cryptography-42.0.4-cp39-abi3-musllinux_1_1_aarch64.whl", hash = "sha256:3c6048f217533d89f2f8f4f0fe3044bf0b2090453b7b73d0b77db47b80af8dff"},
|
||||
{file = "cryptography-42.0.4-cp39-abi3-musllinux_1_1_x86_64.whl", hash = "sha256:6d0fbe73728c44ca3a241eff9aefe6496ab2656d6e7a4ea2459865f2e8613257"},
|
||||
{file = "cryptography-42.0.4-cp39-abi3-musllinux_1_2_aarch64.whl", hash = "sha256:887623fe0d70f48ab3f5e4dbf234986b1329a64c066d719432d0698522749929"},
|
||||
{file = "cryptography-42.0.4-cp39-abi3-musllinux_1_2_x86_64.whl", hash = "sha256:ce8613beaffc7c14f091497346ef117c1798c202b01153a8cc7b8e2ebaaf41c0"},
|
||||
{file = "cryptography-42.0.4-cp39-abi3-win32.whl", hash = "sha256:810bcf151caefc03e51a3d61e53335cd5c7316c0a105cc695f0959f2c638b129"},
|
||||
{file = "cryptography-42.0.4-cp39-abi3-win_amd64.whl", hash = "sha256:a0298bdc6e98ca21382afe914c642620370ce0470a01e1bef6dd9b5354c36854"},
|
||||
{file = "cryptography-42.0.4-pp310-pypy310_pp73-macosx_10_12_x86_64.whl", hash = "sha256:5f8907fcf57392cd917892ae83708761c6ff3c37a8e835d7246ff0ad251d9298"},
|
||||
{file = "cryptography-42.0.4-pp310-pypy310_pp73-manylinux_2_28_aarch64.whl", hash = "sha256:12d341bd42cdb7d4937b0cabbdf2a94f949413ac4504904d0cdbdce4a22cbf88"},
|
||||
{file = "cryptography-42.0.4-pp310-pypy310_pp73-manylinux_2_28_x86_64.whl", hash = "sha256:1cdcdbd117681c88d717437ada72bdd5be9de117f96e3f4d50dab3f59fd9ab20"},
|
||||
{file = "cryptography-42.0.4-pp310-pypy310_pp73-win_amd64.whl", hash = "sha256:0e89f7b84f421c56e7ff69f11c441ebda73b8a8e6488d322ef71746224c20fce"},
|
||||
{file = "cryptography-42.0.4-pp39-pypy39_pp73-macosx_10_12_x86_64.whl", hash = "sha256:f1e85a178384bf19e36779d91ff35c7617c885da487d689b05c1366f9933ad74"},
|
||||
{file = "cryptography-42.0.4-pp39-pypy39_pp73-manylinux_2_28_aarch64.whl", hash = "sha256:d2a27aca5597c8a71abbe10209184e1a8e91c1fd470b5070a2ea60cafec35bcd"},
|
||||
{file = "cryptography-42.0.4-pp39-pypy39_pp73-manylinux_2_28_x86_64.whl", hash = "sha256:4e36685cb634af55e0677d435d425043967ac2f3790ec652b2b88ad03b85c27b"},
|
||||
{file = "cryptography-42.0.4-pp39-pypy39_pp73-win_amd64.whl", hash = "sha256:f47be41843200f7faec0683ad751e5ef11b9a56a220d57f300376cd8aba81660"},
|
||||
{file = "cryptography-42.0.4.tar.gz", hash = "sha256:831a4b37accef30cccd34fcb916a5d7b5be3cbbe27268a02832c3e450aea39cb"},
|
||||
{file = "cryptography-42.0.2-cp37-abi3-macosx_10_12_universal2.whl", hash = "sha256:701171f825dcab90969596ce2af253143b93b08f1a716d4b2a9d2db5084ef7be"},
|
||||
{file = "cryptography-42.0.2-cp37-abi3-macosx_10_12_x86_64.whl", hash = "sha256:61321672b3ac7aade25c40449ccedbc6db72c7f5f0fdf34def5e2f8b51ca530d"},
|
||||
{file = "cryptography-42.0.2-cp37-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:ea2c3ffb662fec8bbbfce5602e2c159ff097a4631d96235fcf0fb00e59e3ece4"},
|
||||
{file = "cryptography-42.0.2-cp37-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:3b15c678f27d66d247132cbf13df2f75255627bcc9b6a570f7d2fd08e8c081d2"},
|
||||
{file = "cryptography-42.0.2-cp37-abi3-manylinux_2_28_aarch64.whl", hash = "sha256:8e88bb9eafbf6a4014d55fb222e7360eef53e613215085e65a13290577394529"},
|
||||
{file = "cryptography-42.0.2-cp37-abi3-manylinux_2_28_x86_64.whl", hash = "sha256:a047682d324ba56e61b7ea7c7299d51e61fd3bca7dad2ccc39b72bd0118d60a1"},
|
||||
{file = "cryptography-42.0.2-cp37-abi3-musllinux_1_1_aarch64.whl", hash = "sha256:36d4b7c4be6411f58f60d9ce555a73df8406d484ba12a63549c88bd64f7967f1"},
|
||||
{file = "cryptography-42.0.2-cp37-abi3-musllinux_1_1_x86_64.whl", hash = "sha256:a00aee5d1b6c20620161984f8ab2ab69134466c51f58c052c11b076715e72929"},
|
||||
{file = "cryptography-42.0.2-cp37-abi3-musllinux_1_2_aarch64.whl", hash = "sha256:b97fe7d7991c25e6a31e5d5e795986b18fbbb3107b873d5f3ae6dc9a103278e9"},
|
||||
{file = "cryptography-42.0.2-cp37-abi3-musllinux_1_2_x86_64.whl", hash = "sha256:5fa82a26f92871eca593b53359c12ad7949772462f887c35edaf36f87953c0e2"},
|
||||
{file = "cryptography-42.0.2-cp37-abi3-win32.whl", hash = "sha256:4b063d3413f853e056161eb0c7724822a9740ad3caa24b8424d776cebf98e7ee"},
|
||||
{file = "cryptography-42.0.2-cp37-abi3-win_amd64.whl", hash = "sha256:841ec8af7a8491ac76ec5a9522226e287187a3107e12b7d686ad354bb78facee"},
|
||||
{file = "cryptography-42.0.2-cp39-abi3-macosx_10_12_universal2.whl", hash = "sha256:55d1580e2d7e17f45d19d3b12098e352f3a37fe86d380bf45846ef257054b242"},
|
||||
{file = "cryptography-42.0.2-cp39-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:28cb2c41f131a5758d6ba6a0504150d644054fd9f3203a1e8e8d7ac3aea7f73a"},
|
||||
{file = "cryptography-42.0.2-cp39-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:b9097a208875fc7bbeb1286d0125d90bdfed961f61f214d3f5be62cd4ed8a446"},
|
||||
{file = "cryptography-42.0.2-cp39-abi3-manylinux_2_28_aarch64.whl", hash = "sha256:44c95c0e96b3cb628e8452ec060413a49002a247b2b9938989e23a2c8291fc90"},
|
||||
{file = "cryptography-42.0.2-cp39-abi3-manylinux_2_28_x86_64.whl", hash = "sha256:2f9f14185962e6a04ab32d1abe34eae8a9001569ee4edb64d2304bf0d65c53f3"},
|
||||
{file = "cryptography-42.0.2-cp39-abi3-musllinux_1_1_aarch64.whl", hash = "sha256:09a77e5b2e8ca732a19a90c5bca2d124621a1edb5438c5daa2d2738bfeb02589"},
|
||||
{file = "cryptography-42.0.2-cp39-abi3-musllinux_1_1_x86_64.whl", hash = "sha256:ad28cff53f60d99a928dfcf1e861e0b2ceb2bc1f08a074fdd601b314e1cc9e0a"},
|
||||
{file = "cryptography-42.0.2-cp39-abi3-musllinux_1_2_aarch64.whl", hash = "sha256:130c0f77022b2b9c99d8cebcdd834d81705f61c68e91ddd614ce74c657f8b3ea"},
|
||||
{file = "cryptography-42.0.2-cp39-abi3-musllinux_1_2_x86_64.whl", hash = "sha256:fa3dec4ba8fb6e662770b74f62f1a0c7d4e37e25b58b2bf2c1be4c95372b4a33"},
|
||||
{file = "cryptography-42.0.2-cp39-abi3-win32.whl", hash = "sha256:3dbd37e14ce795b4af61b89b037d4bc157f2cb23e676fa16932185a04dfbf635"},
|
||||
{file = "cryptography-42.0.2-cp39-abi3-win_amd64.whl", hash = "sha256:8a06641fb07d4e8f6c7dda4fc3f8871d327803ab6542e33831c7ccfdcb4d0ad6"},
|
||||
{file = "cryptography-42.0.2-pp310-pypy310_pp73-macosx_10_12_x86_64.whl", hash = "sha256:087887e55e0b9c8724cf05361357875adb5c20dec27e5816b653492980d20380"},
|
||||
{file = "cryptography-42.0.2-pp310-pypy310_pp73-manylinux_2_28_aarch64.whl", hash = "sha256:a7ef8dd0bf2e1d0a27042b231a3baac6883cdd5557036f5e8df7139255feaac6"},
|
||||
{file = "cryptography-42.0.2-pp310-pypy310_pp73-manylinux_2_28_x86_64.whl", hash = "sha256:4383b47f45b14459cab66048d384614019965ba6c1a1a141f11b5a551cace1b2"},
|
||||
{file = "cryptography-42.0.2-pp310-pypy310_pp73-win_amd64.whl", hash = "sha256:fbeb725c9dc799a574518109336acccaf1303c30d45c075c665c0793c2f79a7f"},
|
||||
{file = "cryptography-42.0.2-pp39-pypy39_pp73-macosx_10_12_x86_64.whl", hash = "sha256:320948ab49883557a256eab46149df79435a22d2fefd6a66fe6946f1b9d9d008"},
|
||||
{file = "cryptography-42.0.2-pp39-pypy39_pp73-manylinux_2_28_aarch64.whl", hash = "sha256:5ef9bc3d046ce83c4bbf4c25e1e0547b9c441c01d30922d812e887dc5f125c12"},
|
||||
{file = "cryptography-42.0.2-pp39-pypy39_pp73-manylinux_2_28_x86_64.whl", hash = "sha256:52ed9ebf8ac602385126c9a2fe951db36f2cb0c2538d22971487f89d0de4065a"},
|
||||
{file = "cryptography-42.0.2-pp39-pypy39_pp73-win_amd64.whl", hash = "sha256:141e2aa5ba100d3788c0ad7919b288f89d1fe015878b9659b307c9ef867d3a65"},
|
||||
{file = "cryptography-42.0.2.tar.gz", hash = "sha256:e0ec52ba3c7f1b7d813cd52649a5b3ef1fc0d433219dc8c93827c57eab6cf888"},
|
||||
]
|
||||
|
||||
[package.dependencies]
|
||||
@@ -933,6 +933,17 @@ files = [
|
||||
[package.dependencies]
|
||||
typing-extensions = ">=4.6.0,<4.7.0 || >4.7.0"
|
||||
|
||||
[[package]]
|
||||
name = "pydub"
|
||||
version = "0.25.1"
|
||||
description = "Manipulate audio with an simple and easy high level interface"
|
||||
optional = false
|
||||
python-versions = "*"
|
||||
files = [
|
||||
{file = "pydub-0.25.1-py2.py3-none-any.whl", hash = "sha256:65617e33033874b59d87db603aa1ed450633288aefead953b30bded59cb599a6"},
|
||||
{file = "pydub-0.25.1.tar.gz", hash = "sha256:980a33ce9949cab2a569606b65674d748ecbca4f0796887fd6f46173a7b0d30f"},
|
||||
]
|
||||
|
||||
[[package]]
|
||||
name = "pyjwt"
|
||||
version = "2.8.0"
|
||||
@@ -1394,4 +1405,4 @@ testing = ["coverage (>=5.0.3)", "zope.event", "zope.testing"]
|
||||
[metadata]
|
||||
lock-version = "2.0"
|
||||
python-versions = "^3.10"
|
||||
content-hash = "8aa1e3fe70b9d326a7809abd70f2d78fee286d5106ab40f7d2d61a7feaf359ef"
|
||||
content-hash = "b8025aa005b3ad74c5e76f766c9311f2fa0592d4672e7f6e328d5f27001554aa"
|
||||
|
||||
@@ -32,6 +32,7 @@ gunicorn = "^21.2.0"
|
||||
gevent = "^23.9.1"
|
||||
httpx = "^0.26.0"
|
||||
tqdm = "^4.66.1"
|
||||
pydub = "^0.25.1"
|
||||
|
||||
|
||||
[tool.poetry.group.server.dependencies]
|
||||
|
||||
Reference in New Issue
Block a user