OUT
OUTFRONT Media Inc.
stockNYSE

# PURE # UNADULTERATED # FOMOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO # GET THE FUCK IN OR BE LEFT THE FUCK OUT

THATS THE DELL TOP GET THE FUCK OUT NOW

Didn’t buy calls yesterday. First time in weeks. 1% day. Buying calls today. WATCH OUT

# QQQ 770 TODAY # CALLS AT OPEN # DO NOT BE LEFT OUT!!!!!

I'm very much enjoying all the "BREAKING OUT" of completely meaningless lines they've been talking about today. Which it kind of had to do, because the lines were converging on a point.

TAKE MY STONK'S NAME OUT YOUR MOTHER FUCKING MOUTH!

# ITS GIVING BLOWN THE ABSOLUTE FUCK OUT ON PUTS :kek: :kek: :kek:

TOMORROW SPY "CRASHES" BACK DOWN TO 772 AND ALL THE SEETHING ANGRY BEARS IN THIS SUB: "SEE I TOLD YOU SO" WHILE CASHING OUT PUTS FOR -65% :kek: :kek: :kek:

"The Fake News New York Times “reported” on my Great, PACKED Rally in Ohio that, “the place was not full. Some upper sections were almost completely empty.” In actuality, thousands of people were unable to get in. The Arena was totally MAXED OUT, including all upper sections. What does happen at all of my SOLD OUT Rallies, is that the people in the upper sections tend to migrate down to the Main Floor — The “migration” process always happens! The Times knows this, and so does everyone else. I never have empty seats — Never have, and never will! Because of their dishonesty, I have cinematographers shooting the various Arenas where I speak, in that some of the Fake News likes to dishonestly report lies and untruths. In actuality, my Events for very good Republican Politicians are probably more crowded than ever. There are no empty seats, there haven’t been for years, and there never will be. The Rallies are “HOTTER” than ever. They are all “happenings,” and they never happened before, and will never be duplicated again. The Networks refuse, however, under any circumstances, to show the Crowds, but you can hear the thunderous applause, and know that it represents thousands and thousands of people. Watch tonight, for example, in the Great State of Nebraska, where I’ll be heading soon. See you later!"

RUSSIAN PLAGUE IS OUT THERE, NEXT THING WE KNOW RASPUTIN IS MAKING A COMEBACK.

# BEARS OUT DOWNVOTING EN MASSE BECAUSE FREE INTERNET POINTS ARE THEY ONLY THING THEY HAVE LEFT TO SPEND :kek :kek: :kek: :kek:

OMFG I 🅱️USSIED OUT AND SOLD MY SPX CALLS TOO EARLY 🔪

# QQQ 760 GAP UP TOMORRROW # DO NOT BE LEFT OUT

# PSA WE HAVE 3 LONG DURATION TREASURY AUCTIONS THIS WEEK - BOND VIGILANTES ARE JUST SPIKING YIELDS BEFORE BUYING THE ABSOLUTE FUCK OUT OF THEM TO LOCK IN THAT FREE MONEY # DON'T GET CAUGHT UP IN THIS BEARISH BS THESIS

WTF IS THIS BULLSHIT JUST BREAK OUT ALREADY 🤬🤬🤬🤬🤬🤬🤬🤬🤬

# HERE COMES THE BREAK OUT!!!!!!!!

# HERE COMES ANOTHER BRAND SPANKING NEW ALL TIME HIGH ON QQQ!!!!!! # DO NOT BE LEFT OUT

JUST SOLD, IM OUT WITH $$$$$$

No. Crying. In. The. Casino. Get OUT.

