Unblock url proxy site

Full-Length Music Albums on YouTube

2012.12.12 18:01 RoflJoe Full-Length Music Albums on YouTube

Post full albums from YouTube. Share and discover.
[link]

2009.09.24 06:25 learn programming

A subreddit for all questions related to programming in any language.
[link]

2013.03.22 22:15 Kung Fu on YouTube

A place to post **full length** Kung Fu Movies found on **YouTube**
[link]

2024.05.14 20:02 CG-07 "Torch is not able to use GPU"

These are the steps I followed to install the program
  1. Download and install Python (I am sure I have activated the add python to path option)
  2. Download and install Git
  3. Download and install stable diffusion through CMD (this is the Github link: https://github.com/AUTOMATIC1111/stable-diffusion-webui )
but when I try running webui-user.bat, I get the following error:
venv "D:\Stable Diffusion\stable-diffusion-webui\venv\Scripts\Python.exe" Python 3.10.6 (tags/v3.10.6:9c7b4bd, Aug 1 2022, 21:53:49) [MSC v.1932 64 bit (AMD64)] Version: v1.9.3 Commit hash: 1c0a0c4c26f78c32095ebc7f8af82f5c04fca8c0 Traceback (most recent call last): File "D:\Stable Diffusion\stable-diffusion-webui\launch.py", line 48, in  main() File "D:\Stable Diffusion\stable-diffusion-webui\launch.py", line 39, in main prepare_environment() File "D:\Stable Diffusion\stable-diffusion-webui\modules\launch_utils.py", line 386, in prepare_environment raise RuntimeError( RuntimeError: Torch is not able to use GPU; add --skip-torch-cuda-test to COMMANDLINE_ARGS variable to disable this check Press any key to continue . . .

Solution methods that I tried but did not work

01.- I tried to edit the code in the webui-user.bat file to:
u/echo off set PYTHON= set GIT= set VENV_DIR= set COMMANDLINE_ARGS= --skip-torch-cuda-test to COMMANDLINE_ARGS call webui.bat
but after that I got the following error
venv "D:\Stable Diffusion\stable-diffusion-webui\venv\Scripts\Python.exe" Python 3.10.6 (tags/v3.10.6:9c7b4bd, Aug 1 2022, 21:53:49) [MSC v.1932 64 bit (AMD64)] Version: v1.9.3 Commit hash: 1c0a0c4c26f78c32095ebc7f8af82f5c04fca8c0 Installing clip Installing open_clip Installing requirements Launching Web UI with arguments: --skip-torch-cuda-test to COMMANDLINE_ARGS D:\Stable Diffusion\stable-diffusion-webui\venv\lib\site-packages\torch\cuda\__init__.py:740: UserWarning: CUDA initialization: The NVIDIA driver on your system is too old (found version 11010). Please update your GPU driver by downloading and installing a new version from the URL: http://www.nvidia.com/Download/index.aspx Alternatively, go to: https://pytorch.org to install a PyTorch version that has been compiled with your version of the CUDA driver. (Triggered internally at ..\c10\cuda\CUDAFunctions.cpp:108.) return torch._C._cuda_getDeviceCount() if nvml_count < 0 else nvml_count no module 'xformers'. Processing without... no module 'xformers'. Processing without... usage: launch.py [-h] [--update-all-extensions] [--skip-python-version-check] [--skip-torch-cuda-test] [--reinstall-xformers] [--reinstall-torch] [--update-check] [--test-server] [--log-startup] [--skip-prepare-environment] [--skip-install] [--dump-sysinfo] [--loglevel LOGLEVEL] [--do-not-download-clip] [--data-dir DATA_DIR] [--config CONFIG] [--ckpt CKPT] [--ckpt-dir CKPT_DIR] [--vae-dir VAE_DIR] [--gfpgan-dir GFPGAN_DIR] [--gfpgan-model GFPGAN_MODEL] [--no-half] [--no-half-vae] [--no-progressbar-hiding] [--max-batch-count MAX_BATCH_COUNT] [--embeddings-dir EMBEDDINGS_DIR] [--textual-inversion-templates-dir TEXTUAL_INVERSION_TEMPLATES_DIR] [--hypernetwork-dir HYPERNETWORK_DIR] [--localizations-dir LOCALIZATIONS_DIR] [--allow-code] [--medvram] [--medvram-sdxl] [--lowvram] [--lowram] [--always-batch-cond-uncond] [--unload-gfpgan] [--precision {full,autocast}] [--upcast-sampling] [--share] [--ngrok NGROK] [--ngrok-region NGROK_REGION] [--ngrok-options NGROK_OPTIONS] [--enable-insecure-extension-access] [--codeformer-models-path CODEFORMER_MODELS_PATH] [--gfpgan-models-path GFPGAN_MODELS_PATH] [--esrgan-models-path ESRGAN_MODELS_PATH] [--bsrgan-models-path BSRGAN_MODELS_PATH] [--realesrgan-models-path REALESRGAN_MODELS_PATH] [--dat-models-path DAT_MODELS_PATH] [--clip-models-path CLIP_MODELS_PATH] [--xformers] [--force-enable-xformers] [--xformers-flash-attention] [--deepdanbooru] [--opt-split-attention] [--opt-sub-quad-attention] [--sub-quad-q-chunk-size SUB_QUAD_Q_CHUNK_SIZE] [--sub-quad-kv-chunk-size SUB_QUAD_KV_CHUNK_SIZE] [--sub-quad-chunk-threshold SUB_QUAD_CHUNK_THRESHOLD] [--opt-split-attention-invokeai] [--opt-split-attention-v1] [--opt-sdp-attention] [--opt-sdp-no-mem-attention] [--disable-opt-split-attention] [--disable-nan-check] [--use-cpu USE_CPU [USE_CPU ...]] [--use-ipex] [--disable-model-loading-ram-optimization] [--listen] [--port PORT] [--show-negative-prompt] [--ui-config-file UI_CONFIG_FILE] [--hide-ui-dir-config] [--freeze-settings] [--freeze-settings-in-sections FREEZE_SETTINGS_IN_SECTIONS] [--freeze-specific-settings FREEZE_SPECIFIC_SETTINGS] [--ui-settings-file UI_SETTINGS_FILE] [--gradio-debug] [--gradio-auth GRADIO_AUTH] [--gradio-auth-path GRADIO_AUTH_PATH] [--gradio-img2img-tool GRADIO_IMG2IMG_TOOL] [--gradio-inpaint-tool GRADIO_INPAINT_TOOL] [--gradio-allowed-path GRADIO_ALLOWED_PATH] [--opt-channelslast] [--styles-file STYLES_FILE] [--autolaunch] [--theme THEME] [--use-textbox-seed] [--disable-console-progressbars] [--enable-console-prompts] [--vae-path VAE_PATH] [--disable-safe-unpickle] [--api] [--api-auth API_AUTH] [--api-log] [--nowebui] [--ui-debug-mode] [--device-id DEVICE_ID] [--administrator] [--cors-allow-origins CORS_ALLOW_ORIGINS] [--cors-allow-origins-regex CORS_ALLOW_ORIGINS_REGEX] [--tls-keyfile TLS_KEYFILE] [--tls-certfile TLS_CERTFILE] [--disable-tls-verify] [--server-name SERVER_NAME] [--gradio-queue] [--no-gradio-queue] [--skip-version-check] [--no-hashing] [--no-download-sd-model] [--subpath SUBPATH] [--add-stop-route] [--api-server-stop] [--timeout-keep-alive TIMEOUT_KEEP_ALIVE] [--disable-all-extensions] [--disable-extra-extensions] [--skip-load-model-at-start] [--unix-filenames-sanitization] [--filenames-max-length FILENAMES_MAX_LENGTH] [--no-prompt-history] [--ldsr-models-path LDSR_MODELS_PATH] [--lora-dir LORA_DIR] [--lyco-dir-backcompat LYCO_DIR_BACKCOMPAT] [--scunet-models-path SCUNET_MODELS_PATH] [--swinir-models-path SWINIR_MODELS_PATH] launch.py: error: unrecognized arguments: to COMMANDLINE_ARGS Press any key to continue . . .
02.- I also tried the following method but it didn't work:
I hope you can help me and thank you in advance for responding.
submitted by CG-07 to StableDiffusion [link] [comments]

2024.05.14 20:01 Only_Gold_1054 Crowdsourcing Alternative Commodity Market Data - Seeking Feedback

Hello Everyone!

I've been working on something that could potentially be interesting to the community, and would love your genuine feedbacks.

I've been talking with some of my friends working as traders in the space, particularly those focused on paper trading, who have shared fascinating insights into the lengths they go to gain an informational edge. Many are spending significant sums to establish direct access to key sites around the world, aiming to be the first to know about supply chain disruptions, inventory fluctuations, and other events that could move markets.
Interestingly, this real-time, on-the-ground intel often spreads first in private chats among exclusive networks of traders before hitting mainstream news channels. This allows those with access to act quickly on the information asymmetry.
I'm developing a crowdsourcing platform (using blockchains as payment rails) that aims to revolutionize this dynamic by connecting data providers ("Agents") directly with data consumers, enabling the efficient exchange of unique, actionable information that can inform trading strategies and risk management. The platform would feature verification mechanisms for data integrity, bonding curve pricing to reflect data value, and tokenized incentives for participation.
Key features of the platform include:
  1. Agents can create private data channels and set a bonding curve pricing model, where the price of access increases as more subscribers join. This acts as a proxy for the credibility and value of the Agent's information. (A Bonding Curve would look something like this: 1*72qA4WIL6LvWUnX6tmfviQ.png (640×480) (medium.com) where supply is the current number of subscribers.)
  2. Various verification mechanisms are in place for Agents, such as location tracking, email confirmation, daily check-ins, and sensor connections to ensure data integrity and reliability.
  3. Data consumers do not directly pay Agents, but rather interact with a smart contract that automatically handles payments and access control based on predefined rules.
  4. The platform includes a real-time chat feature for direct communication between Agents and subscribers, enabling more contextual and timely information sharing.
To all the community members, I'm seeking your valuable feedback on two key aspects:
  1. What kind of alternative data or market insights would you find most valuable and are currently not easily accessible to you? This could include data on supply chain flows, inventory levels, weather patterns, satellite imagery analysis, or any other information that could give you an edge in your trading decisions. I am aware alternative data industry is already a huge industry, but would there be valuable sources of data that are only accessible through last-mile, real-time data updates? (For example in these two posts on oil and coffee's influence from weather, would access to these information through a verified source provide you with information edge?)
  2. What do you foresee as potential drawbacks, risks, or pitfalls of such a platform? Are there any specific concerns around data quality, privacy, security, or regulatory compliance that we should be mindful of? Any thoughts on how to mitigate these risks and build trust in the platform?
Your input would be greatly appreciated as we shape the development of this crowdsourced data exchange platform. The goal is to create a mutually beneficial ecosystem that empowers commodity traders with timely, actionable insights while rewarding data providers for their valuable contributions.
Thank you in advance for your time and insights. I look forward to a fruitful discussion and learning from your experiences in the commodities trading space.
Best regards, OnlyGold
submitted by Only_Gold_1054 to Commodities [link] [comments]

2024.05.14 19:58 THCrunkadelic "ERROR: Exception in ASGI application" while trying to move model after successful finetuning (AllTalk)

I have tried the finetuning 3 times, including re-installing the entire text-generation-webui, and the 3rd time even doing "run as administrator" in the powershell. It errors trying to move the model at the end, and spits out a long line of code I will post below, that begins with the error in my title, and ends with "TypeError: Type is not JSON serializable: WindowsPath". I also get a JSON error when I try to refresh any of the dropdowns, which is weird.
Every time I get the same thing happen. Preflight checklist is good to go. Steps 2, 3, and 4 of finetuning are successful. I can load the model, I can test the model, and it sounds 95% accurate. Then when I try to move the model (I've tried option A, B, and C, they all error the same), I get the below response:
ERROR: Exception in ASGI application Traceback (most recent call last): File "C:\Automatic1111\text-generation-webui-main\installer_files\env\Lib\site-packages\starlette\responses.py", line 265, in __call__ await wrap(partial(self.listen_for_disconnect, receive)) File "C:\Automatic1111\text-generation-webui-main\installer_files\env\Lib\site-packages\starlette\responses.py", line 261, in wrap await func() File "C:\Automatic1111\text-generation-webui-main\installer_files\env\Lib\site-packages\starlette\responses.py", line 238, in listen_for_disconnect message = await receive() ^^^^^^^^^^^^^^^ File "C:\Automatic1111\text-generation-webui-main\installer_files\env\Lib\site-packages\uvicorn\protocols\http\httptools_impl.py", line 568, in receive await self.message_event.wait() File "C:\Automatic1111\text-generation-webui-main\installer_files\env\Lib\asyncio\locks.py", line 213, in wait await fut asyncio.exceptions.CancelledError: Cancelled by cancel scope 1e2a26f79d0
During handling of the above exception, another exception occurred:
+ Exception Group Traceback (most recent call last): File "C:\Automatic1111\text-generation-webui-main\installer_files\env\Lib\site-packages\uvicorn\protocols\http\httptools_impl.py", line 411, in run_asgi result = await app( # type: ignore[func-returns-value] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "C:\Automatic1111\text-generation-webui-main\installer_files\env\Lib\site-packages\uvicorn\middleware\proxy_headers.py", line 69, in __call__ return await self.app(scope, receive, send) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "C:\Automatic1111\text-generation-webui-main\installer_files\env\Lib\site-packages\fastapi\applications.py", line 1054, in __call__ await super().__call__(scope, receive, send) File "C:\Automatic1111\text-generation-webui-main\installer_files\env\Lib\site-packages\starlette\applications.py", line 123, in __call__ await self.middleware_stack(scope, receive, send) File "C:\Automatic1111\text-generation-webui-main\installer_files\env\Lib\site-packages\starlette\middleware\errors.py", line 186, in __call__ raise exc File "C:\Automatic1111\text-generation-webui-main\installer_files\env\Lib\site-packages\starlette\middleware\errors.py", line 164, in __call__ await self.app(scope, receive, _send) File "C:\Automatic1111\text-generation-webui-main\installer_files\env\Lib\site-packages\gradio\route_utils.py", line 689, in __call__ await self.app(scope, receive, send) File "C:\Automatic1111\text-generation-webui-main\installer_files\env\Lib\site-packages\starlette\middleware\exceptions.py", line 65, in __call__ await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send) File "C:\Automatic1111\text-generation-webui-main\installer_files\env\Lib\site-packages\starlette\_exception_handler.py", line 64, in wrapped_app raise exc File "C:\Automatic1111\text-generation-webui-main\installer_files\env\Lib\site-packages\starlette\_exception_handler.py", line 53, in wrapped_app await app(scope, receive, sender) File "C:\Automatic1111\text-generation-webui-main\installer_files\env\Lib\site-packages\starlette\routing.py", line 756, in __call__ await self.middleware_stack(scope, receive, send) File "C:\Automatic1111\text-generation-webui-main\installer_files\env\Lib\site-packages\starlette\routing.py", line 776, in app await route.handle(scope, receive, send) File "C:\Automatic1111\text-generation-webui-main\installer_files\env\Lib\site-packages\starlette\routing.py", line 297, in handle await self.app(scope, receive, send) File "C:\Automatic1111\text-generation-webui-main\installer_files\env\Lib\site-packages\starlette\routing.py", line 77, in app await wrap_app_handling_exceptions(app, request)(scope, receive, send) File "C:\Automatic1111\text-generation-webui-main\installer_files\env\Lib\site-packages\starlette\_exception_handler.py", line 64, in wrapped_app raise exc File "C:\Automatic1111\text-generation-webui-main\installer_files\env\Lib\site-packages\starlette\_exception_handler.py", line 53, in wrapped_app await app(scope, receive, sender) File "C:\Automatic1111\text-generation-webui-main\installer_files\env\Lib\site-packages\starlette\routing.py", line 75, in app await response(scope, receive, send) File "C:\Automatic1111\text-generation-webui-main\installer_files\env\Lib\site-packages\starlette\responses.py", line 258, in __call__ async with anyio.create_task_group() as task_group: File "C:\Automatic1111\text-generation-webui-main\installer_files\env\Lib\site-packages\anyio\_backends\_asyncio.py", line 678, in __aexit__ raise BaseExceptionGroup( ExceptionGroup: unhandled errors in a TaskGroup (1 sub-exception) +-+---------------- 1 ---------------- Traceback (most recent call last): File "C:\Automatic1111\text-generation-webui-main\installer_files\env\Lib\site-packages\starlette\responses.py", line 261, in wrap await func() File "C:\Automatic1111\text-generation-webui-main\installer_files\env\Lib\site-packages\starlette\responses.py", line 250, in stream_response async for chunk in self.body_iterator: File "C:\Automatic1111\text-generation-webui-main\installer_files\env\Lib\site-packages\gradio\routes.py", line 885, in sse_stream raise e File "C:\Automatic1111\text-generation-webui-main\installer_files\env\Lib\site-packages\gradio\routes.py", line 849, in sse_stream response = process_msg(message) ^^^^^^^^^^^^^^^^^^^^ File "C:\Automatic1111\text-generation-webui-main\installer_files\env\Lib\site-packages\gradio\routes.py", line 797, in process_msg return f"data: {orjson.dumps(message.model_dump()).decode('utf-8')}\n\n" ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ TypeError: Type is not JSON serializable: WindowsPath +------------------------------------
submitted by THCrunkadelic to Oobabooga [link] [comments]

2024.05.14 19:43 Both-Delivery8225 URL filtering is slowwwwwwwww

Before calling in a ticket to the dreadful PA TAC, wanted to ask here. I did some BPA tweaks to our corporate shared URL filtering profile that is used on all my various PA platforms as well as Prisma access. They were not major tweaks...mostly relating to allow vs. alert for better logging as well as a few 'drop' unknown categories as well as parked domains. Since those changes were applied, websites (mostly with heavy CDN) like bleepingcomputer.com take FOREVER to load when clicking on the various links/menus within the site itself....sometimes the browser just sits there and never pulls anything up. No block pages appear either. Nothing is standing out in the URL logs as abnormal. I create a custom URL list, add the list to a custom URL category with action 'allow' and poof, the web site loads as expected. Any thoughts or insights?
submitted by Both-Delivery8225 to paloaltonetworks [link] [comments]

2024.05.14 19:43 IdodoHaHatih Youtube Video- Two Steps From Hell - Immortal (Cinematic)(Edit by EpicMusicVideos) URL in post Video from 2015

Hey, I tried looking for the deleted youtube video "Two Steps From Hell - Immortal (Cinematic)(Edit by EpicMusicVideos)" which was uploaded in 2015. The URL is: https://www.youtube.com/watch?v=RSp6V_mT5ME&list=LL&index=2282 .
I tried looking in Wayback Machine and other various sites, the only valid results are metadata. Is there a way for me to watch the video again?
Thanks
submitted by IdodoHaHatih to DHExchange [link] [comments]

2024.05.14 19:31 diamondsw Weird macOS DNS problem

I've had a seriously weird DNS bug for the last few months. I run a homelab with a variety of services and local DNS (dnsmasq) to provide internal addressing. This has worked great - except that macOS keeps losing one DNS entry. In other words, the site will load, work fine for a bit, and between one page click and the next the DNS entry will drop out of the Mac's local DNS resolver cache and Safari/Chrome/etc won't be able to connect. Ping to the DNS name also fails. Flushing the local cache and restarting mDNSResponder fixes it for a while, where a while could be seconds or minutes - but typically not more.
All of the below are local DNS names being resolved from the same local DNS server, so there are absolutely no configuration differences between these names (as you can see, they even resolve to the same host which is using a reverse proxy to send requests to the proper container).
Working domain:
sudo dns-sd -Q wiki.REDACTED Password: DATE: ---Tue 14 May 2024--- 10:15:35.555 ...STARTING... Timestamp A/R Flags IF Name Type Class Rdata 10:15:35.558 Add 2 0 wiki.REDACTED. Addr IN 10.0.1.150 10:15:49.708 Rmv 0 0 wiki.REDACTED. Addr IN 10.0.1.150 10:15:49.720 Add 2 0 wiki.REDACTED. Addr IN 10.0.1.150 10:16:50.849 Rmv 0 0 wiki.REDACTED. Addr IN 10.0.1.150 10:16:50.855 Add 2 0 wiki.REDACTED. Addr IN 10.0.1.150 10:52:28.893 Rmv 0 0 wiki.REDACTED. Addr IN 10.0.1.150 10:52:28.909 Add 2 0 wiki.REDACTED. Addr IN 10.0.1.150 10:59:27.633 Rmv 0 0 wiki.REDACTED. Addr IN 10.0.1.150 10:59:27.643 Add 2 0 wiki.REDACTED. Addr IN 10.0.1.150 10:59:32.106 Rmv 0 0 wiki.REDACTED. Addr IN 10.0.1.150 10:59:32.118 Add 2 0 wiki.REDACTED. Addr IN 10.0.1.150
Flapping domain:
sudo dns-sd -Q manga.REDACTED Password: DATE: ---Tue 14 May 2024--- 10:15:26.980 ...STARTING... Timestamp A/R Flags IF Name Type Class Rdata 10:15:26.980 Add 40000002 0 manga.REDACTED. Addr IN 0.0.0.0 No Such Record 10:15:49.720 Add 2 0 manga.REDACTED. Addr IN 10.0.1.150 10:16:02.047 Add 2 0 manga.REDACTED. Addr IN 0.0.0.0 No Such Record 10:16:03.540 Rmv 0 0 manga.REDACTED. Addr IN 10.0.1.150 10:16:50.855 Add 2 0 manga.REDACTED. Addr IN 10.0.1.150 10:17:03.282 Add 2 0 manga.REDACTED. Addr IN 0.0.0.0 No Such Record 10:17:04.952 Rmv 0 0 manga.REDACTED. Addr IN 10.0.1.150 10:17:04.955 Rmv 0 0 manga.REDACTED. Addr IN 10.0.1.150 10:52:28.908 Add 2 0 manga.REDACTED. Addr IN 10.0.1.150 10:52:41.260 Add 2 0 manga.REDACTED. Addr IN 0.0.0.0 No Such Record 10:52:42.961 Rmv 0 0 manga.REDACTED. Addr IN 10.0.1.150 10:52:42.963 Rmv 0 0 manga.REDACTED. Addr IN 10.0.1.150 10:59:20.051 Add 2 0 manga.REDACTED. Addr IN 10.0.1.150 10:59:27.633 Rmv 0 0 manga.REDACTED. Addr IN 10.0.1.150 10:59:27.643 Add 2 0 manga.REDACTED. Addr IN 0.0.0.0 No Such Record 10:59:32.118 Add 2 0 manga.REDACTED. Addr IN 10.0.1.150 10:59:44.436 Add 2 0 manga.REDACTED. Addr IN 0.0.0.0 No Such Record 10:59:45.985 Rmv 0 0 manga.REDACTED. Addr IN 10.0.1.150 10:59:45.987 Add 2 0 manga.REDACTED. Addr IN 10.0.1.150 10:59:58.532 Add 2 0 manga.REDACTED. Addr IN 0.0.0.0 No Such Record 10:59:59.901 Rmv 0 0 manga.REDACTED. Addr IN 10.0.1.150 10:59:59.903 Rmv 0 0 manga.REDACTED. Addr IN 10.0.1.150 11:22:54.263 Add 2 0 manga.REDACTED. Addr IN 10.0.1.150 11:23:06.658 Add 2 0 manga.REDACTED. Addr IN 0.0.0.0 No Such Record 11:23:08.337 Rmv 0 0 manga.REDACTED. Addr IN 10.0.1.150 11:23:08.341 Add 2 0 manga.REDACTED. Addr IN 10.0.1.150 11:23:45.637 Add 2 0 manga.REDACTED. Addr IN 0.0.0.0 No Such Record 11:23:47.173 Rmv 0 0 manga.REDACTED. Addr IN 10.0.1.150
The temporary fix:
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
This beats the hell out of me, as I cannot fathom why one entry works perfectly and another does not. I even changed that hostname and the weirdness followed the host, which makes even less sense.
Anyone have any clue where to go with this goofiness? I find macOS nigh impossible to troubleshoot ever since Unified Logging and the proliferation of "private" data making even those logs useless.
submitted by diamondsw to MacOS [link] [comments]

2024.05.14 18:47 Apprehensive_One2266 Lost my job today to an agency

*May come off as a rant, I'm sorry
So my employer hired an agency a few days ago and I got notice today that I'm being let go (I'm the only dev/seo/graphic designemarketing/network admin).
I'm kind of lost for words right now because they're asking me to help them convert the current state to WordPress which is what they were using before I built a completely new website.
I've worked for them for 4 months now, I built a static 70 page website from the ground up. This includes all graphic designs, graphic animations, modals, and the hundreds of design changes because they couldn't tell me what they wanted, without me having to make what they don't want. This includes 30 unique service area pages tailored to those areas and are all ranking decently well in a highly competitive service.
About 3 weeks ago, I converted the entire website to django (I have nightmares of changing hard-coded urls)
I built a complete admin dashboard, customer & employee portal. I built forms for blog posts and rss feeds that also posts to social media. I integrated CMS's, multiple api's; I made analytics dashboards, custom on site user tracking, automated geofencing campaigns and more (not trying to rant, I'm sure you get the point)
Then, 2 nights ago I get an email I'm CC'd on asking for DNS access. I knew what was going on I could feel it, but instead I worked 16 hours completely automating markup schema, meta tags and opengraph like an idiot.
Here I am building them a platform so they don't have to rely on 3rd party pay walls and now they cut their losses??? When I been asking them to setup a payment method for 6 days now so we could switch hosting LOL..
Now I have the agency asking me for the old static files (prior to me spending hours optimizing it). I told them to use a CLI to pull the static files off the current host (which I'm pretty sure is only a public directory) but It makes me feel better knowing they're struggling to do just that when I have a .rar file that's named "before_django_conv"
I'm mentally exhausted, I got laid off 3 months prior to working for them from my last job. I'm completely self-taught so getting interviews isn't easy.
submitted by Apprehensive_One2266 to django [link] [comments]

2024.05.14 18:47 Then_Marionberry_259 MAY 13, 2024 STGO.TO STEPPE GOLD ANNOUNCES MAILING AND FILING OF ANNUAL GENERAL AND SPECIAL MEETING MATERIALS IN CONNECTION WITH PROPOSED TRANSACTION WITH BOROO GOLD AND BOROO SINGAPORE

MAY 13, 2024 STGO.TO STEPPE GOLD ANNOUNCES MAILING AND FILING OF ANNUAL GENERAL AND SPECIAL MEETING MATERIALS IN CONNECTION WITH PROPOSED TRANSACTION WITH BOROO GOLD AND BOROO SINGAPORE
https://preview.redd.it/ag74dcxj8f0d1.png?width=3500&format=png&auto=webp&s=7e4bc77da737c24a4d51fd2f8cdbd9db8254d299
Ulaanbaatar, Mongolia--(Newsfile Corp. - May 13, 2024) - Steppe Gold Ltd. (TSX: STGO) (OTCQX: STPGF) (FSE: 2J9) ("Steppe Gold") is pleased to announce that it has filed with the applicable Canadian securities regulatory authorities the management information circular dated May 8, 2024 and related meeting materials of Steppe Gold (the "Meeting Materials") for use at the annual general and special meeting (the "Meeting") of Steppe Gold shareholders (the "Shareholders") to be held in connection with the proposed transaction with Boroo Gold LLC ("Boroo Gold") and Boroo Pte Ltd. ("Boroo Singapore"), or one of its affiliates, as previously announced on April 11, 2024 (the "Transaction"). Steppe Gold has also mailed copies of the Meeting Materials to Shareholders entitled to vote on the Transaction at the Meeting.
At the Meeting, Shareholders will be asked to consider and, if deemed advisable, to approve the Transaction. If the Transaction is completed: (i) Steppe Gold will acquire all of the issued and outstanding shares of Boroo Gold in return for the issuance of that number of common shares in the capital of Steppe Gold ("Common Shares") that would result in Boroo Singapore, directly or indirectly, holding 55.9% of the issued and outstanding Common Shares (calculated on a fully diluted basis); and (ii) Boroo Singapore will acquire the Tres Cruces Oxide Project (the "Tres Cruces Project") by purchasing all of the issued and outstanding shares of two of Steppe Gold's indirect, wholly-owned subsidiaries for aggregate cash consideration of approximately CAD$12 million.
THE STEPPE GOLD BOARD OF DIRECTORS HAS UNANIMOUSLY DETERMINED THAT THE TRANSACTION IS IN THE BEST INTERESTS OF STEPPE GOLD AND UNANIMOUSLY RECOMMENDS THAT SHAREHOLDERS VOTE IN FAVOUR OF THE TRANSACTION.
Benefits of the Transaction
The Transaction is expected to provide meaningful benefits to Shareholders, including:
  • Increased combined gold production to 90,000 oz per annum in 2025 and 150,000 oz gold equivalent per annum by 2026.
  • Strong cash flow and increased financial strength to service ATO Gold Mine Phase 2 Expansion debt and project financing.
  • Funding for exploration programs and further acquisition opportunities in Mongolia.
  • Liquidity from the sale of the Tres Cruces Project.
  • Creation of a multi-asset producer with a strong base and focus on Mongolia.
The Meeting and Voting
The Meeting is scheduled to be held at the Shangri-La Hotel, 19 Olympic Street, Sukhbaatar District-1, Ulaanbaatar 14241 Mongolia on June 24, 2024 at 10:00 a.m. (ULAT). Shareholders may vote in person at the Meeting or by proxy. Shareholders that are unable to attend the Meeting, or any adjourned or postponed Meeting in person, are requested to date, sign and return the form of proxy for use at the Meeting. The deadline for receipt of proxies for the Meeting is 10:00 a.m. (ULAT) on June 20, 2024.
Shareholders are advised to carefully read the Meeting Materials and then vote in person at the Meeting or by proxy. The Meeting Materials are available under the Company's profile on SEDAR+ at www.sedarplus.ca. Only Shareholders of record as at the close of business on May 6, 2024 are eligible to vote at the Meeting.
About Steppe Gold
Steppe Gold is Mongolia's premier precious metals company and 100% owner of the ATO gold mine and the Uudam Khundii project in Mongolia.
About Boroo Gold
Established in 1997, Boroo Gold is a leading gold producer in Mongolia with over 50,000 tons per day mining fleet, 5,500 tons per day mill and carbon-in-leach circuit gold processing plant, 3,000,000 tons per annum heap leach and carbon-in-columns plant and an approximate workforce of over 400 people. Boroo Gold operates the Boroo mine in Selenge province, as well as owning and operating the adjacent Ulaanbulag mine in Mongolia.
Cautionary Statement on Forward-Looking Information
This news release includes certain statements that constitute "forward-looking statements" and "forward-looking information" within the meaning of applicable securities laws (collectively, "forward-looking statements"). These include statements regarding Steppe Gold's intent, or the beliefs or current expectations for Steppe Gold's growth, production and valuation post-closing of the Transaction; future market conditions for metals; timing of the Meeting; and expected benefits to Shareholders as a result of the Transaction.
When used in this news release, words such as "expected", "scheduled" and similar expressions are intended to identify these forward-looking statements as well as phrases or statements that certain actions, events or results "will", or "would" occur or the negative connotation of such terms.
As well, forward-looking statements may relate to Steppe Gold's future outlook and anticipated events, such as the consummation and timing of the Transaction; the satisfaction of the conditions precedent to each of the Transaction; the anticipated benefits of the Transaction; the potential for value creation to Shareholders; the anticipated timing of the closing of the Transaction; the timing and anticipated receipt of required Shareholder, court and regulatory approvals for the Transaction; anticipated gold production of Boroo Gold and combined gold production of Steppe Gold; the anticipated cash flow of Steppe Gold; potential liquidity from the sale of the Tres Cruces Project; and discussion of future plans, projections, objectives, estimates and forecasts and the timing related thereto.
These forward-looking statements involve numerous risks and uncertainties, including those relating to: required shareholder, regulatory and stock exchange approvals; approvals from applicable Mongolian authorities; exercise of any termination rights under the share exchange agreement dated April 11, 2024 between Steppe Gold, Boroo Singapore and Centerra Netherlands BVBA (the "Share Exchange Agreement") or the separate definitive share purchase agreements (the "Share Purchase Agreements"), each between one of Steppe Gold's wholly-owned subsidiaries, on the one hand, and Boroo Singapore or one of its affiliates, on the other hand, each dated April 11, 2024; meeting other conditions precedent to each of the Share Exchange Agreement and the Share Purchase Agreements; material adverse effects on the business, properties and assets of Steppe Gold or Boroo Gold; discrepancies between actual and estimated production and test results, mineral reserves and resources and metallurgical recoveries; and such other risk factors detailed from time to time in Steppe Gold's public disclosure documents, including, without limitation, those risks identified in Steppe Gold's annual information form for the year ended December 31, 2023, which is available on SEDAR+ at www.sedarplus.ca.
Forward-looking statements are based on information available at the time those statements are made and/or management's good faith belief as of that time with respect to future events and are subject to risks and uncertainties that could cause actual performance or results to differ materially from those expressed in or suggested by such forward-looking statements. Forward-looking statements speak only as of the date those statements are made. Except as required by applicable law, Steppe Gold assumes no obligation to update or to publicly announce the results of any change to any forward-looking statement contained or incorporated by reference herein to reflect actual results, future events or developments, changes in assumptions or changes in other factors affecting the forward-looking statements. If Steppe Gold updates any one or more forward-looking statements, no inference should be drawn that the company will make additional updates with respect to those or other forward-looking statements. All forward-looking statements contained in this news release are expressly qualified in their entirety by this cautionary statement.
Contact Information
Steppe Gold
Bataa Tumur-Ochir, Chairman and Chief Executive Officer Jeremy South, Senior Vice President and Chief Financial Officer
Elisa Tagarvaa, Investor Relations Manager ([elisa@steppegold.com](mailto:elisa@steppegold.com))
Shangri-La office, Suite 1201, Olympic Street 19A, Sukhbaatar District 1, Ulaanbaatar 14241, Mongolia Tel: +976 7732 1914
To view the source version of this press release, please visit https://www.newsfilecorp.com/release/209078
​
https://preview.redd.it/hh1g8p1k8f0d1.png?width=4000&format=png&auto=webp&s=a6235f0cde46ed27e5902c3c5847f335d59fca52
Universal Site Links
STEPPE GOLD LTD
STOCK METAL DATABASE
ADD TICKER TO THE DATABASE
www.reddit.com/Treaty_Creek
REPORT AN ERROR
submitted by Then_Marionberry_259 to Treaty_Creek [link] [comments]

2024.05.14 18:26 Kindly_Ice1745 RFPs for Renaissance Commerce Park

https://12ft.io/proxy?q=https%3A%2F%2Fbuffalonews.com%2Fnews%2Flocal%2Fbusiness%2Fdevelopment%2Fbethlehem-steel-site-developer%2Farticle_30e5da3a-1146-11ef-9c11-87d8413e2ff7.html%23tracking-source%3Dhome-top-story
I know we're still probably a decade or two away from seeing this site being used at 2/3 of its original size, but it is really cool to see it being redeveloped and reactivated.
submitted by Kindly_Ice1745 to Buffalo [link] [comments]

2024.05.14 18:15 gingernut02 Responsive Embed issues in React

Hi all, I'm new to Spline and just needing some help as my media queries aren't working when I inspect the mobile version of this website - the Spline viewer seems to shrink to about a quarter of the screen despite CSS adjustments. Responsive design works in Spline 3D editor perfectly. If I could get some help making it 100vh on mobile that'd be amazing! Thanks :) Full site repo. ComputerHero.js:
import Spline from "@splinetool/react-spline"; import React from "react"; import styled from "styled-components"; import "./styles/App.css"; export default function ComputerHero() { return ( 
    
 ); } const Wrapper = styled.div` font-family: "Bebas Neue", sans-serif; font-weight: 400; font-style: normal; margin: 0 auto; `;
App.css:
@import url("https://fonts.googleapis.com/css2?family=Bebas+Neue&family=Raleway:ital,wght@0,100..900;1,100..900&display=swap"); #root { height: 100%; background: #ddc7ba; } body { margin: 0 auto; } App { background: #ddc7ba; } @media (min-width: 700px) and (max-width: 1920px) { canvas { height: 100%; } } @media (min-width: 600px) { canvas { height: 100vh; } }
submitted by gingernut02 to Spline3D [link] [comments]

2024.05.14 17:59 Then_Marionberry_259 MAY 14, 2024 MAG.TO MAG SILVER REPORTS FIRST QUARTER FINANCIAL RESULTS

MAY 14, 2024 MAG.TO MAG SILVER REPORTS FIRST QUARTER FINANCIAL RESULTS
https://preview.redd.it/w3wbxgjzze0d1.png?width=3500&format=png&auto=webp&s=c343619687a11525804d04f755c495d975b2050d
VANCOUVER, British Columbia, May 14, 2024 (GLOBE NEWSWIRE) -- MAG Silver Corp. (TSX / NYSE American: MAG) (“MAG”, or the “Company”) announces the Company’s unaudited consolidated financial results for the three months ended March 31, 2024 (“Q1 2024”). For details of the unaudited condensed interim consolidated financial statements of the Company for the three months ended March 31, 2024 (“Q1 2024 Financial Statements”) and management’s discussion and analysis for the three months ended March 31, 2024 (“Q1 2024 MD&A”), please see the Company’s filings on the System for Electronic Document Analysis and Retrieval Plus (“SEDAR+”) at ( www.sedarplus.ca ) or on the Electronic Data Gathering, Analysis, and Retrieval (“EDGAR”) at ( www.sec.gov ).
All amounts herein are reported in $000s of United States dollars (“US$”) unless otherwise specified (C$ refers to Canadian dollars).
KEY HIGHLIGHTS (on a 100% basis unless otherwise noted)
  • MAG reported net income of $14,895 ($0.14 per share) driven by income from Juanicipio (equity accounted) of $19,244, and adjusted EBITDA 1 of $32,447 for the three months ended March 31, 2024.
  • A total of 325,683 tonnes of ore at a silver head grade of 476 grams per tonne (“g/t”) (equivalent silver head grade 2 713 g/t), was processed at Juanicipio during Q1 2024.
  • Juanicipio achieved silver production and equivalent silver production 2 of 4.5 and 6.4 million ounces, respectively, during Q1 2024.
  • Juanicipio delivered robust cost performance with cash cost 1 of $2.50 per silver ounce sold ($8.66 per equivalent silver ounce sold 3 ), and all-in sustaining cost 1 of $6.11 per silver ounce sold ($11.22 per equivalent silver ounce sold 3 ) in Q1 2024.
  • Juanicipio generated strong operating cash flow of $42,521 and free cash flow 1 of $27,820 in the first quarter of 2024 after tax payments of $25,772.
  • Juanicipio returned a total of $17,459 in interest and loan principal repayments to MAG during Q1 2024.
  • MAG published its updated technical report on Juanicipio on March 27, 2024 outlining robust economics with an after tax NPV of $1.2 billion over an initial 13-year life of mine, generating annual average free cashflow exceeding $130 million. Mineral Resources increased by 33% from the 2017 PEA, with substantial growth in Measured and Indicated categories. Inferred resources also expanded, highlighting significant near-term, high-grade upside potential. An inaugural 15.4 million tonnes Mineral Reserve Estimate at 628 g/t silver equivalent grade was declared enhancing economic confidence. Extensive exploration upside remains, with only 5% of the property explored, indicating high potential for further discoveries.
  • MAG announced 2024 production and cost guidance with Juanicipio expected to produce between 14.3 million and 15.8 million silver ounces yielding between 13.2 million and 14.6 million payable silver ounces at all-in sustaining costs of between $9.50 and $10.50 per silver ounce sold. Juanicipio remains on track to achieve 2024 guidance.
  • On March 22, 2024 the Company, through its Gatling Exploration Inc. subsidiary, acquired 100% ownership of the Goldstake property (contiguous to its current land holdings) from Goldstake Explorations Inc. and Transpacific Resources Inc., for consideration of C$5,000.
________________________
1 Adjusted EBITDA, total cash costs, cash cost per ounce, all-in sustaining costs, all-in sustaining cost per ounce and free cash flow are non-IFRS measures, please see below ‘ Non-IFRS Measures ’ section and section 12 of the Q1 2024 MD&A for a detailed reconciliation of these measures to the Q1 2024 Financial Statements.
2 Equivalent silver head grade and equivalent silver production have been calculated using the following price assumptions to translate gold, lead and zinc to “equivalent” silver head grade and “equivalent” silver production: $23/oz silver, $1,950/oz gold, $0.95/lb lead and $1.15/lb zinc.
3 Equivalent silver ounces sold have been calculated using realized price assumptions to translate gold, lead and zinc to “equivalent” silver ounces sold (metal quantity, multiplied by metal price, divided by silver price). Q1 2024 realized prices of $23.73/oz silver, $2,112.27/oz gold, $0.92/lb lead and $1.08/lb zinc.
CORPORATE
  • The Company is well underway with the preparation of its 2023 sustainability report underscoring its continued commitment to transparency with its stakeholders while providing a comprehensive overview of the Company’s environmental, social and governance (“ESG”) commitments, practices and performance for 2023. A copy of MAG’s 2022 sustainability report and MAG Silver 2022 ESG Data Table are available on the Company’s website at https://magsilver.com/esg/reports/ 4
________________________
4 Information contained in or otherwise accessible through the Company’s website, including the 2022 sustainability report and MAG Silver 2022 ESG Data Table, do not form part of this News Release and are not incorporated into this News Release by reference.
EXPLORATION
  • Juanicipio:
    • Infill drilling at Juanicipio continued in Q1 2024 from underground aimed at upgrading mineralization in areas expected to be mined in the near to mid-term. During Q1 2024, 11,271 metres were drilled from underground.
    • Surface drilling focused on expanding and upgrading the deeper zones and broader regional exploration started in April 2024.
    • During 2024, Juanicipio plans to drill a total of 50,000 metres, with 33,000 metres from underground and 17,000 metres from surface.
  • Deer Trail Project, Utah:
    • On May 29, 2023 MAG started a Phase 3 drilling program focused on up to three porphyry “hub” target areas thought to be the source of the manto, skarn, epithermal mineralization and extensive alteration throughout the project area including that at the Deer Trail and Carissa zones. In late 2023 an early onset of winter snowfall impacted the commencement of the third porphyry “hub” target, which is now expected to be drilled in 2024. The two completed “hub” holes to date total 2,738 metres. Both holes intercepted alteration and mineralization in line with what is expected on the edges of porphyry systems. Follow-up drill targets are planned for summer 2024.
    • With the early onset of snowfall, Phase 4 drilling focussed on lower elevations commenced in the last quarter of 2023 and continued through Q1 2024, aimed at offsetting the Carissa discovery and testing other high-potential targets in the Deer Trail mine area. During Q1 2024, 1,208 metres were drilled at Carissa with results pending.
  • Larder Project, Ontario:
    • Drilling targeting Cheminis and Bear totalled 5,391 metres in Q1 2024. Targets tested include down plunge extension of the high-grade double knuckle at the Bear East zone and extending the Cheminis south mine sequence down plunge.
    • Cheminis Update: Follow-up drilling of the Cheminis South Cadillac-Larder Break (“CLD”) mine sequence down plunge is planned to test below the most recent intercepts. Hole GAT-24-026 intersected a new zone on the north side of the CLB within a fuchsite-silica-albite altered komatiite grading 3.9 g/t gold over 16 metres with 2 higher grade shoots associated with albite dykes (see Table 1 below).
    • Bear Update: Utilizing the updated model and incorporating the updated data from recent drilling, the Bear East zone was successfully extended down plunge by up to 1,100 metres depth. Hole GAT-24-024NB intersected gold mineralization on both sides of the CLB which confirms the presence of either another structural trap at depth or the continuation of the “double knuckle” zone at surface. Gold mineralization intersected on the north zone included 9.4 g/t gold over 2.2 metres within a strongly altered komatiite with syenite intrusions and 1.6 g/t gold over 4.2 metres on the south zone within the south iron-rich volcanics (see Table 1 below). Bear East remains open in all directions.
Table 1: 2024 Larder Drillholes Highlights
https://preview.redd.it/qdr6asmzze0d1.png?width=720&format=png&auto=webp&s=aaedd0020755eaf3404201557cc9623acc995125
JUANICIPIO RESULTS
All results of Juanicipio in this section are on a 100% basis, unless otherwise noted.
Operating Performance
The following table and subsequent discussion provide a summary of the operating performance of Juanicipio for the three months ended March 31, 2024 and 2023, unless otherwise noted.
https://preview.redd.it/9txq8snzze0d1.png?width=720&format=png&auto=webp&s=0089cf57573e8834bdb641cf9e055619e6f6c5b2
(1) Equivalent silver head grades have been calculated using the following price assumptions to translate gold, lead and zinc to “equivalent” silver head grade: $23/oz silver, $1,950/oz gold, $0.95/lb lead and $1.15/lb zinc (Q1 2023: $21.85/oz silver, $1,775/oz gold, $0.915/lb lead and $1.30/lb zinc).
(2) Equivalent silver payable ounces have been calculated using realized price assumptions to translate gold, lead and zinc to “equivalent” silver payable ounces (metal quantity, multiplied by metal price, divided by silver price). Q1 2024 realized prices of $23.73/oz silver, $2,112.27/oz gold, $0.92/lb lead and $1.08/lb zinc (Q1 2023 realized prices of $22.93/oz silver, $1,959.50/oz gold, $0.94/lb lead and $1.43/lb zinc).
During the three months ended March 31, 2024 a total of 325,081 tonnes of ore were mined. This represents an increase of 45% over Q1 2023. Increases in mined tonnages at Juanicipio have been driven by the operational ramp up of the mine towards steady state targets.
During the three months ended March 31, 2024 a total of 325,683 tonnes of ore were processed through the Juanicipio plant; no ore was processed at the nearby Fresnillo and Saucito processing plants (100% owned by Fresnillo). This represents an increase of 47% over Q1 2023. The increase in milled tonnage has been driven by the Juanicipio mill commissioning and operational ramp up to nameplate capacity over the course of 2023.
The silver head grade and equivalent silver head grade for the ore processed in the three months ended March 31, 2024 was 476 g/t and 713 g/t, respectively (three months ended March 31, 2023: 363 g/t and 530 g/t, respectively). Head grades in Q1 2023 were lower as low-grade commissioning stockpiles were processed through the Juanicipio plant. Silver metallurgical recovery during Q1 2024 was 89.1% (Q1 2023: 87.0%) reflecting ongoing optimizations in the processing plant.
The following table provides a summary of the total cash costs 5 and all-in sustaining costs 5 (“AISC”) of Juanicipio for the three months ended March 31, 2024, and 2023.
https://preview.redd.it/riqz1yozze0d1.png?width=720&format=png&auto=webp&s=c5f2edde6bc789d2d379ca3a910beaa1cb262bde
________________________
5 Total cash costs, cash cost per ounce, cash cost per equivalent ounce, all-in sustaining costs, all-in sustaining cost per ounce, and all-in sustaining cost per equivalent ounce are non-IFRS measures, please see the “ Non-IFRS Measures ” section below and section 12 of the Q1 2024 MD&A for a detailed reconciliation of these measures to the Q1 2024 Financial Statements. Equivalent silver ounces sold have been calculated using realized price assumptions to translate gold, lead and zinc to “equivalent” silver ounces sold (metal quantity, multiplied by metal price, divided by silver price). Q1 2024 realized prices of $23.73/oz silver, $2,112.27/oz gold, $0.92/lb lead and $1.08/lb zinc (Q1 2023: $22.93/oz silver, $1,959.50/oz gold, $0.94/lb lead and $1.43/lb zinc).
Financial Results
The following table presents excerpts of the financial results of Juanicipio for the three months ended March 31, 2024 and 2023.
https://preview.redd.it/4zym5dqzze0d1.png?width=720&format=png&auto=webp&s=d25c91cabc7f6c6b35ff61acacc0160f3dfac2e7
Sales increased by $72,207 during the three months ended March 31, 2024, mainly due to 179% higher metal volumes and 2% higher realized metal prices.
Offsetting higher sales was higher production cost ($9,409) which was driven by higher sales and operational ramp-up in mining and processing, including $3,545 in inventory movements, and higher depreciation ($14,083) as the Juanicipio mill achieved commercial production and commenced depreciating the processing facility and associated equipment in June 2023. Operating margin increased by 21% to 52%, mainly due to operational leverage and the lower reliance on the nearby Fresnillo and Saucito processing facilities.
Other expenses increased by $2,159 mainly as a result of higher extraordinary mining and other duties ($872) in relation to higher precious metal revenues from the sale of concentrates and higher consulting and administrative expenses ($2,690) as an operator services agreement became effective upon initiation of commercial production (the “Operator Services Agreement”), offset by lower exchange losses and other costs ($1,566).
Taxes increased by $20,980 impacted by higher taxable profits generated during Q1 2024, and non-cash deferred tax credits related to the commencement of use of plant and equipment in Q1 2023.
Ore Processed at Juanicipio Plant (100% basis)
https://preview.redd.it/koajybrzze0d1.png?width=720&format=png&auto=webp&s=caf1b70c53c47d371b9cebd743877fcd4ae59ba3
(1) The underground mine was considered readied for its intended use on January 1, 2022, whereas the Juanicipio processing facility started commissioning and ramp-up activities in January 2023, achieving commercial production status on June 1, 2023.
(2) Includes toll milling costs from processing mineralized material at the Saucito and Fresnillo plants for Q1 2023.
Sales and treatment charges are recorded on a provisional basis and are adjusted based on final assay and pricing adjustments in accordance with the offtake contracts.
MAG FINANCIAL RESULTS – THREE MONTHS ENDED MARCH 31, 2024
As at March 31, 2024, MAG had working capital of $72,833 (December 31, 2023: $67,262) including cash of $74,683 (December 31, 2023: $68,707) and no long-term debt. As well, as at March 31, 2024, Juanicipio had working capital of $107,088 including cash of $30,991 (MAG’s attributable share is 44%).
The Company’s net income for the three months ended March 31, 2024 amounted to $14,895 (March 31, 2023: $4,713) or $0.14/share (March 31, 2023: $0.05/share). MAG recorded its 44% income from equity accounted investment in Juanicipio of $19,244 (March 31, 2023: $7,919) which included MAG’s 44% share of net income from operations as well as loan interest earned on loans advanced to Juanicipio (see above for MAG’s share of income from its equity accounted investment in Juanicipio).
https://preview.redd.it/5bneimszze0d1.png?width=720&format=png&auto=webp&s=323d988dbd92cf6ca4e815fff071c8ec7f45ee00
NON-IFRS MEASURES
The following table provides a reconciliation of cash cost per silver ounce of Juanicipio to production cost of Juanicipio on a 100% basis (the nearest IFRS measure) as presented in the notes to the Q1 2024 Financial Statements.
https://preview.redd.it/0jhh2stzze0d1.png?width=720&format=png&auto=webp&s=c97634763bd00967ddd878bc09b8e069687fae68
(1) As Q3 2023 represented the first full quarter of commercial production, information presented for total cash costs together with their associated per unit values are not directly comparable.
(2) By-product revenues relates to the sale of other metals namely gold, lead, and zinc.
(3) Equivalent silver payable ounces have been calculated using realized prices to translate gold, lead and zinc to “equivalent” silver payable ounces (metal quantity, multiplied by metal price, divided by silver price). Q1 2024 realized prices: $23.73/oz silver, $2,112.27/oz gold, $0.92/lb lead and $1.08/lb zinc (Q1 2023: $22.93/oz silver, $1,959.50/oz gold, $0.94/lb lead and $1.43/lb zinc).
The following table provides a reconciliation of AISC of Juanicipio to production cost and various operating expenses of Juanicipio on a 100% basis (the nearest IFRS measure), as presented in the notes to the Q1 2024 Financial Statements.
https://preview.redd.it/qkx2r5vzze0d1.png?width=720&format=png&auto=webp&s=0c9cb89471512649ac77b5cbe3177b0621d64835
(1) As Q3 2023 represented the first full quarter of commercial production, information presented for all-in sustaining costs and all-in sustaining margin together with their associated per unit values are not directly comparable.
(2) Equivalent silver payable ounces have been calculated using realized prices to translate gold, lead and zinc to “equivalent” silver payable ounces (metal quantity, multiplied by metal price, divided by silver price). Q1 2024 realized prices: $23.73/oz silver, $2,112.27/oz gold, $0.92/lb lead and $1.08/lb zinc, (Q1 2023 realized prices: $22.93/oz silver, $1,959.50/oz gold, $0.94/lb lead and $1.43/lb zinc).
For the three months ended March 31, 2024 the Company incurred corporate G&A expenses of $3,964 (three months ended March 31, 2023: $3,262), which exclude depreciation expense.
The Company’s attributable silver ounces sold and equivalent silver ounces sold for the three months ended March 31, 2024 were 1,757,630 and 2,475,862 respectively (three months ended March 31, 2023: 880,429 and 1,230,412 respectively), resulting in additional all‐in sustaining cost for the Company of $2.26/oz and $1.60/oz respectively (three months ended March 31, 2023: $3.71/oz and $2.65/oz respectively), in addition to Juanicipio’s all-in-sustaining costs presented in the above table.
The following table provides a reconciliation of EBITDA and Adjusted EBITDA attributable to the Company based on its economic interest in Juanicipio to net income (the nearest IFRS measure) of the Company per the Q1 2024 Financial Statements. All adjustments are shown net of estimated income tax.
https://preview.redd.it/sx6jo7wzze0d1.png?width=720&format=png&auto=webp&s=1fea9df2b8195ce579b570935ab24b9939da5988
(1) As Q3 2023 represents the first full quarter of commercial production, information presented for EBITDA and Adjusted EBITDA is not directly comparable.
The following table provides a reconciliation of free cash flow of Juanicipio to its cash flow from operating activities on a 100% basis (the nearest IFRS measure), as presented in the notes to the Q1 2024 Financial Statements.
https://preview.redd.it/aqnp2dxzze0d1.png?width=720&format=png&auto=webp&s=56db2245eb87ec1f718edc1890b48b9b5d3ad762
(1) As Q3 2023 represents the first full quarter of commercial production, comparative information presented for free cash flow of Juanicipio is not directly comparable.
Qualified Persons: All scientific or technical information in this press release including assay results referred to, and mineral resource estimates, if applicable, is based upon information prepared by or under the supervision of, or has been approved by Gary Methven, P.Eng., Vice President, Technical Services and Lyle Hansen, P.Geo, Geotechnical Director; both are “Qualified Persons” for purposes of National Instrument 43-101, Standards of Disclosure for Mineral Projects
About MAG Silver Corp.
MAG Silver Corp. is a growth-oriented Canadian exploration company focused on advancing high-grade, district scale precious metals projects in the Americas. MAG is emerging as a top-tier primary silver mining company through its (44%) joint venture interest in the 4,000 tonnes per day Juanicipio Mine, operated by Fresnillo plc (56%). The mine is located in the Fresnillo Silver Trend in Mexico, the world's premier silver mining camp, where in addition to underground mine production and processing of high-grade mineralised material, an expanded exploration program is in place targeting multiple highly prospective targets. MAG is also executing multi-phase exploration programs at the 100% earn-in Deer Trail Project in Utah and the 100% owned Larder Project, located in the historically prolific Abitibi region of Canada.
Neither the Toronto Stock Exchange nor the NYSE American has reviewed or accepted responsibility for the accuracy or adequacy of this press release, which has been prepared by management.
Certain information contained in this release, including any information relating to MAG’s future oriented financial information, are “forward-looking information” and “forward-looking statements” within the meaning of applicable Canadian and United States securities legislation (collectively herein referred as “forward-looking statements”), including the “safe harbour” provisions of provincial securities legislation, the U.S. Private Securities Litigation Reform Act of 1995, Section 21E of the U.S. Securities Exchange Act of 1934, as amended and Section 27A of the U.S. Securities Act. Such forward-looking statements include, but are not limited to:
  • statements that address maintaining the nameplate 4,000 tpd milling rate at Juanicipio;
  • statements that address our expectations regarding exploration and drilling;
  • statements regarding production expectations and nameplate;
  • statements regarding the additional information from future drill programs;
  • estimated future exploration and development operations and corresponding expenditures and other expenses for specific operations;
  • the expected capital, sustaining capital and working capital requirements at Juanicipio, including the potential for additional cash calls;
  • expected upside from additional exploration;
  • expected results from Deer Trail Project drilling;
  • expected results from the Larder Project at the Fernland, Cheminis, and Bear zones;
  • expected capital requirements and sources of funding; and
  • other future events or developments.
When used in this release, any statements that express or involve discussions with respect to predictions, beliefs, plans, projections, objectives, assumptions or future events of performance (often but not always using words or phrases such as “anticipate”, “believe”, “estimate”, “expect”, “intend”, “plan”, “strategy”, “goals”, “objectives”, “project”, “potential” or variations thereof or stating that certain actions, events, or results “may”, “could”, “would”, “might” or “will” be taken, occur or be achieved, or the negative of any of these terms and similar expressions), as they relate to the Company or management, are intended to identify forward-looking statements. Such statements reflect the Company’s current views with respect to future events and are subject to certain known and unknown risks, uncertainties and assumptions.
Forward-looking statements are necessarily based upon estimates and assumptions, which are inherently subject to significant business, economic and competitive uncertainties and contingencies, many of which are beyond the Company’s control and many of which, regarding future business decisions, are subject to change. Assumptions underlying the Company’s expectations regarding forward-looking statements contained in this release include, among others: MAG’s ability to carry on its various exploration and development activities including project development timelines, the timely receipt of required approvals and permits, the price of the minerals produced, the costs of operating, exploration and development expenditures, the impact on operations of the Mexican tax and legal regimes, MAG’s ability to obtain adequate financing, outbreaks or threat of an outbreak of a virus or other contagions or epidemic disease will be adequately responded to locally, nationally, regionally and internationally.
Although MAG believes the expectations expressed in such forward-looking statements are based on reasonable assumptions, such statements are not guarantees of future performance and actual results or developments may differ materially from those in the forward-looking statements. These forward-looking statements involve known and unknown risks, uncertainties and many factors could cause actual results, performance or achievements to be materially different from any future results, performance or achievements that may be expressed or implied by such forward-looking statements including amongst others: commodities prices; changes in expected mineral production performance; unexpected increases in capital costs or cost overruns; exploitation and exploration results; continued availability of capital and financing; general economic, market or business conditions; risks relating to the Company’s business operations; risks relating to the financing of the Company’s business operations; risks related to the Company’s ability to comply with restrictive covenants and maintain financial covenants pursuant to the terms of the Credit Facility; the expected use of the Credit Facility; risks relating to the development of Juanicipio and the minority interest investment in the same; risks relating to the Company’s property titles; risks related to receipt of required regulatory approvals; pandemic risks; supply chain constraints and general costs escalation in the current inflationary environment heightened by the invasion of Ukraine by Russia and the events relating to the Israel-Hamas war; risks relating to the Company’s financial and other instruments; operational risk; environmental risk; political risk; currency risk; market risk; capital cost inflation risk; risk relating to construction delays; the risk that data is incomplete or inaccurate; the risks relating to the limitations and assumptions within drilling, engineering and socio-economic studies relied upon in preparing economic assessments and estimates, including the 2017 PEA; as well as those risks more particularly described under the heading “Risk Factors” in the Company’s Annual Information Form dated March 27, 2023 available under the Company’s profile on SEDAR+ at www.sedarplus.ca .
Should one or more of these risks or uncertainties materialize, or should underlying assumptions prove incorrect, actual results may vary materially from those described herein. This list is not exhaustive of the factors that may affect any of the Company’s forward-looking statements. The Company’s forward-looking statements are based on the beliefs, expectations and opinions of management on the date the statements are made and, other than as required by applicable securities laws, the Company does not assume any obligation to update forward-looking statements if circumstances or management’s beliefs, expectations or opinions should change. For the reasons set forth above, investors should not attribute undue certainty to or place undue reliance on forward-looking statements.
Please Note: Investors are urged to consider closely the disclosures in MAG's annual and quarterly reports and other public filings, accessible through the Internet at www.sedarplus.ca and www.sec.gov
LEI: 254900LGL904N7F3EL14
​
For further information on behalf of MAG Silver Corp. Contact Michael J. Curlook, Vice President, Investor Relations and Communications Phone: (604) 630-1399 Toll Free: (866) 630-1399 Email:info@magsilver.com
https://preview.redd.it/d8wzg8yzze0d1.jpg?width=66&format=pjpg&auto=webp&s=a39ec6a39761447bbd4dbd77e92aef49e95e583e
https://preview.redd.it/qr1wv0zzze0d1.png?width=4000&format=png&auto=webp&s=fadeb32c9245f8b70d903b1c70321decddf77985
Universal Site Links
MAG SILVER CORP.
STOCK METAL DATABASE
ADD TICKER TO THE DATABASE
www.reddit.com/Treaty_Creek
REPORT AN ERROR
submitted by Then_Marionberry_259 to Treaty_Creek [link] [comments]

2024.05.14 17:58 hvdub4 Advice combatting scammer

One of my clients (and 1 man show me by proxy) is having a "fun" time combatting a scammer. They have had several intrusions into their M365 accounts because of recycled passwords, volunteering information on scam forms, etc. I've tried educating them, but they have a fairly high turnover rate and a few employees that are of that older generation that trust anything they see on the screen in front of them. It's been almost a year since we've had a mailbox compromised, so I call that progress???
Current situation is that we now have 2 different users that "reached out" to vendors requesting financial changes to their accounts. One email originated from a fraudulent Gmail address (formatted as f.last.company@gmail.com), one from a spoofed domain; so 2 different issues. We found this out because the vendor contacted my client via phone to confirm a requested change - thank goodness for that!
Question 1 - So, how does one report to Gmail a spoofed email address without having the email headers? Is it possible to get the account banned or closed? I found a form on Gmail support but it wanted headers, message subject/body, etc that we don't have since it was sent to the vendor. Have their IT report it?
Question 2 - On the fraudulent domain (the scammer just registered this a few weeks ago) they used a typo of the company name and set up apparently legit mailbox structure for communicating with people. ie: f.last@compan.com instead of f.last@company.com - I've already filed an abuse report at the site it was registered at but with little hope of getting it dealt with.
Any suggestions on how to help shore up this client against these types of attacks? Yes, we have DKIM, SPF, etc already in place, but other than trying to register all permutations of the domain misspellings? All advice will be appreciated - I'm feeling a little out of my league here!
submitted by hvdub4 to msp [link] [comments]

2024.05.14 17:57 Amphibian_Basic Firs impressions feedback

I love the idea of Kosmik but the execution isnt quite there yet. I plan on trying it out further but theres a couple of things that get in the way. This is my first impressions review and what i intend as constructive feedback
Usability (testing on windows 10)
Smaller stuff easy to improve (but are creating attrition for me constantly)
At least on windows feels a bit undercooked. I dont know wether some of those are design choices or features still missing but i feel the design a bit at odds- in some parts it conveys 'use mouse only/first' in others it demands keyboard, and in the mean time some of the common design patterns both for mouse and keyboard arent used or use some non-tradional choice- making it harder to learn, creating some confusion or wrong expectations.
For example the bookmark icon is a vey tradional and ubiqutuous skeumorphic symbol for a very common feature that saves urls or files in a list, tradionally urls. Some apps get away using then for favorite files, photos or other things given their context so the user can imagine the equivalent in a given context... but here it shows alongside the in-app browser, next to an url... Maybe a different icon, like a card with a Plus sign and a tip 'add to canvas'?
I dont understand why tags are in the browser if apparently they only work with cards added on the canvas. If the intent was treating the open browser as a canvas element then said browser should be like a card (for example being able to open multiple browser windows in different universes) as if they were cards. Right now the browser is like a temporary tool...
If the intention (im trying to deduce here) was to apply tags before bookmarking so the bookmark already apply said tags then both operations would work better together- 1 button, the add-site to canvas, and that button opening up a prompt to add tags before confirming if desired.
Overall- Service, app, marketing
I was a bit misled regarding expectations because of a video/moto 'best browser for research' - so i installed it expecting more of a Browser with a canvas then a canvas with a very limited in-app browser. So i came expecting multiple tabs or adding extensions...
I dont mean to say the app should be like a browser BUT it is a interesting area to improve and turn into its differential, given some of the competition and how most people would be using it alongside a browser anyway
In a general sense my impressions:
From the 'best browser for research' perspective:
I wonder if the app allowed for pages inside cards (not previews, rendered pages) would be a good alternative for things like tabs
From a general canvas-notation perspective
I have used waaay too many notes and canvas apps in my search for the apps that filled that niche for me like id like, and heck for years a good app with canvas was my most wanted feature that almost no one was doing save for few clunky flowchart apps.
Im glad that now theres been a boom of options and ive been giving everyone a chance- but still not one have all the things id like (i could pinpoint a frankenstein of features from different apps id wish into one)... Kosmik is already ahead of half of the competition (imo) just by having both a native app and web view options, and by the apps having the files locally+sync instead of rendering from the cloud only all the time (much faster and snappiers wich is a big deal for me) - and the web/browsing+canvas angle is a very interesting proposition
But that is where i got disapointed- the web-browsing in app alongside canvas is still very limited to hit the potential of that proposition. As it is right now, for example, i feel more confortable having any browser in a smaller window and copy-pasting urls into Kosmik then relying fully on the internal browser, save for quick search queries
I focus so much on the browser aspect not only because it was how i first found about kosmik but also because without that angle it falls short on some alternatives. Not completely btw, drawing tools and pdf handling seem to be great and ahead of some alternatives (some are good at drawing but barely beyond that, others better as notes but with terrible or no drawing)...
But i still feel like the 'best app for research' (browser+canvas/notes+pdf), emphasis on the browsing is the best angle, best bet for Kosmik to grow above alternatives... but extra emphasis on potential- i dont feel like its hitting that note quite yet, at least not on windows.
I will try to stick with Kosmik for awhile despite the clunkiness and attriction i feel, but not as id like to use it and more like a buffer between traditional browsing/searching and taking my notes- im planing on inserting Kosmik in between as quick notes for links before later refering to then on notes elsewhere... but i confess im sort of forcing this workflow just to keep using kosmik and keep tabs on updates- im sticking around in the hopes of what may come and not for what it currently is.
I have high hopes for the app and in my case (i lean more towards power user then casual) even if i use other apps a good better version of Kosmik in this niche would fit for me even alongside other apps. Heck i currently use 2 similars in tandem (similar in notes/canvas) for their different strengths and niches- and neither have carved web browsing research as their niche
Anyway, those were my very long 2cents. I hope the feedback is taken positively
submitted by Amphibian_Basic to kosmik_app [link] [comments]

2024.05.14 17:52 ZealousidealNobody22 Home assistant Chat GPT4o intergration

i was on chat gpt and asked it to create an intergration for chatgpt into home assistant and this is what it came up with

Step 1: Home Assistant Custom Component

First, create a custom component in Home Assistant to interface with the ChatGPT API.
Directory structure:
luaCopy code /config/custom_components/chatgpt_integration/ -- __init__.py -- manifest.json -- services.yaml
__init__.py:
pythonCopy code import openai import homeassistant.helpers.config_validation as cv import voluptuous as vol from homeassistant.core import HomeAssistant from homeassistant.helpers.typing import ConfigType, ServiceCall DOMAIN = 'chatgpt_integration' CONF_API_KEY = 'api_key' CONFIG_SCHEMA = vol.Schema({ DOMAIN: vol.Schema({ vol.Required(CONF_API_KEY): cv.string, }) }, extra=vol.ALLOW_EXTRA) def setup(hass: HomeAssistant, config: ConfigType): api_key = config[DOMAIN][CONF_API_KEY] openai.api_key = api_key def handle_chatgpt_request(call: ServiceCall): prompt = call.data.get('prompt') response = openai.Completion.create(engine="text-davinci-004", prompt=prompt, max_tokens=150) hass.states.set('chatgpt_integration.response', response.choices[0].text.strip()) hass.services.register(DOMAIN, 'ask', handle_chatgpt_request) return True
manifest.json:
jsonCopy code { "domain": "chatgpt_integration", "name": "ChatGPT Integration", "version": "1.0", "requirements": ["openai"], "dependencies": [], "codeowners": [] }
services.yaml:
yamlCopy code ask: description: "Ask ChatGPT a question" fields: prompt: description: "The question to ask ChatGPT" example: "What's the weather like today?"

Step 2: Web Interface

Create a simple HTML file to serve as the front end for interacting with the ChatGPT service in Home Assistant.
index.html:
htmlCopy code     Home Assistant ChatGPT Interface    
 
Home Automation with ChatGPT

Step 3: Deploy the Web Interface

To serve the index.html file, you can use Home Assistant’s built-in web server or another web server like Nginx or Apache.
Option 1: Serving with Home Assistant (simpler) Place index.html in the /config/www directory and access it via http://your-home-assistant-url/local/index.html.
Option 2: Serving with Nginx (advanced) Set up an Nginx server to serve the index.html file and proxy requests to Home Assistant.

Step 4: Testing

  1. Ensure your Home Assistant is running and the custom component is properly loaded.
  2. Access the web interface via http://your-home-assistant-url/local/index.html.
  3. Enter a prompt and see the response from ChatGPT displayed.
This example demonstrates a basic integration. For a production-ready solution, consider adding error handling, security measures (like API key protection), and a more sophisticated frontend framework.
submitted by ZealousidealNobody22 to homeassistant [link] [comments]

2024.05.14 17:30 ExaminationOdd8421 user_proxy.initiate_chat summary_args

I created an agent that given a query it searches on the web using BING and then using APIFY scraper it scrapes the first posts. For each post I want a summary using summary_args but I have a couple of questions:
  1. Is there a limit on how many things can we have with the summary_args? When I add more things I get: Given the structure you've requested, it's important to note that the provided Reddit scrape results do not directly offer all the detailed information for each field in the template. However, I'll construct a summary based on the available data for one of the URLs as an example. For a comprehensive analysis, each URL would need to be individually assessed with this template in mind. (I want all of the URLs but it only outputs one)
  2. Is there a way to store locally the summary_args? Any suggestions?
    chat_result = user_proxy.initiate_chat( manager, message="Search the web for information about Deere vs Bobcat on reddit,scrape them and summarize in detail these results.", summary_method="reflection_with_llm", summary_args={ "summary_prompt": """Summarize for each scraped reddit content and format summary as EXACTLY as follows: data = { URL: url used, Date Published: date of post or comment, Title: title of post, Models: what specific models are mentioned?, ... (15 more things)... } """
Thanks!!!
submitted by ExaminationOdd8421 to AutoGenAI [link] [comments]

2024.05.14 17:28 Astrid_Nicrosil POV: you are browsing Tumblr in 2023

Just a friendly reminder that it's okay for men to be gender non-conforming! Just because a cis guy is feminine doesn't mean he's trans! If anything, being a cis gender non-conforming man is even more radical and challenging than being a trans woman!
(Screenshot of a post a trans woman made, joking that a stranger she saw buying floral scented bodywash was egg behavior. Post has 4 notes.) Calling someone an egg is misgendering, even if you yourself are trans. Trans women need to learn to stop grooming coercing gnc men into identifying as something they're not. Saying someone's an egg is really bioessentialist, and, tbh? TERF behavior. (Post has 12k notes)
(Reblog) This is so so important. I'm a femboy and my trans woman friend called me an egg once and it made me uncomfortable, so obviously this is a systemic issue and not my friend being a bit of an ass.
Call out post for (mildly popular trans woman) (her blog is 18+ and she actively blocks minors who follow her). They (she uses she/her exclusively) reblogged mildly suggestive art, and when confronted they refused to hold themselves accountable, saying "literally am I not allowed to have a sexuality?" This aggressiveness and hypersexuality are clear indications they are a predator due to amab socialization.
Most Annoying Blog Tournament!
Contestants: - a literal Nazi - a literal Nazi - mildly popular and annoying trans woman - mildly popular and annoying trans woman - a literal pedophile - mildly popular and annoying trans woman - literal Nazi and pedophile
! WARNING: THIS POST HAD BEEN FLAGGED SEXUALLY EXPLICIT, PORNOGRAPHIC AND DEGENERATE!
transition timeline :3 (Two pictures of a trans woman. Both are profile shots, and she is fully clothed in each. The first is labled 'pre-HRT', the second is labeled '2 years HRT'. She is smiling brightly in the second picture.)
(Official post from staff) We've been receiving reports that safe-for-work posts by trans women are being flagged as sexually explicit. We have investigated the algorithm used to determine NSFW content and determined it was in fact due to human action. We know there have been concerns about staff members being TERFs or being transmisogynistic in the past, since trans women especially have been randomly banned for no reason, but rest assured, if you inquire about this further your blog and every single one of your posts will be scrubbed from the site using our never before seen moderation tools.
Why do we need to use TME (transmisogyny exempt) and TMA (transmisogyny affected) anyway? It's just AMAB and AFAB (it's not), and, really, anyone can be affected by transmisogyny! A cis guy wearing fingernail polish is equally affected by transmisogyny as a trans woman. There's nothing inherently unique about the oppression trans women experience, so language like this only serves to divide the community.
(Reblog) TME/TMA wasn't really a thing until all the girls with urls like mousegirlthighs and coyotegirlcock showed up. Speaking which, what's with those urls? They're always so sexual and always so surprised when no one takes them seriously... (User is named prolapsenecrosis and posts untagged guro)
(Transmisogynistic caricature from popular media in the 2000s) is such a genderqueer icon 🤩🤩
Just a friendly reminder that it's okay to be for men to be gender-nonconforming!
/Uj I wrote this about a year ago and it's been sitting in my drafts. Would you believe it's only gotten worse?
I could put more effort into formatting this to look like actual Tumblr posts and make fake urls and everything but whatever. Apologies to the real mousegirlthighs, coyotegirlcock, and prolapsenecrosis if you exist.
submitted by Astrid_Nicrosil to transgendercirclejerk [link] [comments]

2024.05.14 17:16 Then_Marionberry_259 MAY 14, 2024 FR.TO FIRST MAJESTIC REMINDS SHAREHOLDERS TO VOTE IN UPCOMING ANNUAL GENERAL MEETING

MAY 14, 2024 FR.TO FIRST MAJESTIC REMINDS SHAREHOLDERS TO VOTE IN UPCOMING ANNUAL GENERAL MEETING
https://preview.redd.it/amc20qi8se0d1.png?width=3500&format=png&auto=webp&s=e2fae5d450ab83c349831614e8d9c1261014cb33
Vancouver, British Columbia--(Newsfile Corp. - May 14, 2024) - First Majestic Silver Corp. (NYSE: AG) (TSX: FR) (FSE: FMV) (the "Company" or "First Majestic") reminds its shareholders about the Company's upcoming Annual General Meeting of Shareholders (the "2024 AGM") scheduled to take place on Thursday, May 23, 2024 at 10:00 a.m. (Pacific Time) at the Sutton Place Hotel located at 845 Burrard Street, Vancouver, British Columbia, V6Z 2K6.
The Board of Directors of First Majestic unanimously recommends that shareholders vote FOR all the resolutions that have been put forward for the 2024 AGM.
The record date for notice and for voting at the 2024 AGM was March 28, 2024. Only shareholders as of the record date will be entitled to vote at the meeting. Shareholders as of the record date are encouraged to vote before the proxy voting deadline on Tuesday, May 21, 2024 at 10:00 a.m. (Pacific Time).
If you are a registered shareholder of the Company and are unable to attend the 2024 AGM, please read, sign and date the form of proxy for the meeting (the "Proxy") and deposit it with Computershare Investor Services Inc. ("Computershare") by courier or mail at 100 University Avenue, 8th Floor, Toronto, Ontario M5J 2Y1, Attention: Proxy Department, or by facsimile at 1-866-249-7775 (toll-free in North America) or 1-416-263-9524 (international) by 10:00 a.m. (Pacific Time) on Tuesday, May 21, 2024, or at least 48 hours (excluding Saturdays, Sundays and holidays) before any postponement or adjournment of the meeting). Alternatively, registered shareholders may vote by telephone (1-866-732-8683) or online (www.investorvote.com) using the control number listed on the Proxy that they received from Computershare.
Non-registered shareholders may participate in the 2024 AGM (either themselves or through a proxyholder, or through intermediaries using the voting instruction form). Alternatively, some non-registered shareholders may be able to vote by telephone or online and should refer to the voting instruction form that they received for further details and instructions.
EVERY VOTE COUNTS
Voting is quick and easy. First Majestic has retained Kingsdale Advisors to provide shareholders with assistance in voting their shares, and they may be reached by telephone at 1-866-851-3214 (toll-free in North America) or 1-647-577-3635 (text and call enabled outside North America), or by email at [contactus@kingsdaleadvisors.com](mailto:contactus@kingsdaleadvisors.com).
To obtain current information about voting your First Majestic common shares, and for copies of the materials for the 2024 AGM, please visit www.firstmajesticagm.com, or scan the QR code below:
https://preview.redd.it/d82f1zo8se0d1.jpg?width=218&format=pjpg&auto=webp&s=5b92a1c645b14040aee870464450ea0170adc9f8
ABOUT THE COMPANY
First Majestic is a publicly traded mining company focused on silver and gold production in Mexico and the United States. The Company presently owns and operates the San Dimas SilveGold Mine, the Santa Elena SilveGold Mine, and the La Encantada Silver Mine as well as a portfolio of development and exploration assets, including the Jerritt Canyon Gold project located in northeastern Nevada, U.S.A.
First Majestic is proud to own and operate its own minting facility, First Mint, LLC, and to offer a portion of its silver production for sale to the public. Bars, ingots, coins and medallions are available for purchase online at www.firstmint.com, at some of the lowest premiums available.
For further information, contact [info@firstmajestic.com](mailto:info@firstmajestic.com), visit our website at www.firstmajestic.com or call our toll-free number 1.866.529.2807.
FIRST MAJESTIC SILVER CORP.
"Signed"
Keith Neumeyer, President & CEO
Cautionary Note Regarding Forward-Looking Statements
This news release contains "forward‐looking information" and "forward-looking statements" under applicable Canadian and U.S. securities laws (collectively, "forward‐looking statements"). These statements relate to future events or the Company's future performance, business prospects or opportunities that are based on forecasts of future results, estimates of amounts not yet determinable and assumptions of management made in light of management's experience and perception of historical trends, current conditions and expected future developments. Forward-looking statements include, but are not limited to, statements with respect to: the time and place of the 2024 AGM; the process of voting at the 2024 AGM; and the use of the online and telephone platforms to cast votes. Assumptions may prove to be incorrect and actual results may differ materially from those anticipated. All statements other than statements of historical fact may be forward‐looking statements. Although First Majestic has attempted to identify important factors that could cause actual results to differ materially from those contained in forward-looking statements, there may be other factors that cause results not to be as anticipated, estimated or intended.
The Company believes that the expectations reflected in these forward‐looking statements are reasonable, but no assurance can be given that these expectations will prove to be correct and such forward‐looking statements included herein should not be unduly relied upon. These statements speak only as of the date hereof. The Company does not intend, and does not assume any obligation, to update these forward-looking statements, except as required by applicable laws.
To view the source version of this press release, please visit https://www.newsfilecorp.com/release/209068
​
https://preview.redd.it/1yxdabv8se0d1.png?width=4000&format=png&auto=webp&s=cda284c426d82431cbf5faf4aa1574e029a16db3
Universal Site Links
FIRST MAJESTIC SILVER CORP. COM
STOCK METAL DATABASE
ADD TICKER TO THE DATABASE
www.reddit.com/Treaty_Creek
REPORT AN ERROR
submitted by Then_Marionberry_259 to Treaty_Creek [link] [comments]

2024.05.14 17:07 FistofDavid New to Python - Not understanding passing something to an argument

Hello! I just started dabbling with Python and came across a script on Github that I want to try. The issue is it requires me to pass the location of a source file as well as a location to place downloaded files and I'm not quite sure how to do this. I've tried different things like attempting to define variables in different ways, but no luck as I'm consistently getting syntax errors or what I've done is not defining it properly. The script is the following and the Github states to pass the source file as the first argument and the download location as the second argument. Would someone be able to help me understand where this should be defined and how to do so? Again, very new and inexperienced with Python and I get that this is probably advance for a beginner. Edit - Formatting
#!/usbin/env python # -*- encoding: utf-8 """ Download podcast files based on your Overcast export. If you have an Overcast account, you can download an OPML file with a list of every episode you've played from https://overcast.fm/account. This tool can read that OPML file, and save a local copy of the audio files for every episode you've listened to. """ import argparse import datetime import errno import filecmp import functools import glob import itertools import json import os import sqlite3 import sys from urllib.parse import urlparse from urllib.request import build_opener, install_opener, urlretrieve import xml.etree.ElementTree as ET def parse_args(argv): """Parse command-line arguments.""" parser = argparse.ArgumentParser(description=__doc__) parser.add_argument( "OPML_PATH", help="Path to an OPML file downloaded from https://overcast.fm/account", ) parser.add_argument( "--download_dir", default="audiofiles", help="directory to save podcast information to to", ) args = parser.parse_args(argv) return { "opml_path": os.path.abspath(args.OPML_PATH), "download_dir": os.path.abspath(args.download_dir), } def get_episodes(xml_string): """ Given the XML string of the Overcast OPML, generate a sequence of entries that represent a single, played podcast episode. """ root = ET.fromstring(xml_string) # The Overcast OPML has the following form: # #  #  # Overcast Podcast Subscriptions #  # ... # ... #  #  # # Within the  block of XML, there's a list of feeds # with the following structure (some attributes omitted): # #  #  # ... #  # # We use an XPath expression to find the  entries # (so we get the podcast metadata), and then find the individual # "podcast-episode" entries in that feed. for feed in root.findall("./body/outline[@text='feeds']/outline[@type='rss']"): podcast = { "title": feed.get("title"), "text": feed.get("text"), "xml_url": feed.get("xmlUrl"), } for episode_xml in feed.findall("./outline[@type='podcast-episode']"): episode = { "published_date": episode_xml.get("pubDate"), "title": episode_xml.get("title"), "url": episode_xml.get("url"), "overcast_id": episode_xml.get("overcastId"), "overcast_url": episode_xml.get("overcastUrl"), "enclosure_url": episode_xml.get("enclosureUrl"), } yield { "podcast": podcast, "episode": episode, } def has_episode_been_downloaded_already(episode, download_dir): try: conn = sqlite3.connect(os.path.join(download_dir, "overcast.db")) except sqlite3.OperationalError as err: if err.args[0] == "unable to open database file": return False else: raise c = conn.cursor() try: c.execute( "SELECT * FROM downloaded_episodes WHERE overcast_id=?", (episode["episode"]["overcast_id"],), ) except sqlite3.OperationalError as err: if err.args[0] == "no such table: downloaded_episodes": return False else: raise return c.fetchone() is not None def mark_episode_as_downloaded(episode, download_dir): conn = sqlite3.connect(os.path.join(download_dir, "overcast.db")) c = conn.cursor() try: c.execute("CREATE TABLE downloaded_episodes (overcast_id text PRIMARY KEY)") except sqlite3.OperationalError as err: if err.args[0] == "table downloaded_episodes already exists": pass else: raise c.execute( "INSERT INTO downloaded_episodes VALUES (?)", (episode["episode"]["overcast_id"],), ) conn.commit() conn.close() def _escape(s): return s.replace(":", "-").replace("/", "-") def get_filename(*, download_url, title): url_path = urlparse(download_url).path extension = os.path.splitext(url_path)[-1] base_name = _escape(title) return base_name + extension def download_url(*, url, path, description): # Some sites block the default urllib User-Agent headers, so we can customise # it to something else if necessary. opener = build_opener() opener.addheaders = [("User-agent", "Mozilla/5.0")] install_opener(opener) try: tmp_path, _ = urlretrieve(url) except Exception as err: print(f"Error downloading {description}: {err}") else: print(f"Downloading {description} successful!") os.rename(tmp_path, path) def download_episode(episode, download_dir): """ Given a blob of episode data from get_episodes, download the MP3 file and save the metadata to ``download_dir``. """ if has_episode_been_downloaded_already(episode=episode, download_dir=download_dir): return # If the MP3 URL is https://example.net/mypodcast/podcast1.mp3 and the # title is "Episode 1: My Great Podcast", the filename is # ``Episode 1- My Great Podcast.mp3``. audio_url = episode["episode"]["enclosure_url"] filename = get_filename(download_url=audio_url, title=episode["episode"]["title"]) # Within the download_dir, put the episodes for each podcast in the # same folder. podcast_dir = os.path.join(download_dir, _escape(episode["podcast"]["title"])) os.makedirs(podcast_dir, exist_ok=True) # Download the podcast audio file if it hasn't already been downloaded. download_path = os.path.join(podcast_dir, filename) base_name = _escape(episode["episode"]["title"]) json_path = os.path.join(podcast_dir, base_name + ".json") # If the MP3 file already exists, check to see if it's the same episode, # or if this podcast isn't using unique filenames. # # If a podcast has multiple episodes with the same filename in its feed, # append the Overcast ID to disambiguate. if os.path.exists(download_path): try: cached_metadata = json.load(open(json_path, "r")) except Exception as err: print(err, json_path) raise cached_overcast_id = cached_metadata["episode"]["overcast_id"] this_overcast_id = episode["episode"]["overcast_id"] if cached_overcast_id != this_overcast_id: filename = filename.replace(".mp3", "_%s.mp3" % this_overcast_id) old_download_path = download_path download_path = os.path.join(podcast_dir, filename) json_path = download_path + ".json" print( "Downloading %s: %s to %s" % (episode["podcast"]["title"], audio_url, filename) ) download_url(url=audio_url, path=download_path, description=audio_url) try: if filecmp.cmp(download_path, old_download_path, shallow=False): print("Duplicates detected! %s" % download_path) os.unlink(download_path) download_path = old_download_path except FileNotFoundError: # This can occur if the download fails -- say, the episode is # in the Overcast catalogue, but no longer available from source. pass else: # Already downloaded and it's the same episode. pass # This episode has never been downloaded before, so we definitely have # to download it fresh. else: print( "Downloading %s: %s to %s" % (episode["podcast"]["title"], audio_url, filename) ) download_url(url=audio_url, path=download_path, description=audio_url) # Save a blob of JSON with some episode metadata episode["filename"] = filename json_string = json.dumps(episode, indent=2, sort_keys=True) with open(json_path, "w") as outfile: outfile.write(json_string) save_rss_feed(episode=episode, download_dir=download_dir) mark_episode_as_downloaded(episode=episode, download_dir=download_dir) def save_rss_feed(*, episode, download_dir): _save_rss_feed( title=episode["podcast"]["title"], xml_url=episode["podcast"]["xml_url"], download_dir=download_dir ) # Use caching so we only have to download this RSS feed once. @functools.lru_cache() def _save_rss_feed(*, title, xml_url, download_dir): podcast_dir = os.path.join(download_dir, _escape(title)) today = datetime.datetime.now().strftime("%Y-%m-%d") rss_path = os.path.join(podcast_dir, f"feed.{today}.xml") if not os.path.exists(rss_path): print("Downloading RSS feed for %s" % title) download_url( url=xml_url, path=rss_path, description="RSS feed for %s" % title, ) matching_feeds = sorted(glob.glob(os.path.join(podcast_dir, "feed.*.xml"))) while ( len(matching_feeds) >= 2 and filecmp.cmp(matching_feeds[-2], matching_feeds[-1], shallow=False) ): os.unlink(matching_feeds[-1]) matching_feeds.remove(matching_feeds[-1]) if __name__ == "__main__": args = parse_args(argv=sys.argv[1:]) opml_path = args["opml_path"] download_dir = args["download_dir"] try: with open(opml_path) as infile: xml_string = infile.read() except OSError as err: if err.errno == errno.ENOENT: sys.exit("Could not find an OPML file at %s" % opml_path) else: raise for episode in get_episodes(xml_string): download_episode(episode, download_dir=download_dir)
submitted by FistofDavid to learnpython [link] [comments]

2024.05.14 16:55 WriteReflection How to use SEO to rank your social media content

SEO isn't just for website content. You can use SEO keyword strategy to rank your social media posts on sites like YouTube, Reddit, Instagram, and even Pinterest.
Entrepreneurs and small businesses already are at a disadvantage against larger competitors fighting for visibility online. Optimizing your social posts for search can help drive more visibility and engagement.
Just like webpage content benefits from SEO, using target keywords and other tactics can make your social updates more findable in search engines as well as inside the social media platforms themselves.
Here's how to do it.
  1. Use industry relevant keywords in posts, descriptions, and hashtags Identify the primary keywords and phrases you want to rank for and then naturally work them into the text updates, image captions, hashtags, and meta descriptions. This helps your content show up when people search for those terms.
  2. Optimize your social profiles Make sure your brand/business name, bio, website URL, and other profile information uses relevant keywords. This interconnected web of signals ties everything together for crawlers looking for content to match the search queries.
  3. Share links to optimized content Any time you create a new blog post, service page, or other SEO-optimized webpage, share a link through your social channels. Never put links in the main body of social media posts. Instead, put them in the first comment of the post. This drives visibility and can help build relevant backlinks.
  4. Use hashtags intelligently Trending hashtags might get your content seen. Using them can also bury your content among the masses of other brands using the same strategy. Instead, use niche, descriptive hashtags around your target keywords.
  5. Engage your audience Actively engaging with the people in your comment section signals to search engines that your social content is relevant and valuable. Encourage interaction by asking questions, running polls, and hosting Q&A sessions. Make sure someone from your business acknowledges posters and answers questions when possible.
  6. Post consistently There's no magic formula for how often you should post to boost SEO. However, we recommend maintaining a consistent publishing cadence rather than posting in bursts when the mood strikes. The algorithms will learn to predict your posting pattern and prioritize your content for search.
Have more questions about how to SEO your social media content? Post them in the comments.
submitted by WriteReflection to SmallBizContent [link] [comments]

2024.05.14 16:25 customEntregineer Help Needed: Persistent Resource Consumption Issues with WooCommerce Site on VPS

Hi everyone,
I’m facing a persistent issue with a WooCommerce eCommerce website I built using a template purchased from ThemeForest. The site has been running fine for over three years, but for the past 3-4 months, it has been experiencing frequent downtime due to high resource consumption. Here's a rundown of the problem:
This website is critical for my friend (I'm helping for free because I recommended the one who made the website initially 3 years ago), and his business heavily relies on it. I’m feeling a lot of pressure to get this resolved.
Has anyone experienced a similar issue? Any suggestions on what else I can try? Any help or advice would be greatly appreciated!
Thank you in advance!
EDIT : here is the url of the website : https://goldenbabyshop.com/
submitted by customEntregineer to Wordpress [link] [comments]

2024.05.14 15:56 SignalPractical4526 Need help with OAuth - New to Flet, New to Dev

Hi All,
I am a noobie developer. I am trying to implement google oauth for my app but I am not sure what the issue is, it just doesnt work. For experimentation purposes I tried with github also but I face the same problem.
  1. I created the Oauth concent screen with the appropriate test users and scope
  2. I generated the necessary credentials with the appropriate origin and redirect URL
  3. Very rightly added the creds to my code
  4. Created my program (see below)
  5. I run the program, site at http://localhost:8550 runs, I click on the button and I am redirected to google
  6. I authenticate and agree and then I am redirected to the site http://localhost:8550/api/oauth/redirect
  7. Redirect URL looks like this : http://localhost:8550/api/oauth/redirect?state=yrn7z2dqtAt76WLGUL7LEg&code=4/0AdLIrYfzkcG1tQYc4mXRSFyxAUacsW78HgU4sdqWN-ogIgmJwZJAma4WBVY4WrEckFLFVA&scope=email+profile+openid+https://www.googleapis.com/auth/userinfo.profile+https://www.googleapis.com/auth/userinfo.email&authuser=1&prompt=consent
but after this nothing happens. The on_login() function simply remains untouched, nothing is printed, this is probably because the authentication is not complete. But others seem to be getting this to work with the exact same code. 
import flet from flet import * from flet.auth.providers import GoogleOAuthProvider clientID = "960907517986-pn9g4a6vou7spkv5dcqp9e5lveeqr9la.apps.googleusercontent.com" clientSecret = "GOCSPX-UwIdBmnIyu2bayHFtejMXXXXXXXX" def main(page: Page): provider = GoogleOAuthProvider( client_id=clientID, client_secret=clientSecret, redirect_url="http://localhost:8550/api/oauth/redirect", ) resulttxt=Column() def logingoogle(e): page.login(provider, scope=["https://www.googleapis.com/auth/userinfo.email", "https://www.googleapis.com/auth/userinfo.profile"]) def on_login(e): print(page.auth.user) resulttxt.controls.append( Column([ Text(f"name : {page.auth.user['name']}"), Text(f"email : {page.auth.user['email']}"), ]) ) page.update() page.on_login = on_login page.add( Column([ Text("Login Google", size=30), ElevatedButton("Sign google", bgcolor="blue", color="white", on_click=logingoogle ), resulttxt ]) ) flet.app(target=main, port=8550, view=WEB_BROWSER)
The tutorial I followed is : https://www.youtube.com/watch?v=t9ca2jC4YTo&t=20s
I tried using other oauth provider like Github, but same issue. I am redirected to the page with code after that nothing happens.
I am not sure if this will help, I am doing this on a mac m1. I have also tried with both chrome and firefox.
submitted by SignalPractical4526 to flet [link] [comments]

2024.05.14 15:02 marijuanahh Error: Local Access

'Your browser is misconfigured. Do not use the proxy to access the router console, localhost, or local LAN destinations.' i haven't used i2p for about a year, now when i run the app i cant access any sites and this is the error i get. Can anyone please help?
submitted by marijuanahh to i2p [link] [comments]

http://rodzice.org/