#0504
Unidentified Russian Navy ship UCAC2, sent a message to the Russian Navy Northern Fleet Naval Base in Severodvinsk, RJD99 on 4619.5 kHz CW 19NOV2026 at 0504 UTC

Position 67 05N 32 21E

RJD99 answered on 6259.5 kHz

The position is at the Vitino oil terminal anchorage
November 19, 2026 at 5:23 AM
Unidentified Russian Navy ship UCAC2, sent a message to the Russian Navy Northern Fleet Naval Base in Severodvinsk, RJD99 on 4619.5 kHz CW 18NOV2026 at 0504 UTC

Position 66 54N 32 50E

RJD99 answered on 6259.5 kHz

Probably at the usual anchorage
November 18, 2026 at 5:14 AM
ICAO: #A6652B
Owner: #PSAAIRLINES
Flt: #JIA5588 #N511AE #CRJ7
Time: 2026-11-20 13:28:08 CST
Min Alt: 21975 ft
Min Dist: 102.3 nm (151deg SSE)
Squawk: #0504
#adsb #planefence by kx1t sdr-e adsbexchange flightaware faa
November 20, 2026 at 7:39 PM
Gold set for worst week in eight months as firm dollar, Fed hike bets weigh
Gold prices slipped on Friday **and were headed for their worst week in eight months, as a resilient US dollar and expectations of a Federal Reserve interest-rate hike in December weighed on bullion.** Spot gold fell 2.7% to $3,525.25 per ounce by 0504 GMT, after hitting its lowest level since September 2025 earlier in the session. Bullion was down about 9.2% so far this week, its sharpest weekly decline since the week ending March 20. US gold futures for December delivery slid 4.3% to $3,526.00. “There seems to be a bit of forced liquidation going on across the market in general, with expectations of imminent US rate hikes and inflation that could be persistent, leading to high yields and a higher US dollar as a result, pressuring gold,” said Kyle Rodda, senior financial market analyst. Asian shares slid on Friday, putting them on track for their worst week since 2020, as Anthropic’s debut failed to restore investor faith in the AI sector. The dollar held near a 19-month high on Friday, extending its recent rally and making greenback-priced bullion more expensive for holders of other currencies. Federal Reserve Bank of Philadelphia President Anna Paulson said on Thursday the Fed will need to raise interest rates again because inflation is too high, while arguing that shared understanding matters more than explicit guidance on the rate outlook. Markets see a 96.8% chance of a 25-basis-point US rate hike in December, while the probability of a larger 50-basis-point move is priced at 3.2%, according to CME’s FedWatch tool. Higher interest rates increase the opportunity cost of holding non-yielding bullion, reducing its appeal to investors. Elsewhere, Swiss gold exports fell to 109.7 metric tons in October, down 34% from the prior month as deliveries to Britain were lower, Swiss customs data showed on Thursday. Oil prices edge higher as Houthi attacks on Riyadh raise supply concerns Among other metals, spot silver fell 3.5% to $41.25 per ounce, platinum dropped 3.6% to $1,299.25, and palladium slid 3.3% to $879.47. All three metals were headed for weekly losses.
www.brecorder.com
November 20, 2026 at 8:04 AM
Before PJ Harvey on the Friday!
November 13, 2026 at 5:27 PM
#0504 - #0505 Patrat & Watchog #twiart #pokemonfanart #pokemon #pokedex

Please consider supporting me if you like my work:
🅿️ patreon.com/twilidramon (see more pokemon - and mega pokemon - there!)
☕ ko-fi.com/twilidramon (tip or commission me!!)
My Gallery >> deviantart.com/twilidramonart
November 11, 2026 at 2:17 PM
#PlaneAlert ICAO: #424771
Owner: #JETAVIATIONFLIGHTSERVICES
Flt: #JAS39 #VPCUA #GLF5
Time: 2026-11-12 23:12:08 CET
Min Alt: 45000 ft
Squawk: #0504
#aircraft over #heerlen - #adsb #planefence by kx1t - sdr-e airplanes flightaware
November 12, 2026 at 10:12 PM
Unidentified Russian Navy ship RBE94, sent a message to the Russian Navy Northern Fleet Naval Base in Severodvinsk, RJD99 on 6906.5 kHz CW 11NOV2026 at 0504 UTC