# ============================================================================= # llama-elana - standalone TCP inference host for llama.cpp # # This folder contains ONLY our code. It is a normal subfolder of a llama.cpp # source tree and reaches the whole engine ONE LEVEL UP: # # <llama.cpp>/llama-elana/CMakeLists.txt <- this file # <llama.cpp>/CMakeLists.txt <- the untouched llama.cpp root # # The trick is the add_subdirectory(.. ) below: it pulls the ORIGINAL llama.cpp # build in as a child of this project, EXCLUDE_FROM_ALL, so nothing from the # upstream tree is built except what our target actually links. No source file # is copied, symlinked or patched - they are compiled straight from ../. # # That also makes this folder portable: copy it to any llama.cpp checkout and # ./build.sh works there, building against THAT checkout's sources. # # What gets linked (and what deliberately does NOT): # llama ggml llama-common llama-common-base mtmd server-context <- ours # llama-server-impl llama-server llama-ui cpp-httplib <- NOT linked # # server-context is the HTTP-free half of llama-server (context, slots, tasks, # sampling, template, multimodal). We compile its sources directly instead of # adding tools/ as a subdirectory, because tools/ also drags in llama-ui (which # downloads web assets) and llama-server-impl (which needs cpp-httplib). The # source list is READ FROM the upstream tools/server/CMakeLists.txt at configure # time, so if upstream adds a file to server-context we pick it up automatically # instead of silently building a stale set. # ============================================================================= cmake_minimum_required(VERSION 3.14) project(llama-elana C CXX) # Make the RUNPATH that CMake generates $ORIGIN-relative, including the entries it # adds automatically for every linked shared library. Without this CMake appends # the absolute build path of libggml-cpu.so/libggml-cuda.so, so a copied build/ # folder silently loads those two backends out of the tree it was built in. set(CMAKE_BUILD_RPATH_USE_ORIGIN ON) # ----------------------------------------------------------------------------- # Locate the llama.cpp source root: one folder up. # ----------------------------------------------------------------------------- set(LLAMA_ROOT "${CMAKE_CURRENT_SOURCE_DIR}/.." CACHE PATH "llama.cpp source tree to build against (defaults to the parent folder)") # get_filename_component works on CMake 3.14+ (cmake_path would need 3.20) get_filename_component(LLAMA_ROOT "${LLAMA_ROOT}" ABSOLUTE) if (NOT EXISTS "${LLAMA_ROOT}/CMakeLists.txt") message(FATAL_ERROR "No llama.cpp source tree at '${LLAMA_ROOT}'.\n" "This folder is meant to live INSIDE a llama.cpp checkout " "(<llama.cpp>/llama-elana). Point -DLLAMA_ROOT=<path> at one, or copy " "this folder into a llama.cpp source directory.") endif() if (NOT EXISTS "${LLAMA_ROOT}/tools/server/server-context.cpp") message(FATAL_ERROR "'${LLAMA_ROOT}' has a CMakeLists.txt but no tools/server/server-context.cpp.\n" "llama-elana needs a llama.cpp tree that ships the server-context library " "(llama.cpp >= b5xxx, the split that separated server-context from the HTTP layer).") endif() message(STATUS "llama-elana: building against llama.cpp at ${LLAMA_ROOT}") # ----------------------------------------------------------------------------- # Defaults that differ from upstream, set BEFORE the parent project() runs so # they win over upstream's option() defaults. # ----------------------------------------------------------------------------- # We only ever want our own executable: no tests, examples, tools, app or Web UI. # (Upstream turns these ON for a standalone build; we are not standalone.) set(LLAMA_BUILD_TESTS OFF CACHE BOOL "" FORCE) set(LLAMA_BUILD_EXAMPLES OFF CACHE BOOL "" FORCE) set(LLAMA_BUILD_TOOLS OFF CACHE BOOL "" FORCE) set(LLAMA_BUILD_APP OFF CACHE BOOL "" FORCE) set(LLAMA_BUILD_UI OFF CACHE BOOL "" FORCE) set(LLAMA_BUILD_COMMON ON CACHE BOOL "" FORCE) # arg parsing, chat template, sampler # mtmd (multimodal/mmproj) lives under tools/mtmd. With LLAMA_BUILD_TOOLS=OFF the # upstream root only adds it when LLAMA_BUILD_MTMD is ON (see CMakeLists.txt:258), # and then the library alone - the mtmd CLI executables stay gated out. set(LLAMA_BUILD_MTMD ON CACHE BOOL "" FORCE) # Shared libs, like the upstream build, so the result uses libllama.so/libggml.so. set(BUILD_SHARED_LIBS ON CACHE BOOL "build shared libraries" FORCE) if (NOT CMAKE_BUILD_TYPE) set(CMAKE_BUILD_TYPE Release CACHE STRING "Build type" FORCE) endif() # Put our binary directly in the build folder, so 'cd build && ./llama-elana' works. # (Upstream sets CMAKE_RUNTIME_OUTPUT_DIRECTORY to <build>/bin; libraries stay there.) set(ELANA_OUT_DIR "${CMAKE_CURRENT_BINARY_DIR}") # ----------------------------------------------------------------------------- # Pull in the upstream tree (one level up) without building any of it. # The binary dir is placed under ours so the two build trees never collide. # ----------------------------------------------------------------------------- add_subdirectory("${LLAMA_ROOT}" "${CMAKE_CURRENT_BINARY_DIR}/llama" EXCLUDE_FROM_ALL) # ----------------------------------------------------------------------------- # server-context: compiled from the ORIGINAL upstream sources, listed by reading # upstream's own CMakeLists so the set can never drift out of date. # ----------------------------------------------------------------------------- set(_sc_cmake "${LLAMA_ROOT}/tools/server/CMakeLists.txt") file(READ "${_sc_cmake}" _sc_text) # Grab the source list of the first add_library(... STATIC ...) block. string(REGEX MATCH "add_library\\(\\$\\{TARGET\\}[^\n]*\n?[^\n]*STATIC([^)]*)\\)" _sc_block "${_sc_text}") string(REGEX MATCHALL "[a-zA-Z0-9_.-]+\\.cpp" _sc_names "${_sc_block}") if (NOT _sc_names) message(FATAL_ERROR "Could not parse the server-context source list out of ${_sc_cmake}.\n" "Upstream changed the layout of tools/server/CMakeLists.txt; update the " "regex below or list the sources explicitly.") endif() set(ELANA_SERVER_CONTEXT_SRCS "") foreach(_name IN LISTS _sc_names) set(_path "${LLAMA_ROOT}/tools/server/${_name}") if (NOT EXISTS "${_path}") message(FATAL_ERROR "server-context source listed by upstream but missing: ${_path}") endif() list(APPEND ELANA_SERVER_CONTEXT_SRCS "${_path}") endforeach() list(LENGTH ELANA_SERVER_CONTEXT_SRCS _sc_count) message(STATUS "llama-elana: compiling ${_sc_count} server-context sources from upstream") # ----------------------------------------------------------------------------- # Our target. # ----------------------------------------------------------------------------- add_executable(llama-elana llama_elana_host.cpp ${ELANA_SERVER_CONTEXT_SRCS}) # Threads::Threads is created by find_package() inside the llama.cpp subdirectory, # where imported targets are directory-scoped - we need our own call at this scope. find_package(Threads REQUIRED) target_compile_features(llama-elana PRIVATE cxx_std_17) # server-context.h / server-task.h / server-common.h live in upstream tools/server; # mtmd.h lives in upstream tools/mtmd. Everything else arrives transitively through # the llama-common / mtmd / llama targets (their PUBLIC include dirs). # # CMAKE_CURRENT_BINARY_DIR is first on purpose: build.sh writes llama_elana_version.h there # (NOT via configure_file, which only runs at configure time and would go stale on a source # change). The source includes it through __has_include, so a build that bypassed build.sh # still compiles and reports version 0 / hash unknown instead of failing. target_include_directories(llama-elana PRIVATE "${CMAKE_CURRENT_BINARY_DIR}" "${CMAKE_CURRENT_SOURCE_DIR}" "${LLAMA_ROOT}/tools/server" "${LLAMA_ROOT}/tools/mtmd" "${LLAMA_ROOT}" ) # NOTE: no 'server-context' in this list on purpose - we compile those upstream # sources directly into this executable (see above), so there is no such target # to link. Everything else is a real target from the parent tree. target_link_libraries(llama-elana PRIVATE mtmd llama-common llama Threads::Threads ) if (WIN32) target_link_libraries(llama-elana PRIVATE ws2_32) endif() set_target_properties(llama-elana PROPERTIES RUNTIME_OUTPUT_DIRECTORY "${ELANA_OUT_DIR}" # Run straight out of the build tree: libraries land in build/llama/bin. # $ORIGIN-relative ONLY, so the built binary keeps working if the whole build # folder is moved or copied - an absolute BUILD_RPATH here is what made a # copied build/ resolve libraries out of the tree it was originally built in. BUILD_RPATH "$ORIGIN:$ORIGIN/llama/bin:$ORIGIN/bin" INSTALL_RPATH "$ORIGIN:$ORIGIN/bin" ) message(STATUS "llama-elana: executable -> ${ELANA_OUT_DIR}/llama-elana")