Position 66 38N 34 24E in Sosnovaya Bay

RBE94 first called on 4537.5 kHz but was directed to 6906.5 by RJD99
RJD99 answered on 6007.5 kHz
November 11, 2026 at 5:27 AM
November 11, 2026 at 8:24 PM
Job ID: REF 2026-0504
Extract: Postdoctoral position at Chalmers to study how food composition and fermentation influence gut microbial interactions and metabolism for next-generation food design.
November 11, 2026 at 8:44 AM
November 10, 2026 at 9:59 AM
#0504 Patrat #twiart #pokemonfanart #pokemon #pokedex

Please consider supporting me if you like my work:
🅿️ patreon.com/twilidramon (see more pokemon - and mega pokemon - there!)
☕ ko-fi.com/twilidramon (tip or commission me!!)
My Gallery >> deviantart.com/twilidramonart
November 9, 2026 at 2:58 PM
ノクチルの誕生日で素数なのは雛菜だけ
透  0504(2³×3²×7)
円香 1027(13×79)
雛菜 0317
小糸 1111(11×101)

そして小糸だけが7(ひ「なな」)を持っていない

どういうことだろうか…😱
(ほんまになに?)
November 10, 2026 at 5:26 AM
BTW, it's cool to do both - TFI Local Link Tipperary edition 🚌✨

With 5 regular routes and 45+ door-to-door routes across Tipperary, we're here to help you get to wherever you need to be.

📞 0504 39310
🌐 www.locallinktipperary.ie
November 12, 2026 at 10:49 AM
Our simple steps (with complimentary Paint drawings 🎨 ) on how to find out whether there's a Local Link bus in Tipperary that can pick you up and drop you off at your home! 🏡 🚌
November 9, 2026 at 10:13 AM
0504/1001 — Attention, Subconscious Tasking, and Value Creation does not finish the making

The generation starts where the match-span ends. The surface is “Attention, Subconscious Tasking, and Value Creation”. An empty room can already be an agreement. (1/3)
November 8, 2026 at 6:50 PM
ICAO: #A2CF34
Owner: #ENVOYAIR
Flt: #ENY3592 #N280NN #E75L
Time: 2026-11-05 20:16:09 CST
Min Alt: 28000 ft
Min Dist: 31.94 nm (-99deg W)
Squawk: #0504
#adsb #planefence by kx1t sdr-e adsbexchange flightaware faa
November 6, 2026 at 2:39 AM
9 757 7858 61 48 17 647 95 2 Mike Echo 23 363 5637 0 33 062 99 1 5 92 90 156 6 3 380 9998 5 411 191 9 816 091 Alfa Whiskey Alfa Yankee 67 567 1 30 8 97 342 0504 8 71 947 8324 30 693 961 63 042 6773 5 7 82 301 0121 7 030 5583 05 41 61 066 594 702 775 4 85 266 6 525 281 9 14 914 9413 9 9 01 15 314 6 5
November 6, 2026 at 9:46 PM
ICAO: #3C1BAE
Owner: #EUROPEANAIRTRANSPORT
Flt: #BCS6756 #DAZMN #A306
Time: 2026-11-05 11:18:36 CET
Min Alt: 9732 m
Min Dist: 0.22 km (-65deg WNW)
Squawk: #0504
#adsb #planefence by kx1t sdr-e airplanes flightaware
November 5, 2026 at 10:24 AM
Travel to Clonmel town centre from your front door with the TFI Local Link T53 service! 🚌🏠

Service details:
📆 Every Thursday
⏰️ Service commences at 8am approx.
🚌 Returns from Clonmel at 12:30pm approx.
☕ Perfect for meeting friends, shopping and staying […]