Bulls time to **BREAK OUT THE RED PANTIES** https://preview.redd.it/n97islo8ylth1.jpeg?width=686&format=pjpg&auto=webp&s=8dbc0efa77444817ac954d91fb9a400398179c61

Second post ko na ito on the G C A S H ipo (here’s the first one if may pake ka hahahaha: https://www.reddit.com/r/phinvest/s/zgX4KVn9Cr) MAHABA NA NAMAN. Sinubukan ko na paikliin kay Chatgpt Gemini Claude Grok. Pero tinatamad na ako so idea dump na lang tas bahala na kung babasahin ng iba. mahaba pa rin siya hahahaha Dati sinabi ko better 6-7 vs yung 10 ceiling. Eh ayun na nga at 6.6 ang offer. 🤣 But honestly thinking about it, salo na lang ako somewhere 4-5, I can be wrong, but parang deins pa rin pala ako at 6.6. I think the more interesting way to look at GCash now is not simply “expensive vs cheap.” It’s how much of a premium am I willing to pay for growth? At 6.6, GCash P/E is roughly 20x annualized H1 2026 earnings. So kung nasa 5, it’s roughly 15.5x. Kung 4, roughly 12.4x. These are based on annualizing H1 2026 net income, so obviously hindi ito exact FY2026 P/E. Just a way to compare the valuation at different entry prices. I’m comparing GCash to big Philippine banks that are trading at much lower multiple: roughly 7x-ish earnings for BDO/BPI while also paying dividends consistently at around 4–5%+ depending on the bank and share price. GCash doesn’t have an established dividend yield yet. And that’s not automatically a negative. In fact, if Mynt can reinvest the money and generate very high returns, I’d rather they do that than pay me a dividend. But it does change the equation. If I buy the other Ayala company BPI at a much lower P/E and get a \~5% dividend, I’m getting paid while I wait. If I buy GCash at 20x earnings with no established dividend, I’m paying upfront for something-somewhere-somehow-potentially-in the future growth. So the growth has to show up. Hence my hesitation even at a lowered offer of 6.6. H1 2026 net income was up only \~7.3%. Revenue was up \~10.4%. EBITDA actually declined \~4%. Meanwhile, payments grew \~23% and monthly active users grew \~11%. Yes, GCash is clearly still growing. I’m not arguing otherwise. The only question I’m asking is: **How much of that growth is actually translating into shareholder earnings?** The payment numbers are particularly interesting. Payment volume is growing strongly, but payment take rate reportedly fell from around 0.32% to 0.25%. This is consistent with my original concern about payments becoming more of a utility business. QRPh interoperability, lower transfer fees (actually mostly zero na nga since my last post), payment processors, etc. are great for consumers and merchants. But they can also make it harder for GCash to capture the same economics from every peso flowing through the platform. GCash GTV looks very impressive. But **GTV × take rate = economics.** You can have massive transaction growth while monetization gets harder. Which now brings me back to lending. This is probably the most important part of the GCash story that I’m watching now. GCash has a huge amount of data and a massive user base, even claiming 40M active users. You would think that data advantage really translates into better underwriting, lower losses and better risk-adjusted returns. Their lending could potentially become a very powerful growth engine. But data doesn’t magically eliminate credit risk. GCash’s reported NPL was around 4.9% in June, versus roughly 3.35% for the banking system. That’s not an apples-to-apples comparison because the loan products and borrowers are different, but it’s still something I want to watch PLUS the type of lending products/ offers matters. Traditional banks have mortgages, auto loans, secured business loans, corporate loans, etc. GCash’s lending opportunity is in smaller, unsecured consumer/MSME credit — potentially a huge, untapped market, but also potentially more sensitive to borrower stress. The question isn’t: “Why can’t GCash score borrowers better if they have all that data?” But: “How much does GCash’s data advantage actually translate into better credit performance and risk-adjusted returns?” If the answer is “a lot,” then I could become much more bullish to their CreditTech plans as it seems like that’s their next growth engine, the next 10x maybe in the next 10 years? Which now brings me back to valuation. 20x for a great company doesn’t mean it’s a great entry price. At that pricing, I’m still giving GCash a premium versus banks. I’m just not giving it *as much* of a premium. And I think that’s the key point. I’m not questioning whether GCash will grow. I’m asking myself how much of that growth I’m willing to pay for upfront. Could I change my mind? Absolutely. If earnings growth accelerates, NPLs continue improving, and the data advantage clearly translates into better credit economics, then I’m happy to pay a higher multiple. I’d rather change my mind because the numbers changed than defend an old Reddit post forever. 😂 PEACE (also may trolls last time na acct created in the past 5 days hahaha so as an experiment tignan din natin dito). NOT FINANCIAL ADVICE. RESEARCH. USE YOUR BRAIN. USE AI TOOLS. FIGURE IT OUT. TRADE AT YOUR OWN RISK.

Omg the stock market is gonna crash SELL SELL SELL EVERYONE. FREAK RHW FUCK OUT!!! JUST FREAKOUT!!! 😂😂😂😂

# WHY GOING OUT IS SO COSTLY. THE FCK # DID I JUST REALLY SPEND $276 FOR A SMALL BREAKFAST (FOR 2), A LUNCH, COFFEE AND ICECREAM???????? WTF

If anyone want to gain confidence, sharing one of my MF portfolio value. This is when everyone is complaining about Indian equity markets. Markets reward those who stay here for long term, and punishes those who are here for short term. Long-term doesn't mean LTCG type taxed terminology Long term, it means minimum of 10 years, ofcourse forgot to tell that this portfolio was created in 08/2019, slowly added through lump sum investment. I believe waiting patiently would reward much better than doing IN OUT transactions. https://preview.redd.it/fqc3zwe5nhth1.jpeg?width=1016&format=pjpg&auto=webp&s=bdfef378ee536c2fed21aea8bacfff6bd7aa33d3