[Original post on mastodon.ie]
November 5, 2026 at 12:06 PM
Solana Shred Recovery: When Valid Shreds Form an Invalid Erasure Batch
_Originally published on xroot.dev._ A Solana block reaches validators as shreds, in batches of 32 data shreds and 32 coding shreds tied together by one Merkle root that the leader signs. Every shred in a batch can carry a valid signature and a valid Merkle proof while the batch itself is wrong, because nothing in the signature says the coding shreds are the parity of the data. SIMD-0504 says the rules for a batch apply to rebuilt shreds as much as to received ones, and between 24 October and 5 November Agave rebuilt its recovery path to enforce that: every validator now rebuilds every batch, so a batch like this fails everywhere. We modelled the old and new paths with the Reed–Solomon library Agave uses and ran four kinds of malformed batch past simulated validators losing packets. Under the old code, what a validator ended up doing depended on which shreds it happened to receive. Under the new code, every validator that collects 32 shreds rejects the batch: none of 800,000 rebuilds of a malformed batch passed. ## How an erasure batch is built The leader cuts its block into data shreds and, for every 32 of them, computes 32 coding shreds with a Reed–Solomon code. Any 32 of the 64 are enough to rebuild the other 32, so a validator can lose half of a batch to the network and still have the block. Then the leader hashes all 64 shreds into a Merkle tree, signs the root and attaches to each shred its path to that root. A validator checks each shred on arrival: the signature over the root, and the path from the shred to the root. **Shreds per batch** — 32 data + 32 coding **Needed to rebuild the batch** — any 32 **Payload: data · coding shred** — 1,203 · 1,228 bytes **Erasure-coded part of each** — 987 bytes **Merkle tree** — 64 leaves, 6 levels ## What the signature does not cover The Merkle root commits to the bytes of each of the 64 shreds. It says nothing about how they relate. A leader can compute its coding shreds from different data, or change one byte of a shred after encoding, then build the tree and sign. Each shred still verifies on its own. The batch is not a Reed–Solomon codeword: rebuilding it from different subsets of shreds gives different answers. Until 29 October, Agave ran Reed–Solomon only when data shreds were missing and at least 32 shreds of the batch were present, tried again after every new insert of shreds, and logged a failed attempt at info level before moving on. The Merkle check made sure a rebuilt shred was byte-for-byte what the leader had signed, so a bad batch could never smuggle in different block data. But whether a validator noticed anything depended on which shreds it held. In our simulation of 2,000 validators per row, adding one shred per insert, each row counts the validators that completed the batch from data shreds alone · recovered without noticing the bad shred · were left waiting for repair: **First coding shred corrupted, 1% loss** — 1,492 · 0 · 508 **First coding shred corrupted, 5% loss** — 379 · 0 · 1,621 **Last coding shred corrupted, 1% loss** — 62 · 1,934 · 4 **Last coding shred corrupted, 5% loss** — 29 · 1,895 · 76 Those in the first group never looked at a coding shred. With the first coding shred corrupted, every recovery that used it failed, about 31 failed attempts per validator even with no loss, and at 5% loss four validators in five could not complete the batch from Turbine. Repair fixes that, because it hands out the shreds the leader signed, but it takes longer. With the last coding shred corrupted, most recoveries never touched it and quietly succeeded. A corrupted data shred, or coding shreds computed from other data, behaved like the first case. Nothing in any row was rejected. ## SIMD-0504: the batch is the unit of validity SIMD-0504, written by Philip Taffet of Firedancer, replaces the shred rules each client inferred from Agave’s code with a written list. Sixteen checks apply to each shred: index ranges, the fixed 32:32 layout, a Merkle tree of exactly six levels, flag and size rules. A shred that fails them is dropped. Eight checks apply to the batch as a whole: one slot, one shred version, one chained Merkle root, one parent across the data shreds, padding only at the end. A block containing a batch that fails them is invalid. Under TowerBFT a validator must not vote for it, and under Alpenglow it must vote skip. None of the sixteen or eight checks says the coding shreds must be the parity of the data. That follows from the proposal’s note on recovery: the batch checks apply to received and rebuilt shreds alike, so a validator that received all 32 data shreds must still check the coding shreds. The proposal says why: to eliminate any divergence based on whether a validator received or recovered a shred. A rule that only the validators who happened to need recovery could check would split the cluster the first time a leader broke it. Agave enforces the note by rebuilding every batch, and a batch whose coding shreds aren’t the parity of its data cannot be rebuilt to the root the leader signed. ## “Always recover”: how Agave checks every batch Agave landed the change in a series of pull requests: #16194 wired the rebuild into blockstore on 29 October, #16378 added the feature gate and enforcement a day later, and #16639 stopped retrying a batch that cannot be rebuilt once SIMD-0504 is active. In the code at the time of writing, a batch is rebuilt exactly once, in the insert that first brings it to 32 shreds, whether or not any data shred is missing: received exactly 32: reconstruct the other 32 shards received more than 32: reconstruct missing data from 32 of them, re-encode all 32 coding shards, compare with the coding shards received then: rebuild the Merkle tree from all 64 leaves, compare with the signed root fail either check: with SIMD-0504 active, mark the slot dead (unless it was already full before this insert) The gate is `stricter_shred_validation`, key `s5o4YoA9zUrw9j4v335ncdG5PpznDBsrgM6CvUGrasA`. On 6 November at 03:18 UTC its feature account did not exist on mainnet, testnet or devnet. Until it is activated, Agave runs every check and reports failures to its metrics, but rejects nothing it did not reject before. ## Same verdict, whatever arrived Our model follows that code with the same library, version and features (reed-solomon-erasure 6.0.0 with `simd-accel`), 987-byte shards and Agave’s Merkle construction. We built four malformed batches, the first or last coding shred flipped by one bit after encoding, one data shred flipped, and all coding shreds computed from different data, and rebuilt each from 200,000 random subsets of every size from 32 to 64 shreds: **Honest batch, 200,000 subsets** — all pass **Malformed batches, 800,000 subsets** — 0 pass **…failed as Merkle mismatch** — 629,095 **…failed as wrong parity** — 170,905 The reason is simple once written down. The rebuild produces one Reed–Solomon codeword from the shreds it used. For the batch to pass, that codeword must equal the signed shreds at every position the validator did not receive (or the Merkle root differs) and at every coding position it did receive (or the parity check fails). The positions it used to rebuild match by construction. So passing requires the codeword to match all 64 signed shreds, which only happens if the batch was a valid codeword to begin with. In the packet-loss simulation every validator that reached 32 shreds flagged every malformed batch, at every loss rate from 0 to 45%, and passed the honest one. That held with one shred per insert, and again with inserts of a random 1 to 16 shreds, where about half the failures of the last-coding-shred batch came from the parity comparison rather than the Merkle root. The only validators without a verdict were those that never collected 32 shreds through Turbine, 16 to 19% of them at 45% loss and none at 20% or less; they run the same check when repair brings the batch to 32. ## What rebuilding every batch costs Less than it sounds. The old code already rebuilt a batch whenever a data shred was missing when it reached 32 shreds, and that is nearly always. The leader sends a batch’s data and coding shreds together, and Turbine routes each shred down its own tree. If they arrive in random order, the first 32 are exactly the 32 data shreds with probability 1 in C(64, 32), about 5.5 × 10⁻¹⁹, which fits the pull request’s estimate that the old code skipped recovery less than once in a trillion batches. What is new is re-encoding the received coding shreds when an insert pushes a batch past 32 at once, and rebuilding batches made only of data shreds. Timed on our model, per batch: **Old recovery, 16 data + 16 coding** — 299 µs **New rebuild, same 32 shreds** — 299 µs **New rebuild, 24 data + 16 coding** — 325 µs **New rebuild, 32 data and no coding** — 299 µs **New rebuild, all 64 received** — 305 µs Most of that is hashing the 64 leaves of the Merkle tree, about 214 µs here, which both versions do; encoding 32 coding shreds takes about 83 µs. For the same 32 shreds the new path costs exactly what the old one did, and re-encoding the received coding shreds adds about 9% when more than 32 are present. These are timings of our model on an Apple M1 Pro; absolute numbers depend on the hardware, SHA-256 speed above all. ## Two Turbine changes around it **Rebuilt coding shreds are now retransmitted.** A validator forwards rebuilt shreds to its children in Turbine, so one dropped packet upstream doesn’t starve everyone below. When an insert brings only data shreds, the rebuild produces coding shreds the validator never received, and the first version of always-recover, keeping Agave’s old output, threw them away. #16622 forwards them as well, which its description notes Firedancer already did. **Leaders no longer rebroadcast.** When a leader’s own slot had not been seen by enough stake, Agave’s replay stage asked the broadcast stage to send every data and coding shred of that slot again, after 5 seconds and then at doubling intervals up to 320 seconds. On 5 November #16595 removed Tower consensus from Agave’s replay stage as part of its Alpenglow cleanup, and the request went with it. Hours later #16713 deleted the broadcast worker that served those requests. The issue behind it had called the mechanism redundant if repair works. A validator missing shreds now has two ways to get them: rebuild them from the batch, or ask a peer through repair. ## What this does not show We ran a model of Agave’s rebuild, not Agave: shred headers, signatures, the per-shred checks and the batch header checks are not in it, and a malformed batch here differs from an honest one only in its erasure coding. Arrival order and loss are random and independent, which real Turbine is not, and inserts are one shred or a random 1 to 16. We had no cluster, so nothing here was measured on a network; the timings are from an Apple M1 Pro, not validator hardware. Firedancer’s implementation of the same rules was out of scope. ## Shred Recovery: Questions People Actually Ask ### What is a Solana erasure batch? A group of 64 shreds: 32 data shreds carrying the block and 32 coding shreds that are their Reed–Solomon parity, so any 32 of the 64 rebuild the rest. All 64 are leaves of one Merkle tree, and the leader signs its root. Agave and SIMD-0504 also call it an FEC set. ### What does SIMD-0504 change about shred validation? It replaces the checks validators inherited from Agave’s code with a written list: sixteen checks on each shred and eight on each erasure batch as a whole. A batch that fails them makes the block invalid: under TowerBFT a validator must not vote for it, under Alpenglow it must vote skip. The checks apply whether a shred was received or rebuilt, so a validator has to check the coding shreds even when all 32 data shreds arrived. ### What is “always recover” in Agave? Agave rebuilds every erasure batch once, in the batch of incoming shreds that first brings it to 32 shreds, even when no data shred is missing. It re-encodes the coding shreds from the data, compares them with the coding shreds it received, and rebuilds the Merkle tree from all 64 leaves to compare with the signed root. With the SIMD-0504 feature active, a failure marks the slot dead unless it was already full. ### Is SIMD-0504 active on Solana mainnet? No. Agave’s gate, stricter_shred_validation, was merged on 30 October 2026 and had no feature account on mainnet, testnet or devnet on 6 November. Until it is activated, Agave runs the checks and reports failures to metrics without rejecting anything new. ### Does a Solana leader still rebroadcast slots that did not propagate? Not in Agave’s main branch. The replay code that asked a leader to resend an unpropagated slot was removed on 5 November 2026 along with Tower consensus in replay, and the broadcast worker that served those requests was deleted the same day. Missing shreds are recovered from erasure coding or fetched through repair. ## The one-line version A leader can sign an erasure batch whose shreds each verify but whose coding shreds aren’t the parity of its data; SIMD-0504 makes that batch invalid, and Agave now rebuilds every batch once it has 32 shreds, so every validator rejects it the same way, whichever shreds reached it. Sources: SIMD-0504 at commit `33c75cff`; Agave #16194, #16378, #16639, #16622, #16595 and #16713, read at commit `9eacc06d`; the old recovery path at `dd6f564f`. The model, simulation and timings are our own.
dev.to
November 6, 2026 at 4:35 AM
GDOT-0504: I-575 N before BigShantyRd MM 1.7 (Cobb)
🕒 2:03 PM - 2:05 PM ET (4x speed)
🌡️ 69°F | Overcast

📍: 34.024464,-84.559559
November 3, 2026 at 7:05 PM
ICAO: #4CAA5C
Owner: #RYANAIR
Flt: #RYR61FH #EIEVX #B738
Time: 2026-11-03 16:41:38 CET
Min Alt: 11880 m
Min Dist: 0.7 km (-25deg NNW)
Squawk: #0504
#adsb #planefence by kx1t sdr-e airplanes flightaware
November 3, 2026 at 3:47 PM
Within your illusion, the lesson is love. This lesson is begun when the conscious seeker becomes aware that it is the lesson. – L/Leema

https://www.llresearch.org/channeling/1986/0504
May 4, 1986 - Sunday meditation - L/L Research
L/Leema: I am L/Leema. I greet you in the love and in the light of the one infinite Creator. It is a privilege to have been called to your group this evening, for although none in the circle but the instrument had a question, this instrumen...
www.llresearch.org
November 3, 2026 at 2:00 PM