Well, let's wrap up what I've found at the very least interesting in the last couple weeks for pirates and purists alike! This one is very small, not much happening lately!
Sony:
As maybe you've seen, there's no better indication that 'if they don't let you buy it, then pirate it' than Sony delists Ghost of Tsushima PC from various Steam regions, much like Helldivers 2 saw.
​

Following Sony's decision last week to delist Helldivers 2 in 170 regions worldwide on Steam, it seems this will be the firm's PC stance moving forward, and it has since done the same for the imminent PC release of Ghost of Tsushima. More regions have been added to the list, taking the total number of territories affected to 180, which is now consistent across both titles.
Previously, Sony has said that Ghost of Tsushima's single player offering would be unaffected by this additional requirement. The game's Steam Page still states that a PSN account is required to play the Legends multiplayer mode, but it was delisted anyway. Due to the open nature of Valve's platform, these changes are pretty visible, and including Sucker Punch's primarily single player open world epic in this blanket ban comes as a legitimate surprise.

SteamDB's post here shows the refund.
This is bullshit. The good news? Sony do not use Denuvo for their PC games, so it will be available as soon as possible to be pirated.
​
​
Rockstar:
By all accounts, it looks like Rockstar's Red Dead Redemption will be releasing on PC - in line with their usual tactics of releasing on a console platform and leaving PC for last, at least it will (probably) be coming to PC.
​
​
Denuvo:
A Denuvo 'outage' made a completely single-player game Persona 5 unplayble - amusingly Denuvo claim that "there was no outage related to its servers at this time"

• The Denuvo server outage rendered the PC version of Persona 5 Royal unplayable on May 2nd
• A partial workaround allowed Steam users to access the game without online functionality, but most didn't use it, with the game's concurrent player count consequently plummeting from 16,600 to just over 600
• The outage lasted for hours, angering fans

The thing we can take away from this is Denuvo sucks, and it's just better to play the damn thing via Yuzu or Ryujinx.
​
Related, we now see that it is confirmed that Homeworld 3 will release with Denuvo. The only good news is that Gearbox is one of the few publishers who remove Denuvo. So...just wait for this one.
​
​
Just...interesting and useful:
This video guide via YouTuber 'MonroeWorld' shows you how to SSHFS - mount your Steam Deck as a Windows drive.

"Access your Deck's storage using whatever file manager or tools you want ON AND FROM Windows. In a few minutes, you can copy roms, access compatdata, backup/restore save files and more without ever leaving the comfort of Windows. In about ten minutes, you will have your common Steam Deck locations mounted as drive letters in Windows - accessing them just like any other Windows drive" 

Here is a github link for a GUI for the sshfs manager
Even better u/ReplacementFun53 has a full written guide on how to do so here!!! - 100% what you should be checking out, it's perfect!
​
​
FitGirl:
Has a new section on her page (remember, always use the official site, not one of the dodgy rip-offs) Updates now have their own sub-section on her page for games which have, you guessed it, been recently updated - called Updates Digest. Super handy! I love seeing these kind of incremental UX updates, yay!
​
​
Hydra Launcher:
Hydra is an open-source launcher released in the last few weeks by the Brazilian community. Being able to download and launch games from fitgirl and dodi - it has/is a torrent client, automatically applies metadata for games, emulators and roms; seems to hope to be an all-in-one piracy portal. Personally, I prefer to manually add games from trusted links myself. But I'm paranoid. At least it is interesting.
​

Hydra is a free open game launcher focused on being 100% safe, self-sufficient, ad-free, without registration, without subscription and without waiting times.
Hydra combines games from platforms like Steam and Epic Games with trackers from repackers/crackers known and trusted by the pirate gaming community (such as Fitgirl, Dodi and KaOsKrew.
The game downloads are done directly through the platform, as we have our own private torrent protocol.
Hydra currently has the capability to search among a list of more than 13,000 repacks posted in secure places on the internet, but not limited to that. being self-sufficient, Hydra can navigate the trackers not only looking for updates of games that are already registered but also for games that have just been released.

​
​
Lastly the AMA with Dodi:
Well and truly locked in for the 16th. I have a post pinned at the top of PiratedGames, and have just reached out to the mods of Piracy about posting in their sub letting the users know what is happening. I also just posted in his discord server (at his behest). The only thing yet to be determined will be the exact time, for Americans it may be the 15th (your time), but...time-zones fry my brain so I don't know. Really excited about having him come by, the repacker scene is fascinating to me, so I can't wait to hear what he says.

• It will be the typical method: top level questions will be more likely to get an answer.
• Comment a question, he (may) comment a reply.
• The usual sub-reddit rules I have apply more than ever, but the most important is to be kind.
• I have set a custom user flair for his name here, but it should be obvious who is who: u/DODI-Releases is his account.
• I have nothing for this final dot-point.

​
Guides?
I'm working on one lil guide since its been awhile since my last. Most probably will post after the aforementioned AMA.
​
Lastly?
Thanks to all of you, we're nearing 17k members here and you're all super lovely. This is such a strange sub-reddit because everyone is so damned nice. I just wanted to thank you all for being here, it makes it so nice.
If you wanted to show off your Deck's home screen - then this post a couple days ago is where you can do it!
​
​
^{Thanks, all <3}
​
​

On August 18, 2015 the Boston Red Sox hired the late General Manager of the Detroit Tigers, Dave Dombrowski, to run the team, replacing Ben Cherrington. The development focused Cherrington had failed to follow up the Red Sox miracle 2013 season with even winning records in the two years since, though the farm system ranked among the very best in baseball and a wave of prospects had just hit the majors (among them, Xander Bogaerts, Jackie Bradley Jr., Mookie Betts, and Blake Swihart). Thus, the swapping of Cherington for Dombrowski was rightly interpreted as the Red Sox moving to a more assertive phase, to win now even at the expense of the player development system.
Ironically Dombrowski had been fired by the Tigers because of his belief that the organization’s competitive window had closed and that the team needed to rebuild; the Tigers gave the job to his former assistant who got one more winning season out of their aging core before the inevitabilities became insurmountable. By that time the Red Sox were in the midst of their second straight division crown of three, which climaxed with the single greatest season in franchise history. This is how Dombrowski built that team, as well as the fiscal panic that cost the Red Sox the greatest all around player in franchise history following it:
~2015~
November 13, 2015: Traded Logan Allen, Carlos Asuaje, Javy Guerra and Manuel Margot to the San Diego Padres. Received Craig Kimbrel.
The first major transaction of the Dave Dombrowski era set the pace for the next four years; trading four prospects for a relief pitcher constitutes the classic win-now move. In this case the Red Sox won the deal in both the long and short terms, as only Manuel Margot developed in regular at the major league level, and that at a position where the Red Sox were not in need (center field). Meanwhile Craig Kimbrel made the all-star team in each of his three seasons in Boston, the second of which was one of the greatest relief performances in the game’s history.
December 4, 2015: Signed David Price as a free agent, 217 million dollars over seven years.
At once the most maligned and most underrated move of the Dombrowski era as well as being the biggest, the David Price signing saw the Red Sox for the first time handout a nine figure contract to a free agent pitcher. This was all the more dramatic as they had alienated and traded away their own homegrown southpaw ace (Jon Lester) less than eighteen months before. This was also the first time with the Red Sox that Dave Dombrowski acquired a player he was he previously familiar with, perhaps slightly overpaying for that familiarity. Did we mention that this was largest contract ever given to a pitcher at time, too?
Price had a solid first season in Boston, leading the league in innings pitched with 230 and striking out nearly a man per inning. Nonetheless the first three years of his tenure were marked with mutual hostility towards the ever-ravenous Boston sports media, only alleviated after his fantastic 2018 postseason run. Aging and injuries limited both the quantity and quality of his performance in 2017 and 2019; this trend as well as his 31 million annum salary contributed to owner John Henry’s decision to offload Price even at the cost of Mookie Betts. If only for that last reason alone the David Price signing is one the Red Sox would likely not repeat in hindsight.
December 7, 2015: Traded Jonathan Aro and Wade Miley to the Seattle Mariners. Received Roenis Elías and Carson Smith.
The first of many times Dombrowski would be burned in pursuit of bullpen arms, this deal with Seattle comes down to Wade Miley for Carson Smith. Miley had been signed as a reclamation project by Cherrington before 2015 in the hopes that Miley could serve as a solid mid-rotation option, which he more or less fulfilled with just short of 200 league average innings. Smith on the other hand was coming off his first full season in the majors where he gave the Mariners seventy brilliant innings of high leverage relief pitching (2.31 ERA, 11.8 K/9, and only two home runs allowed).
In a twist of fate, this trade hurt both teams as Smith immediately got injured and only pitched 24 innings in the rest of his career while Miley bombed in Seattle en route to a midseason jettisoning. Yet he rebounded with Baltimore in 2017 and remains an effective if oft-injured starting pitcher to this day, currently with the Milwaukee Brewers.
~2016~
June 10, 2016: Drafted Bobby Dalbec in the 4th round of the 2016 amateur draft.
The once and future Red Sox, Quad A superstar Bobby Dalbec!
July 7, 2016: Traded Wendell Rijo and Aaron Wilkerson to the Milwaukee Brewers. Received Aaron Hill and cash.
With Pablo Sandoval well into his career of eating his way out of Boston, the Red Sox carried a gaping hole at third base from August 2012 to July 2017. One of the short term attempts at a fix featured the acquisition of infielder Aaron Hill, hoping that he and Travis Shaw could platoon for the rest of the 2016 season. The thirty four year old Hill had been decent in Milwaukee in the first half after two bad seasons, but he reverted to that form as soon as he put on a Red Sox uniform, posting a 54 OPS+ in 137 plate appearances. After another terrible eighty plate appearances for the Giants in 2017 Hill was done. On the bright side, the two players Dombrowski gave up for him never amounted to anything.
July 9, 2016: Traded Jose Almonte and Luis Alejandro Basabe to the Arizona Diamondbacks. Received Brad Ziegler.
Ziegler was an accomplished submarine righty who the Red Sox acquired for basically free to get same-sided batters out, a role which he fulfilled to perfection (1.52 ERA in 30 innings). Another clearly won trade for DD.
July 14, 2016: Traded Anderson Espinoza to the San Diego Padres. Received Drew Pomeranz.
At the time, Anderson Espinoza was a teenager in Single A while Drew Pomeranz had appeared to finally unlock his long-salivated over potential with an all-star appearance. Ideally the Padres were hoping Espinoza could eventually develop to that same quality while the Red Sox expected Pomeranz to fill the fourth spot in the rotation. Neither team got what they wanted, at least in 2016 or for most of thereafter; Espinoza immediately went down with a major arm injury which kept him from pitching professionally for five years. Pomeranz himself reverted to his pre-breakout level for the rest of the season, bounced back with a big 2017 (17-6, 3.32 ERA, a strikeout per inning across 174 frames) and then finally was the forgotten man on the 2018 pitching staff due to injuries and ineffectiveness (6.08 ERA in 74 innings, 66 strikeouts to 44 walks). At this point the thirty year old southpaw looked like the quintessential example of TNSTAAPP (There’s No Such Thing As A Pitching Prospect), another electric arm who would never match his potential due to injuries and command woes. Anyways, Pomeranz then seemed to resuscitate his career out of the bullpen for the 2019 Brewers and 2020-21 Padres with a sub-2 ERA across 70 innings in those three seasons…before injuries again struck. Though he has not pitched in the majors in three years he remains in the Dodgers minor league system, currently (where else) on the injured list.
December 6, 2016: Traded Victor Diaz, Luis Alexander Basabe, Michael Kopech and Yoán Moncada to the Chicago White Sox. Received Chris Sale.
It’s easy to forget now, but Moncada was not only a can’t miss prospect but one of the three best in all of baseball at the time, and Kopech was another Top 100 type. I’ve covered Kopech in my previous article on Red Sox pitching prospect busts but Moncada’s own failure to reach his ceiling was due more to injuries and a passive approach at the plate. Thus far into his career, Moncada has had two good seasons out of seven and played in at least 130 games in only three. With a strikeout rate of thirty percent, a declining walk rate, little power and less defense, he’s become a fourteen million dollar albatross even when on the field for the White Sox.
Sale, of course, had two Cy Young Award worthy campaigns before injuries and an ill-advised extension soured his final five seasons as a Red Sox. That extension will be discussed further when we come to it, but the trade on its own was inarguably a major victory.
Traded a player to be named later, Josh Pennington, Mauricio Dubón and Travis Shaw to the Milwaukee Brewers. Received Tyler Thornburg. The Boston Red Sox sent Yeison Coca (June 5, 2017) to the Milwaukee Brewers to complete the trade.
Yet another ill-fated trade for a relief pitcher, this time costing the Red Sox heavily in terms of value lost; Shaw went to become an all-star power bat at second and third base for the next two seasons in Milwaukee before his career petered out. Thornburg on the other hand contracted thoracic outlet syndrome from which he never recovered. Even if he had pitched well, the Red Sox could have used Shaw more than any setup man due to Dustin Pedroia’s career ending knee injury.
December 8, 2016: Signed Mitch Moreland as a free agent.
Mitch Moreland was a decent first baseman, but could Dave really not find someone better to play first over the next three years? Even if they cost more than $18.5 million?
December 20, 2016: Traded Clay Buchholz to the Philadelphia Phillies. Received Josh Tobias.
This was more of a psychic relief to Red Sox Nation than anything else, finally alleviating them of the constant confusion over which Bucholz would show up on the mound—the oft-injured and easy to hit version, or the dominating ace? Fittingly Clay’s last three seasons in the majors featured two horrid starts for Philly, sixteen dominating starts in Arizona, and then finally split the difference with a final dozen poor performances as a Blue Jay.
~2017~
June 12, 2017: Drafted Tanner Houck in the 1st round (24th pick) of the 2017 amateur draft.
Houck’s selection constitutes one-third of the total number of draft picks by Dombrowski that made which helped the Red Sox at the major league level (the other two being fourteenth round pick Kutter Crawford in 2016 and fellow first rounder Triston Casas in 2018); inability to find even depth pieces in the draft left the Red Sox farm system utterly void of impact talent by 2018.
June 23, 2017: Selected Doug Fister off waivers from the Los Angeles Angels.
As alluded to in my previous article, veteran GMs tend to reacquire players they were familiar with from previous stops. Fister had been an excellent fourth starter for the Tigers early in the 2010s but by 2017 the end was clearly staring him in the face; a 4.88 ERA in eighteen appearances (fifteen starts) just underlined this inevitable and unenviable conclusion.
July 26, 2017: Traded Shaun Anderson and Gregory Santos to the San Francisco Giants. Received Eduardo Núñez.
Nunez was the short-term solution to Pedroia’s knee injury. He turned out to be the medium-term solution too, as the degenerate condition of the incumbent’s affliction led DD to resign Nunez that winter. While fantastic down the stretch in 2017 this was a stretch of the infielder’s capabilities; Nunez suffered his own knee injuries and posted a remarkable -2.3 WAR as Boston’s primary keystone occupant over the 2018 and 2019 seasons.
July 31, 2017: Traded Gerson Bautista, Jamie Callahan and Stephen Nogosek to the New York Mets. Received Addison Reed.
Another deadline, another deal to reinforce the bullpen. Reed was inconsistent for the Red Sox during his two month stay, which turned out to be the penultimate chapter for his career—a poor 2018 in Minnesota marked the end of his major league career, an astonishingly quick demise even for a reliever.
~2018~
February 26, 2018: Signed J.D. Martinez as a free agent, five years and 110 million dollars.
The best free agent signing of the Dombrowski era, JD provided the power bat the Red Sox sorely lacked after Big Papi’s retirement. In his first and best season in Boston Martinez led the majors in both runs batted in and total bases, placed third in MVP voting, and earned Silver Sluggers at two different positions! He declined linearly from there, but remains a productive member of any team’s lineup to this day; he has spent the last two seasons as the Dodgers and now Mets’ DH, attempting to compensate for declining bat speed by sacrificing contact for power.
March 4, 2018: Signed Ryan Brasier as a free agent.
The quality of Brasier’s pitching is inversely proportional to the quality of the expectations laid upon him. Thus he alternates excellent if limited seasons with ostensibly healthier but more erratic contributions.
March 24, 2018: Traded Deven Marrero to the Arizona Diamondbacks. Received a player to be named later. The Arizona Diamondbacks sent Josh Taylor (May 15, 2018) to the Boston Red Sox to complete the trade.
Deven Marrero was the prototypical good-field/no-hit infielder. Taylor is yet another oft-injured reliever, though he at least gave the Red Sox two solid seasons as the primary southpaw in 2019 and 2021. After missing all of 2022, he was traded to the Royals for Adalberto Mondesi and a teenage infielder named Angel Pierre; while Mondesi knee injuries seem to have ended his career Pierre posted a .415 OBP in rookie ball last year. Keep an eye and ear out for him as he climbs through the minor league ranks.
June 4, 2018: Drafted Triston Casas in the 1st round (26th pick) of the 2018 amateur draft.
Get well soon. There’s only so much Bobby Dalbec a fan can take.
June 28, 2018: Traded Santiago Espinal to the Toronto Blue Jays. Received Steve Pearce and cash.
Moreland had never and would never hit southpaws, but it took until the middle of his second season in Boston for the Red Sox to provide him with a platoon partner. When they finally did so at least they chose one of the very best platoon players in the major leagues in Steve Pearce; Pearce of course would win the World Series MVP that should have gone to Price later that year.
July 25, 2018: Traded Jalen Beeks to the Tampa Bay Rays. Received Nathan Eovaldi.
Even had he not resigned with the team during the offseason, Eovaldi would have earned his place in Red Sox lore for his heroic six inning relief appearance in the World Series. We’ll discuss the extension later, but also note that Beeks is perhaps the only pitcher who the Rays failed to turn into a Cy Young contender. What’s the opposite of adding insult to injury?
July 30, 2018: Traded Ty Buttrey and Williams Jerez to the Los Angeles Angels. Received Ian Kinsler and cash.
With Nunez playing well below replacement level, the Red Sox needed a replacement for the replacement. Kinsler in his penultimate season at least provided a solid glove; just in case the Red Sox also picked up Brandon Phillips.
November 16, 2018: Signed Steve Pearce as a free agent. AND, December 6, 2018: Signed Nathan Eovaldi as a free agent.
These were covertly two of the worst transactions of the Dave Dombrowski era. Refusing to say goodbye to midseason rentals is risky enough, but the amount of money given to Pearce and Eovaldi also baffled reasonable explanations; a thirty-six-year-old platoon hitter at first base is replaceable enough, even when he’s not the weak side of the arrangement. Had Pearce played well and been healthy in 2019, perhaps the six and quarter million would have seemed mostly worth it; instead, he “hit” .180 in twenty nine games before retiring.
Meanwhile, Eovaldi’s lengthy injury history made it a minor miracle that he was healthy enough for the Red Sox during his three months in Boston—bringing him back for four years and sixty-eight million dollars can only be explained as a sentimental move, an excessive reward for that World Series performance. As could have been reasonably expected in December 2018, Nitro Nate only proved worthy of that contract in one out of four seasons; in the other three he was either injured for most of the season, ineffective, or both.
~2019~
March 23, 2019: Extended Chris Sale for five years, 145 million dollars.
It wasn’t the David Price contract that caused the fiscal panic that cost the Red Sox their best player since at least Carl Yastrzemski, not really. The Red Sox could have eaten that sunken cost, had it been the sole albatross on their pitching staff. But, of course, it was only one of three unnecessary contracts that Dave Dombrowski issued to injury-prone starting pitchers on the wrong side of thirty. Sale had already shown long term red flags in 2018, which argued for letting him play out his walk year in 2019 before possibly ponying up the cash to keep him. After all, the Red Sox also had to extend Xander Bogaerts as well as the inestimable Betts; those two would cost at least sixty million a year to retain. Since they were coming off the most dominant single season in franchise history, perhaps now was the best time to let go some of the chief contributors, before the Red Sox tricked themselves into trying to recapture lightning in a bottle…Well, you know what happened in reality.
Between them, Eovaldi, Sale, and Price cost the Red Sox $52 million in 2019 alone, then $67 million in 2020; accounting for other contracts (JBJ’s arbitration rang up $11 million, Bogey was extended for $20 million, and JD was on the books for about $24 million) that was at least $122 million dollars already assigned to six players entering 2020. Assuming a payroll of effectively $200 million, this would have left about thirty million to spend on the other twenty-odd players required to field a team after giving Mookie his presumed megadeal. Turning back to 2019, just like with the Tigers in 2015, Dave couldn’t even make his customary July trade for pitching; the acquisition of Andrew Cashner from the Orioles felt like a low-budget parody of his previous deadline splashes, which of course it was.
There’s the real reason Dave Dombrowski was fired—just as in Detroit his full throttle commitment to a win-now mandate from ownership eventually led to a top-heavy roster and barren farm system. Have fun while you can, Phillies Phans.
Final Note/Small Self Promotion I forget to add: You could have read this post ten days earlier if you follow my blog

Thankfully I have a log server setup that was able to capture what the router was outputting during this. The router needed to be rebooted manually before being able to function again. Is anyone aware of a fix for this kernel panic that occured on bcm63xx_nand?
Googling I was able to pull a post from 2022 with this issue and a github link.
First post: https://www.spinics.net/lists/stable/msg533157.html Final response: https://www.spinics.net/lists/stable/msg533157.html
GitHub: https://github.com/torvalds/linux/blob/mastedrivers/mtd/nand/raw/brcmnand/brcmnand.c
Looks like this is specifically an issue only Asus can resolve. Trying to call them is a nightmare, L1 can only read FAQ docs, and my L2 guy's first option was to offer a refurb unit before he proceeded to quite literally snore on the phone.
Posting this for hopefully visibility, but looks like I may go the Merlin route and install something else on this unit.

5/5/24 1:05:03 Warning RT1-D60F01D-C user kernel CSIMON: M2M usr already registered ... 5/5/24 1:05:03 Warning RT1-D60F01D-C user kernel CSIMON: CSIMON[1.1.0] Initialization 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel ---[ end trace cb7df7a7c2c07f1d ]--- 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel [] kthread+0xd8/0xf0 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel [] smpboot_thread_fn+0x1d8/0x280 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel [] schedule+0x34/0x90 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel [] __schedule+0x2f8/0x628 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel [] pick_next_task_rt+0xf0/0x1b0 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel [] pull_rt_task+0x2d8/0x328 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel [] irq_work_queue_on+0xe0/0x120 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel [] warn_slowpath_null+0x18/0x20 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel [] warn_slowpath_common+0x98/0xd0 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel [] dump_stack+0x90/0xb0 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel [] show_stack+0x14/0x20 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel [] dump_backtrace+0x0/0x150 5/12/24 12:49:51 Emergency RT1-D60F01D-C user kernel Call trace: 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel Hardware name: Broadcom-v8A (DT) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel CPU: 1 PID: 12 Comm: watchdog/1 Tainted: P O 4.1.52 #2 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel [last unloaded: nf_conntrack_ftp] 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel wlcsm(P) init_addr( (null) - (null)), core_addr(ffffffbffc000000 - ffffffbffc0014b0) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel bcmlibs(P) init_addr( (null) - (null)), core_addr(ffffffbffc008000 - ffffffbffc00a9d0) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel rdp_fpm init_addr( (null) - (null)), core_addr(ffffffbffc013000 - ffffffbffc0167a0) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel bdmf init_addr( (null) - (null)), core_addr(ffffffbffc021000 - ffffffbffc03da04) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel bcmvlan(P) init_addr( (null) - (null)), core_addr(ffffffbffc16f000 - ffffffbffc17e8f0) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel rdpa_gpl init_addr( (null) - (null)), core_addr(ffffffbffc196000 - ffffffbffc197bc8) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel rdpa_gpl_ext init_addr( (null) - (null)), core_addr(ffffffbffc1aa000 - ffffffbffc1aa0c0) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel rdpa(P) init_addr( (null) - (null)), core_addr(ffffffbffc1ae000 - ffffffbffc229b98) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel rdpa_usr init_addr( (null) - (null)), core_addr(ffffffbffc3cd000 - ffffffbffc3d2fa8) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel rdpa_mw init_addr( (null) - (null)), core_addr(ffffffbffc3dc000 - ffffffbffc3e06b8) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel chipinfo(P) init_addr( (null) - (null)), core_addr(ffffffbffc3e9000 - ffffffbffc3e9134) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel bcm_ingqos(P) init_addr( (null) - (null)), core_addr(ffffffbffc3ed000 - ffffffbffc3f1098) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel rdpa_cmd init_addr( (null) - (null)), core_addr(ffffffbffc42a000 - ffffffbffc4378e0) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel pktflow(P) init_addr( (null) - (null)), core_addr(ffffffbffc44e000 - ffffffbffc4766e0) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel cmdlist(P) init_addr( (null) - (null)), core_addr(ffffffbffc4a8000 - ffffffbffc4b41b0) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel bcm_enet init_addr( (null) - (null)), core_addr(ffffffbffc4c3000 - ffffffbffc4e16f4) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel pktrunner(P) init_addr( (null) - (null)), core_addr(ffffffbffc50b000 - ffffffbffc511968) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel nciLservices(P) init_addr( (null) - (null)), core_addr(ffffffbffc522000 - ffffffbffc522ab8) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel nciexLinuxETH(P) init_addr( (null) - (null)), core_addr(ffffffbffc529000 - ffffffbffc52aaf8) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel nciTMSkmod(P) init_addr( (null) - (null)), core_addr(ffffffbffc533000 - ffffffbffc55a808) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel bcmmcast init_addr( (null) - (null)), core_addr(ffffffbffc59f000 - ffffffbffc5ab798) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel bcm_pcie_hcd init_addr( (null) - (null)), core_addr(ffffffbffc5bf000 - ffffffbffc5c2b28) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel wfd init_addr( (null) - (null)), core_addr(ffffffbffc5cd000 - ffffffbffc5d17d8) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel pwrmngtd(P) init_addr( (null) - (null)), core_addr(ffffffbffc5da000 - ffffffbffc5da618) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel bcmpdc init_addr( (null) - (null)), core_addr(ffffffbffc5de000 - ffffffbffc5df6d0) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel bcmspu init_addr( (null) - (null)), core_addr(ffffffbffc5e5000 - ffffffbffc5ec648) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel bcm_thermal init_addr( (null) - (null)), core_addr(ffffffbffc5fd000 - ffffffbffc5fdb00) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel otp(P) init_addr( (null) - (null)), core_addr(ffffffbffc603000 - ffffffbffc6035a4) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel hnd init_addr( (null) - (null)), core_addr(ffffffbffc607000 - ffffffbffc634ae8) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel emf(P) init_addr( (null) - (null)), core_addr(ffffffbffc67f000 - ffffffbffc681828) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel igs(P) init_addr( (null) - (null)), core_addr(ffffffbffc688000 - ffffffbffc68b3e8) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel cfg80211 init_addr( (null) - (null)), core_addr(ffffffbffc694000 - ffffffbffc6b9118) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel dpsta(P) init_addr( (null) - (null)), core_addr(ffffffbffc6e2000 - ffffffbffc6e4af0) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel wl(P) init_addr( (null) - (null)), core_addr(ffffffbffc73b000 - ffffffbffcaa9a40) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel dhd init_addr( (null) - (null)), core_addr(ffffffbffcf4b000 - ffffffbffcfd5eb8) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel usb_common init_addr( (null) - (null)), core_addr(ffffffbffd091000 - ffffffbffd091208) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel usbcore init_addr( (null) - (null)), core_addr(ffffffbffd095000 - ffffffbffd0acf60) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel bcm_usb init_addr( (null) - (null)), core_addr(ffffffbffd0d1000 - ffffffbffd0d10a8) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel xhci_hcd init_addr( (null) - (null)), core_addr(ffffffbffd0d6000 - ffffffbffd0e5cc8) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel xhci_plat_hcd init_addr( (null) - (null)), core_addr(ffffffbffd0f9000 - ffffffbffd0f9538) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel xhci_pci init_addr( (null) - (null)), core_addr(ffffffbffd0fe000 - ffffffbffd0fe770) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel ehci_hcd init_addr( (null) - (null)), core_addr(ffffffbffd102000 - ffffffbffd109768) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel ehci_platform init_addr( (null) - (null)), core_addr(ffffffbffd111000 - ffffffbffd111890) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel ehci_pci init_addr( (null) - (null)), core_addr(ffffffbffd116000 - ffffffbffd116618) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel ohci_hcd init_addr( (null) - (null)), core_addr(ffffffbffd11a000 - ffffffbffd11ee28) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel ohci_platform init_addr( (null) - (null)), core_addr(ffffffbffd127000 - ffffffbffd127800) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel ohci_pci init_addr( (null) - (null)), core_addr(ffffffbffd12c000 - ffffffbffd12c270) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel mii init_addr( (null) - (null)), core_addr(ffffffbffd130000 - ffffffbffd130b70) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel usbnet init_addr( (null) - (null)), core_addr(ffffffbffd135000 - ffffffbffd138000) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel cdc_acm init_addr( (null) - (null)), core_addr(ffffffbffd141000 - ffffffbffd143670) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel libphy init_addr( (null) - (null)), core_addr(ffffffbffd14c000 - ffffffbffd14fad8) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel asix init_addr( (null) - (null)), core_addr(ffffffbffd15a000 - ffffffbffd15c880) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel ax88179_178a init_addr( (null) - (null)), core_addr(ffffffbffd165000 - ffffffbffd167770) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel cdc_ether init_addr( (null) - (null)), core_addr(ffffffbffd16d000 - ffffffbffd16d750) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel rndis_host init_addr( (null) - (null)), core_addr(ffffffbffd173000 - ffffffbffd173b10) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel cdc_ncm init_addr( (null) - (null)), core_addr(ffffffbffd179000 - ffffffbffd17b1e0) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel cdc_wdm init_addr( (null) - (null)), core_addr(ffffffbffd183000 - ffffffbffd1848c8) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel qmi_wwan init_addr( (null) - (null)), core_addr(ffffffbffd18a000 - ffffffbffd18a728) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel cdc_mbim init_addr( (null) - (null)), core_addr(ffffffbffd195000 - ffffffbffd195b48) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel ipheth init_addr( (null) - (null)), core_addr(ffffffbffd19a000 - ffffffbffd19ad38) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel ah4 init_addr( (null) - (null)), core_addr(ffffffbffd1a1000 - ffffffbffd1a2058) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel esp4 init_addr( (null) - (null)), core_addr(ffffffbffd1a6000 - ffffffbffd1a7270) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel ipcomp init_addr( (null) - (null)), core_addr(ffffffbffd1ac000 - ffffffbffd1ac380) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel xfrm4_tunnel init_addr( (null) - (null)), core_addr(ffffffbffd1b0000 - ffffffbffd1b0170) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel xfrm_user init_addr( (null) - (null)), core_addr(ffffffbffd1b4000 - ffffffbffd1b8558) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel nf_conntrack_ftp init_addr( (null) - (null)), core_addr(ffffffbffc005000 - ffffffbffc005c30) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel nf_nat_ftp init_addr( (null) - (null)), core_addr(ffffffbffc01c000 - ffffffbffc01c2c8) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel nf_conntrack_rtsp init_addr( (null) - (null)), core_addr(ffffffbffc15a000 - ffffffbffc15b260) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel nf_nat_rtsp init_addr( (null) - (null)), core_addr(ffffffbffc161000 - ffffffbffc161a38) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel nf_conntrack_h323 init_addr( (null) - (null)), core_addr(ffffffbffc359000 - ffffffbffc35ca00) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel nf_nat_h323 init_addr( (null) - (null)), core_addr(ffffffbffc16c000 - ffffffbffc16d0e8) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel tun init_addr( (null) - (null)), core_addr(ffffffbffc18f000 - ffffffbffc19254c) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel scsi_mod init_addr( (null) - (null)), core_addr(ffffffbffc365000 - ffffffbffc375960) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel sd_mod init_addr( (null) - (null)), core_addr(ffffffbffc19f000 - ffffffbffc1a3bd8) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel sg init_addr( (null) - (null)), core_addr(ffffffbffc3a3000 - ffffffbffc3a75d0) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel usb_storage init_addr( (null) - (null)), core_addr(ffffffbffc3b1000 - ffffffbffc3b4c20) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel uas init_addr( (null) - (null)), core_addr(ffffffbffc3d7000 - ffffffbffc3d9140) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel tfat(PO) init_addr( (null) - (null)), core_addr(ffffffbffc6e9000 - ffffffbffc71a368) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel tntfs(PO) init_addr( (null) - (null)), core_addr(ffffffbffce70000 - ffffffbffcebc438) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel Modules linked in: thfsplus(O) init_addr( (null) - (null)), core_addr(ffffffbffcee5000 - ffffffbffcef2084) 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel WARNING: CPU: 1 PID: 12 at kernel/irq_work.c:71 irq_work_queue_on+0xe0/0x120() 5/12/24 12:49:51 Warning RT1-D60F01D-C user kernel ------------[ cut here ]------------ 5/12/24 12:49:50 Info RT1-D60F01D-C user kernel CFG80211-ERROR) wl_cfg80211_del_key : WLC_SET_KEY error (-19) 5/12/24 12:49:50 Info RT1-D60F01D-C user kernel CFG80211-ERROR) wl_cfg80211_del_station : WLC_SCB_DEAUTHENTICATE_FOR_REASON err -19 5/12/24 12:49:50 Info RT1-D60F01D-C daemon hostapd eth6: STA 52:8b:6d:e0:43:40 IEEE 802.11: disassociated due to inactivity 5/12/24 12:49:50 Info RT1-D60F01D-C user kernel CFG80211-ERROR) wl_cfg80211_del_station : WLC_GET_ASSOCLIST error -19 5/12/24 12:49:50 Info RT1-D60F01D-C user kernel CFG80211-ERROR) wl_cfg80211_sta_info : GET STA INFO failed, -19 5/12/24 12:49:47 Info RT1-D60F01D-C user kernel CFG80211-ERROR) wl_cfg80211_sta_info : GET STA INFO failed, -19 5/12/24 12:49:21 Info RT1-D60F01D-C user kernel CFG80211-ERROR) wl_cfg80211_del_station : WLC_SCB_DEAUTHENTICATE_FOR_REASON err -19 5/12/24 12:49:21 Info RT1-D60F01D-C user kernel CFG80211-ERROR) wl_cfg80211_del_station : WLC_GET_ASSOCLIST error -19 5/12/24 12:49:21 Info RT1-D60F01D-C user kernel CFG80211-ERROR) wl_cfg80211_del_key : WLC_SET_KEY error (-19) 5/12/24 12:49:21 Info RT1-D60F01D-C user kernel CFG80211-ERROR) wl_cfg80211_del_station : WLC_SCB_DEAUTHENTICATE_FOR_REASON err -19 5/12/24 12:49:21 Info RT1-D60F01D-C daemon hostapd eth6: STA 54:27:1e:97:2d:5a IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE) 5/12/24 12:49:21 Info RT1-D60F01D-C user kernel CFG80211-ERROR) wl_cfg80211_del_station : WLC_GET_ASSOCLIST error -19 5/12/24 12:49:20 Info RT1-D60F01D-C user kernel CFG80211-ERROR) wl_cfg80211_del_key : WLC_SET_KEY error (-19) 5/12/24 12:49:20 Info RT1-D60F01D-C user kernel CFG80211-ERROR) wl_cfg80211_del_station : WLC_SCB_DEAUTHENTICATE_FOR_REASON err -19 5/12/24 12:49:20 Info RT1-D60F01D-C daemon hostapd eth6: STA 54:27:1e:97:2d:5a IEEE 802.11: disassociated due to inactivity 5/12/24 12:49:20 Info RT1-D60F01D-C user kernel CFG80211-ERROR) wl_cfg80211_del_station : WLC_GET_ASSOCLIST error -19 5/12/24 12:49:20 Info RT1-D60F01D-C user kernel CFG80211-ERROR) wl_cfg80211_sta_info : GET STA INFO failed, -19 5/12/24 12:49:17 Info RT1-D60F01D-C user kernel CFG80211-ERROR) wl_cfg80211_sta_info : GET STA INFO failed, -19 5/12/24 12:49:07 Info RT1-D60F01D-C user kernel CFG80211-ERROR) wl_cfg80211_del_station : WLC_SCB_DEAUTHENTICATE_FOR_REASON err -19 5/12/24 12:49:07 Info RT1-D60F01D-C user kernel CFG80211-ERROR) wl_cfg80211_del_station : WLC_GET_ASSOCLIST error -19 5/12/24 12:49:07 Info RT1-D60F01D-C user kernel CFG80211-ERROR) wl_cfg80211_del_key : WLC_SET_KEY error (-19) 5/12/24 12:49:07 Info RT1-D60F01D-C daemon hostapd eth6: STA 5c:60:ba:5b:38:05 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE) 5/12/24 12:49:07 Info RT1-D60F01D-C user kernel CFG80211-ERROR) wl_cfg80211_del_station : WLC_SCB_DEAUTHENTICATE_FOR_REASON err -19 5/12/24 12:49:07 Info RT1-D60F01D-C user kernel CFG80211-ERROR) wl_cfg80211_del_station : WLC_GET_ASSOCLIST error -19 5/12/24 12:49:07 Info RT1-D60F01D-C user kernel CFG80211-ERROR) wl_cfg80211_del_station : WLC_SCB_DEAUTHENTICATE_FOR_REASON err -19 5/12/24 12:49:07 Info RT1-D60F01D-C user kernel CFG80211-ERROR) wl_cfg80211_del_station : WLC_GET_ASSOCLIST error -19 5/12/24 12:49:07 Info RT1-D60F01D-C user kernel CFG80211-ERROR) wl_cfg80211_del_key : WLC_SET_KEY error (-19) 5/12/24 12:49:07 Info RT1-D60F01D-C user kernel CFG80211-ERROR) wl_cfg80211_del_station : WLC_SCB_DEAUTHENTICATE_FOR_REASON err -19 5/12/24 12:49:07 Info RT1-D60F01D-C daemon hostapd eth6: STA de:46:24:7f:8d:41 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE) 5/12/24 12:49:07 Info RT1-D60F01D-C user kernel CFG80211-ERROR) wl_cfg80211_del_station : WLC_GET_ASSOCLIST error -19 5/12/24 12:49:06 Info RT1-D60F01D-C user kernel CFG80211-ERROR) wl_cfg80211_del_key : WLC_SET_KEY error (-19) 5/12/24 12:49:06 Info RT1-D60F01D-C daemon hostapd eth6: STA 5c:60:ba:5b:38:05 IEEE 802.11: disassociated due to inactivity 5/12/24 12:49:06 Info RT1-D60F01D-C user kernel CFG80211-ERROR) wl_cfg80211_del_station : WLC_SCB_DEAUTHENTICATE_FOR_REASON err -19 5/12/24 12:49:06 Info RT1-D60F01D-C user kernel CFG80211-ERROR) wl_cfg80211_del_station : WLC_GET_ASSOCLIST error -19 5/12/24 12:49:06 Info RT1-D60F01D-C user kernel CFG80211-ERROR) wl_cfg80211_sta_info : GET STA INFO failed, -19 5/12/24 12:49:06 Info RT1-D60F01D-C user kernel CFG80211-ERROR) wl_cfg80211_del_key : WLC_SET_KEY error (-19) 5/12/24 12:49:06 Info RT1-D60F01D-C daemon hostapd eth6: STA de:46:24:7f:8d:41 IEEE 802.11: disassociated due to inactivity 5/12/24 12:49:06 Info RT1-D60F01D-C user kernel CFG80211-ERROR) wl_cfg80211_del_station : WLC_SCB_DEAUTHENTICATE_FOR_REASON err -19 5/12/24 12:49:06 Info RT1-D60F01D-C user kernel CFG80211-ERROR) wl_cfg80211_del_station : WLC_GET_ASSOCLIST error -19 5/12/24 12:49:06 Info RT1-D60F01D-C user kernel CFG80211-ERROR) wl_cfg80211_sta_info : GET STA INFO failed, -19 5/12/24 12:49:04 Emergency RT1-D60F01D-C user WAN Connection: WAN(0) link down. 5/12/24 12:49:04 Info RT1-D60F01D-C user kernel CFG80211-ERROR) wl_cfg80211_del_station : WLC_SCB_DEAUTHENTICATE_FOR_REASON err -19 5/12/24 12:49:04 Info RT1-D60F01D-C user kernel CFG80211-ERROR) wl_cfg80211_del_station : WLC_GET_ASSOCLIST error -19 5/12/24 12:49:04 Info RT1-D60F01D-C user kernel CFG80211-ERROR) wl_cfg80211_del_key : WLC_SET_KEY error (-19) 5/12/24 12:49:04 Info RT1-D60F01D-C daemon hostapd eth6: STA f0:b3:ec:80:b9:20 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE) 5/12/24 12:49:04 Info RT1-D60F01D-C user kernel CFG80211-ERROR) wl_cfg80211_del_station : WLC_SCB_DEAUTHENTICATE_FOR_REASON err -19 5/12/24 12:49:04 Info RT1-D60F01D-C user kernel CFG80211-ERROR) wl_cfg80211_del_station : WLC_GET_ASSOCLIST error -19 5/12/24 12:49:03 Info RT1-D60F01D-C user kernel CFG80211-ERROR) wl_cfg80211_del_station : WLC_SCB_DEAUTHENTICATE_FOR_REASON err -19 5/12/24 12:49:03 Info RT1-D60F01D-C user kernel CFG80211-ERROR) wl_cfg80211_del_station : WLC_GET_ASSOCLIST error -19 5/12/24 12:49:03 Info RT1-D60F01D-C user kernel CFG80211-ERROR) wl_cfg80211_del_key : WLC_SET_KEY error (-19) 5/12/24 12:49:03 Info RT1-D60F01D-C daemon hostapd eth6: STA e2:55:49:cf:7b:35 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE) 5/12/24 12:49:03 Info RT1-D60F01D-C user kernel CFG80211-ERROR) wl_cfg80211_del_station : WLC_SCB_DEAUTHENTICATE_FOR_REASON err -19 5/12/24 12:49:03 Info RT1-D60F01D-C user kernel CFG80211-ERROR) wl_cfg80211_del_station : WLC_GET_ASSOCLIST error -19 5/12/24 12:49:03 Warning RT1-D60F01D-C user kernel Print bfdIndexLUT 5/12/24 12:49:03 Warning RT1-D60F01D-C user kernel Print BFM table 5/12/24 12:49:03 Warning RT1-D60F01D-C user kernel Print smctinytable 5/12/24 12:49:03 Warning RT1-D60F01D-C user kernel Print smctable 5/12/24 12:49:03 Warning RT1-D60F01D-C user kernel Print vasippchistory 5/12/24 12:49:03 Warning RT1-D60F01D-C user kernel Print vasipregister 5/12/24 12:49:03 Warning RT1-D60F01D-C user kernel Print axmacphyIfTbl 5/12/24 12:49:03 Info RT1-D60F01D-C user kernel CFG80211-ERROR) wl_cfg80211_sta_info : GET STA INFO failed, -19 5/12/24 12:49:03 Info RT1-D60F01D-C user kernel CFG80211-ERROR) wl_cfg80211_sta_info : GET STA INFO failed, -19 5/12/24 12:49:02 Info RT1-D60F01D-C user kernel CFG80211-ERROR) wl_cfg80211_del_key : WLC_SET_KEY error (-19) 5/12/24 12:49:02 Info RT1-D60F01D-C daemon hostapd eth6: STA f0:b3:ec:80:b9:20 IEEE 802.11: disassociated due to inactivity 5/12/24 12:49:02 Info RT1-D60F01D-C user kernel CFG80211-ERROR) wl_cfg80211_del_station : WLC_SCB_DEAUTHENTICATE_FOR_REASON err -19 5/12/24 12:49:02 Info RT1-D60F01D-C user kernel CFG80211-ERROR) wl_cfg80211_del_station : WLC_GET_ASSOCLIST error -19 5/12/24 12:49:02 Info RT1-D60F01D-C user kernel CFG80211-ERROR) wl_cfg80211_sta_info : GET STA INFO failed, -19 5/12/24 12:49:02 Info RT1-D60F01D-C user kernel CFG80211-ERROR) wl_cfg80211_del_key : WLC_SET_KEY error (-19) 5/12/24 12:49:02 Info RT1-D60F01D-C daemon hostapd eth6: STA e2:55:49:cf:7b:35 IEEE 802.11: disassociated due to inactivity 5/12/24 12:49:02 Info RT1-D60F01D-C user kernel CFG80211-ERROR) wl_cfg80211_del_station : WLC_SCB_DEAUTHENTICATE_FOR_REASON err -19 5/12/24 12:49:02 Info RT1-D60F01D-C user kernel CFG80211-ERROR) wl_cfg80211_del_station : WLC_GET_ASSOCLIST error -110 5/12/24 12:48:57 Info RT1-D60F01D-C user kernel CFG80211-ERROR) wl_cfg80211_sta_info : GET STA INFO failed, -110 5/12/24 12:48:52 Info RT1-D60F01D-C user kernel CFG80211-ERROR) wl_cfg80211_sta_info : GET STA INFO failed, -110 5/12/24 12:48:47 Info RT1-D60F01D-C user kernel CFG80211-ERROR) wl_cfg80211_sta_info : GET STA INFO failed, -110 5/12/24 12:48:32 Warning RT1-D60F01D-C user kernel [] start_kernel+0x390/0x3a4 5/12/24 12:48:32 Warning RT1-D60F01D-C user kernel [] rest_init+0x88/0x98 5/12/24 12:48:32 Warning RT1-D60F01D-C user kernel [] cpu_startup_entry+0x1ec/0x250 5/12/24 12:48:32 Warning RT1-D60F01D-C user kernel [] cpuidle_enter+0x18/0x20 5/12/24 12:48:32 Warning RT1-D60F01D-C user kernel [] el1_irq+0x80/0xf8 5/12/24 12:48:32 Warning RT1-D60F01D-C user kernel 7e80: 00378b34 ffffffc0 00777ec0 ffffffc0 00378b3c ffffffc0 60000145 00000000 5/12/24 12:48:32 Warning RT1-D60F01D-C user kernel 7e60: 0076e000 ffffffc0 1ffd7338 ffffffc0 007b44c0 ffffffc0 00777ec0 ffffffc0 5/12/24 12:48:32 Warning RT1-D60F01D-C user kernel 7e40: 00000001 00000000 f6e3469c 0000681b 00774000 ffffffc0 00945000 ffffffc0 5/12/24 12:48:32 Warning RT1-D60F01D-C user kernel 7e20: 00000000 00000000 f6ea1ee0 0000681b 1ffd7338 ffffffc0 00000001 00000000 5/12/24 12:48:32 Warning RT1-D60F01D-C user kernel 7e00: f69c0920 00000000 00000000 00000000 000f5908 ffffffc0 00000000 00000000 5/12/24 12:48:32 Warning RT1-D60F01D-C user kernel 7de0: 00000000 00000000 f69bff9c 00000000 f69bfe04 00000000 f69bfe18 00000000 5/12/24 12:48:32 Warning RT1-D60F01D-C user kernel 7dc0: 30000000 003b8aa5 09c95568 ffffffc0 0078a7f0 ffffffc0 06ce157c 00000001 5/12/24 12:48:32 Warning RT1-D60F01D-C user kernel 7da0: 00520206 00000000 14000000 00000000 0c2b1114 00000000 00000018 00000000 5/12/24 12:48:32 Warning RT1-D60F01D-C user kernel 7d80: 00777ec0 ffffffc0 00378b3c ffffffc0 f6ea1ee0 0000681b a8000000 0041f2cd 5/12/24 12:48:32 Warning RT1-D60F01D-C user kernel 7d60: f6ea1ee0 0000681b 00000000 00000080 5/12/24 12:48:32 Warning RT1-D60F01D-C user kernel Exception stack(0xffffffc000777d70 to 0xffffffc000777ea0) 5/12/24 12:48:32 Warning RT1-D60F01D-C user kernel [] gic_handle_irq+0x88/0x90 5/12/24 12:48:32 Warning RT1-D60F01D-C user kernel [] handle_IPI+0x190/0x1a0 5/12/24 12:48:32 Warning RT1-D60F01D-C user kernel [] dump_stack+0x90/0xb0 5/12/24 12:48:32 Warning RT1-D60F01D-C user kernel [] show_stack+0x14/0x20 5/12/24 12:48:32 Warning RT1-D60F01D-C user kernel [] dump_backtrace+0x0/0x150 5/12/24 12:48:32 Emergency RT1-D60F01D-C user kernel Call trace: 5/12/24 12:48:32 Warning RT1-D60F01D-C user kernel Hardware name: Broadcom-v8A (DT) 5/12/24 12:48:32 Warning RT1-D60F01D-C user kernel CPU: 0 PID: 0 Comm: swappe0 Tainted: P O 4.1.52 #2 5/12/24 12:48:32 Critical RT1-D60F01D-C user kernel CPU0: stopping 5/12/24 12:48:32 Warning RT1-D60F01D-C user kernel [] SyS_write+0x44/0xa0 5/12/24 12:48:32 Warning RT1-D60F01D-C user kernel [] vfs_write+0x90/0x188 5/12/24 12:48:32 Warning RT1-D60F01D-C user kernel [] __vfs_write+0xa8/0x108 5/12/24 12:48:32 Warning RT1-D60F01D-C user kernel [] generic_file_write_iter+0xcc/0x200 5/12/24 12:48:32 Warning RT1-D60F01D-C user kernel [] __generic_file_write_iter+0x148/0x198 5/12/24 12:48:32 Warning RT1-D60F01D-C user kernel [] generic_perform_write+0x110/0x198 5/12/24 12:48:32 Warning RT1-D60F01D-C user kernel [] jffs2_write_end+0x134/0x238 5/12/24 12:48:32 Warning RT1-D60F01D-C user kernel [] jffs2_write_inode_range+0x178/0x298 5/12/24 12:48:32 Warning RT1-D60F01D-C user kernel [] jffs2_write_dnode+0xd8/0x398 5/12/24 12:48:32 Warning RT1-D60F01D-C user kernel [] jffs2_flash_writev+0x1d4/0x478 5/12/24 12:48:32 Warning RT1-D60F01D-C user kernel [] __jffs2_flush_wbuf+0xb8/0xd18 5/12/24 12:48:32 Warning RT1-D60F01D-C user kernel [] mtd_write+0x4c/0x68 5/12/24 12:48:32 Warning RT1-D60F01D-C user kernel [] part_write+0x20/0x28 5/12/24 12:48:32 Warning RT1-D60F01D-C user kernel [] nand_write+0x5c/0x88 5/12/24 12:48:32 Warning RT1-D60F01D-C user kernel [] nand_do_write_ops+0xb4/0x3d8 5/12/24 12:48:32 Warning RT1-D60F01D-C user kernel [] nand_check_wp+0x40/0x68 5/12/24 12:48:32 Warning RT1-D60F01D-C user kernel [] brcmnand_cmdfunc+0x128/0x2f0 5/12/24 12:48:32 Warning RT1-D60F01D-C user kernel [] brcmnand_send_cmd+0x134/0x140 5/12/24 12:48:32 Warning RT1-D60F01D-C user kernel [] panic+0xd8/0x220 5/12/24 12:48:32 Warning RT1-D60F01D-C user kernel [] dump_stack+0x90/0xb0 5/12/24 12:48:32 Warning RT1-D60F01D-C user kernel [] show_stack+0x14/0x20 5/12/24 12:48:32 Warning RT1-D60F01D-C user kernel [] dump_backtrace+0x0/0x150 5/12/24 12:48:32 Emergency RT1-D60F01D-C user kernel Call trace: 5/12/24 12:48:32 Warning RT1-D60F01D-C user kernel Hardware name: Broadcom-v8A (DT) 5/12/24 12:48:32 Warning RT1-D60F01D-C user kernel CPU: 1 PID: 1494 Comm: wlc_monitor Tainted: P O 4.1.52 #2 5/12/24 12:48:32 Emergency RT1-D60F01D-C user kernel Kernel panic - not syncing: BUG! 5/12/24 12:48:31 Warning RT1-D60F01D-C user kernel BUG: failure at drivers/mtd/nand/brcmnand/brcmnand.c:1339/brcmnand_send_cmd()! 5/12/24 12:48:31 Error RT1-D60F01D-C user kernel bcm63xx_nand ff801800.nand: intfc status 700000e0 5/12/24 12:48:31 Error RT1-D60F01D-C user kernel bcm63xx_nand ff801800.nand: timeout waiting for command 0x1 

I've seen a few people's takes on a wardrobe system before. I've been in bed trying to get to sleep thinking about this, so here's my take on it. Ideally, it would be simple to create and fit thematically in the game, which I've tried to do.
Infinitycloset - Closet door in world 1 town which occasionally opens to reveal a void (potentially has an infinity mirror effect within). Unlocks around mid-World 1. Something compels you to throw old junk into the infinity...
The closet lets you 'sell' it equippable items. You can sell anything for the first equipment page, and trophies and capes earned from quests and boss kills from equipment tab 2. Special capes, premium hats, and 1 and done trophies would not be sellable. So, you'd be able to sell Dice Dynamo, but not Idle Skiller. These are collected similarly to the slab. When you put an item in the closet, it's gone, and you can't get it back.
Rewards after selling numbers of specific items:

• 1 item - The void: lists the item like slab and shows the stats.
• 10 - Psychic Materialization: lets you create an ethereal copy of the item. It can't be used in crafting or post office, only worn.
• 100 - Secret technique: unlocks extra bonuses similar in scope to shiny pets. These bonuses would be global across all characters to potentially encourage different setups rather than everyone being in identical gear. For instance, say "copper pickaxe" increased multi-ore chance for copper ore by 100%. Every character gets that bonus if 1 character has the ethereal copy equipped. An exception would be gear for warriors, etc. would only affect warriors.
• 1000 - Yoked: Ethereal item spawns with maxed godlier creation on all of the stats and lets you apply upgrade stones.
• 10000 - Storefront mannequin: By random happenstance, one of your items landed on a floating mannequin, activating the secret technique permanently.
• 100000 - Taupe stacks: The closet has had enough of your antics. Your stack is now colored taupe, to show its disdain for you.

Closet mastery - Potentially equinox or rift upgrade - Gives x1.01 to all secret techniques per taupe stack.
Junksight aura - Unlocked at start of world 4. The closet has an eye for trash, and it knows how to find all the junk you haven't been looting from the mountains of corpses. The basic idea for this would be to reactivate quest items from the game with no value. You would be able to target one world at a time or turn it off completely. It would add farming value for certain mobs. Drop rate would be around 1/1000 of the basic item but it would also be affected by multikill. So, in the time it takes to get 1 billion regular items, you'd get around 1 million quest items. Almost all of the junk is from world 1 and 2, so I'd redistribute it across worlds 1-4
Example distribution of quest items:
World 1:

• ketchup bottle - red mushroom
• time thingy - baby boa
• strange rock - poop

World 2:

• sesame seed - mimic
• casual confidante - pincermin
• triumphant treason - tyson
• claiming cashe - sand giant

World 3:

• employee statistics - bloque
• signed contract - penguin
• loomi's room key - quenchie
• monster rating - cryo snake

World 4:

• mustard bottle - Donut
• dog bone - Gelatinous Cuboid
• corporatube sub - flying worm
• instablab follower - biggole worm
• cloudsound follower - octoblob

Clobulyte vendor - By channeling the power of useless items, the Clobulyte will search all parallel dimensions for a version of you who hasn't sold this particular quest reward. He will then mug parallel you.
At the same time the Junksight aura is unlocked, you get a secondary vendor near the closet. This would be a weekly reset and offer inventory similarly to how chip inventory is offered. 3-5 random quest rewards would be offered starting at 1000 of a random junk quest item. Each buy increases it to 2000, 3000, etc. The last slot would only sell trophies, starting at 10000. There would need to be some sort of unlock for the trophies, possibly requiring all 10 characters to get the world 5 completion trophy before being able to buy it.
Here's the list of items I found which Clobulyte would sell: Red Headband, Junk Pickaxe, old hatchet, stump prop, little wooden katana, alien headband, carrot horror, silver stopwatch, adam's leaf, frisbee ring, mcr shirt, cowbo Galloneer, Jar, shallow watering, oceanic ring, deepwater trench ring
Trophies: Blunder Hero, king of food, yumyum sheriff, Frost prince, critter baron, nebula royal, One of the divine
Example special techinques:
Obviously, coming up with useful bonuses is the hardest part. Especially because I don't know what would be difficult or possible to implement. These are just some of the things I've thought would be neat. Since the text of these are long, they wouldn't display on the item, but only on the closet UI.
One note: some 'sets' of items would work like the lab gems. When all of them are activated, they double the bonus.
Early world X armor set: (Copper, Dementia, Lustre, etc). World X drops have 5% Rares droprate (See Journeyman Rares Everywhere talent) and 10% when full set is activated.
Late world X armor set: (Silver, platinum, etc) World X kills have 1/2000 chance to summon plunderous mobs.
Bored beanie: World 1 kills can spawn a giant bored bean, who drops his prized collection of world 1 trophies.
World X dna splicer: Increases Pet fight damage from world X by the average DNA levels, up to x2.0
Warrior weapon: 1% Chance for skills to not enter cool down.
Mage weapon: 1% Chance to increase the length of any buff cast by 50%
Archer weapon: 1% Chance to cast whale attack instead of auto attack.
Lucky lad: Equips the misc bonus of Lucky lad again.
Luckier lad: Equips the misc bonus of Luckier lad again.
World X Completion trophy: All equips from World X have 30 free mastery points (x1.3 effectiveness)
Boss X Cape: Kills of the boss on the hardest difficulty award 1 extra Gem.
Final thoughts
Anyway, even if the bonuses were just like 10% mining experience, I think the system itself would be kind of fun. It would give you a place to put a lot more resources and tie together quest rewards from earlier worlds that we all got rid of. Also, it avoids the issue of how you would store / remove items which may have custom stats. For this reason, keychains wouldn't really work. Hopefully I can now go to sleep. Yes, I know Lava doesn't read this. I don't care. Thanks for coming to my Ted talk.

Setting Up a Controlled Registration Process

In today's digital age, ensuring the security and integrity of online platforms is paramount, particularly when it comes to user registration and data protection. One effective method for enhancing security is by implementing a whitelist system for email addresses during the registration process. This approach allows only a predetermined set of email addresses to create accounts, effectively preventing unauthorized access and reducing the risk of spam or fraudulent activities. By leveraging JavaScript, developers can easily integrate this functionality into their web applications, offering a robust solution to safeguard their platforms against unwelcome registrations.
The concept of a whitelist-based registration system not only enhances security but also ensures that access is granted exclusively to users who meet specific criteria, such as being a part of an organization or a closed community. This method is particularly useful for platforms that require a high level of confidentiality and control over user access. The implementation of such a system using JavaScript involves checking submitted email addresses against a predefined list and proceeding with the registration process only if the email is found in the whitelist. This article will guide you through the steps to set up this system, ensuring your platform remains exclusive and secure.

Command/Function	Description
includes()	Checks if an array includes a certain value, returning true or false as appropriate.
push()	Adds one or more elements to the end of an array and returns the new length of the array.
indexOf()	Returns the first index at which a given element can be found in the array, or -1 if it is not present.

Deep Dive into Email Whitelisting Strategies

Email whitelisting is a critical strategy for enhancing the security and integrity of web applications. It serves as a gatekeeper, ensuring that only emails from approved senders can perform certain actions, such as registering for an account. This method is particularly effective in preventing spam and unauthorized access, which are common issues in open registration systems. By restricting access to a select group of email addresses, administrators can maintain a higher level of control over who is allowed to participate in their platform. Moreover, email whitelisting can be customized to suit various needs, whether for a small-scale project or a large organization, making it a versatile tool in the developer’s arsenal.
Implementing an email whitelist requires careful consideration and planning. The list can be static, where the allowed emails are hardcoded into the application, or dynamic, allowing administrators to add or remove addresses as needed. Dynamic lists offer more flexibility but require a more complex setup, including a user interface for managing the list and backend logic to check the email against the list during registration. Regardless of the approach, it's crucial to ensure that the list is securely stored and managed to prevent unauthorized modifications. Additionally, developers must consider user experience, providing clear feedback when a user attempts to register with an email not on the whitelist and offering guidance on how to proceed if legitimate users are inadvertently blocked.

Validating Email Addresses Against a Whitelist

JavaScript Example

const whitelist = ['user@example.com', 'admin@example.com']; function validateEmail(email) { return whitelist.includes(email); } 

Adding an Email to the Whitelist

JavaScript Snippet

function addToWhitelist(email) { if (whitelist.indexOf(email) === -1) { whitelist.push(email); console.log(email + ' added to whitelist'); } else { console.log(email + ' is already in the whitelist'); } } 

Enhancing Security with Email Whitelists

The implementation of email whitelists as a security measure in registration processes is becoming increasingly popular among web developers and administrators. This method involves creating a list of approved email addresses that are allowed to access certain resources or register for a service. The primary advantage of using a whitelist is its ability to provide an additional layer of security, ensuring that only authorized users can create accounts or access sensitive information. This is particularly beneficial for organizations or services that require strict control over user access, such as corporate intranets, educational platforms, or membership-based websites. By limiting registration to approved email addresses, administrators can effectively prevent unauthorized access and mitigate the risk of cyber threats.
Moreover, the use of email whitelists can significantly reduce the incidence of spam and fraudulent registrations, which are common challenges for public-facing websites. It allows for a more managed and controlled user base, enhancing the overall user experience by ensuring that services are used by the intended audience. However, the implementation of such a system requires careful consideration and management. Administrators must maintain and update the whitelist to accommodate new users, which can be labor-intensive for larger organizations. Additionally, it's crucial to balance security measures with user convenience, as overly restrictive whitelisting could deter potential users or create barriers to access for legitimate users.

Frequently Asked Questions on Email Whitelisting

1. Question: What is an email whitelist?
2. Answer: An email whitelist is a list of email addresses that are allowed to access a certain service or resource, used to enhance security and prevent unauthorized registrations.
3. Question: How does email whitelisting improve security?
4. Answer: It ensures that only pre-approved users can register or access specific services, reducing the risk of unauthorized access, spam, and fraudulent activities.
5. Question: Can email whitelisting be applied to any website?
6. Answer: Yes, it can be implemented on any website or platform that requires user registration or access control.
7. Question: Is managing an email whitelist difficult?
8. Answer: It can be, especially for larger organizations, as it requires regular updates to include new approved users and remove those no longer authorized.
9. Question: Does email whitelisting guarantee 100% security?
10. Answer: While it significantly enhances security, no system is foolproof, and it should be part of a comprehensive security strategy.
11. Question: What happens if an approved email is compromised?
12. Answer: Administrators should remove the compromised email from the whitelist immediately and take steps to secure the account.
13. Question: How do users get added to an email whitelist?
14. Answer: Administrators manually add users to the whitelist based on their eligibility or upon request.
15. Question: Can users request to be added to the whitelist?
16. Answer: Yes, users can request access, but their email addresses must be approved by an administrator.
17. Question: Are there alternatives to email whitelisting for security?
18. Answer: Yes, other methods include multi-factor authentication, CAPTCHAs, and blacklisting, but each has its own advantages and disadvantages.
19. Question: How can organizations ensure their whitelist is up-to-date?
20. Answer: Regularly review and update the whitelist to include new users and remove those who are no longer authorized or have left the organization.

Wrapping Up on Email Whitelists

Implementing an email whitelist is an effective strategy to enhance the security and integrity of web applications. By allowing only pre-approved email addresses to register or access certain services, administrators can significantly mitigate the risk of unauthorized access and cyber threats. While the process requires ongoing management, including the regular update of the whitelist, the benefits far outweigh the administrative effort. It ensures a safer environment for users and protects sensitive information from potential breaches. Moreover, this method plays a crucial role in maintaining the quality of the user base, preventing spam registrations, and ensuring that services are utilized by the intended audience. As digital platforms continue to evolve, the importance of implementing robust security measures like email whitelisting cannot be overstated. It is a proactive step towards safeguarding digital assets, enhancing user trust, and ensuring the longevity and success of online platforms.
https://www.tempmail.us.com/en/whitelist/implementing-a-registration-whitelist-with-javascript

Low Profile Mushkin Redline ST DDR5-6400MHz 64GB 2x32GB Dual Channel with lowest timings ever C30-37-37-96 So i can put them in any ITX case without wondering for AIO or any air cooler since they are very low profile, at the same time i didn't Stick to the 6000MHz Sweet spot cause in the near future the new Sweet spot with Zen 5 could probably be 6400MHz, also i didn't want tò renounce tò the latencies that 6000MHz modules can offer, and these 6400MHz modules have same CL30 which Is the lowest on 6000MHz, and other timings are unbeleable Low as well 37-37-96. This means in theory we can have Better performance and latencies for AMD setup.
Now the question Is: these modules are not registed AMD EXPO not either Intel XMP, i have tò use them with 7950X3D and Asus Rog Strix X670E-I Gaming Mini ITX which says for rams 6400+(OC), all motherboards stops at 5600MHz, everything above Is considered OC, so we have here only two ram slots and this is the max amount of ram to be reachen on 2 slot to use at least dual channel.
Will they work Just mounting them, since they have no dedicated profile? Will the system boot with ram 6400MHz CL30-37-37-96 1,4v? Is this 1:1 with CPU so i get max performance from bot RAM and CPU? If they dont boot correctly can they be manual set to 6400MHz CL30-37-37-37? In this case all other untouched timings Will make a difference? After all, should i stik tò some Low Profile DDR5 64GB 2x32GB Dual Channel Kingston Fury Beast 6000MHz CL30-36-36-32 1,4v wich have bot Intel XMP 3.0 and AMD EXPO 1.1 profiles? Will this ran at 1:1 and Will they autoconfig on startup with profiles?
The reason i wanna choice between these two Memories Is because i wanna take the highest performance at lowest timings still trying tò ran 1:1 and possible with autoconfig with auto presets and profiles and with max amount on RAM possible on two slots for dual channel and also because i Ve read that on bigger motherboards some people are having troubles using 4 slots and quad Channel Is basically useless.
Also wanna understand what you mean with 1:1.
Is there possibility tò have Better performances on higher clocked rams such as 8400MHz? Does that make difference? The higher latencies are a problem? Will the CPU and chipset manage It automatically? Depends from motherboards? Very confusional.
I've seen this pair of DDR5 8200MHz CL36 1,4V 48GB 2x24GB Dual Channel Intel XMP 3.0 and AMD EXPO 1.1. They are higher frequency lowest timings still 1.4v and have Intel and AMD profiles. So should they work? Would there run at 1:1? Depending from motherboards? But no motherboard list 8200+ In any case if you set them manually would you obtain Better performances of the other cited 6000 and 6400 modules?
Another alternative of which ive seen a test comparing 6000MHz CL30-36-36-32 1,4v rams 64GB 2x32GB Dual Channel with 7950X3D UCLK=MCLK 1:1 Gear 1 vs 8000MHz CL38-48-48-128 1,45v rams 48GB 2x24GB Dual Channel with 7950X3D UCLK=FCLK 1:2 Gear 2 and the difference was great despite 1:2 and higher voltage less amount of ram but It didn't use AMD EXPO so i dont even know how they GOT them working. Using 8400MHz modules could make a difference?
For what i know i seem tò have understood that best choice Is Low Profile 64GB 2x32GB DDR5 6000MHz Cl30-36-36-32 at 1,4v with both INTEL XMP 3.0 and AMD EXPO 1.1 profiles tò run perfectly at 1:1 and everything else Is useless.
But i Ve also seen test in which RAM Speed matters and 8400MHz rams have no enemies and surclasses 6000MHz RAM.
I dunno which Low profiles RAMs ro buy for my 7950X3D and X670 on mini ITX.

Playstation 3

• 007 Quantom of Solace - 5
• 2014 FIFA World Cup Brazil - 4
• Alpha Protocol - 14
• Assassins Creed Brotherhood - 3
• Assassins Creed II - 3
• Assassins Creed Revelations - 3
• Batman Arkham City - 4
• Blazblue Calamity Trigger Limited Edition - 18
• Blazblue Continuum Shit Extend Limited Edition - 10
• Borderlands: The Pre-Sequel! - 4
• Bound by Flame - 6
• Call of Duty Back Ops - 4
• Call of Duty Ghosts - 4
• Castlevania Lords of Shadow 2 - 18
• Crysis 2 - 3
• Devil May Cry HD Collection - 10
• Dragon Age II - 4
• Dragon's Dogma Dark Arisen - 7
• Eat Lead - 12
• Fallout New Vegas - 5
• Fantastic Four Rise of the Silver Surfer - 9
• Far Cry 3 - 3
• Fracture - 7
• Full Auto 2 Battlelines - 4
• Ghost Recon Future Soldier - 3
• Hitman Absolution - 3
• Injustice God Among Us - 5
• Jurassic The Haunted - 20
• Killzone 3 - 4
• Kingdoms of Amalur Reckoning - 4
• Lucha Libre AAA: Heroes Del Ring - 15
• Madden 25 - 1
• Marvel vs Capcom 3: Fate of Two Worlds - 8
• Medal of Honor Limited Edition - 3
• Medieval Moves Deadmund's Quest - 3
• Middle Earth Shadow of Mordor - 4
• Playstation Move Heroes - 5
• Port Royale 3: Pirates & Merchants - 5
• Resident Evil 5 - 4
• Saints Row The Third - 4
• Sleeping Dogs - 4
• SOCOM 4: US Navy Seals - 3
• Sports Champions - 3
• The Darkness II - 5
• The Elder Scrolls V Skyrim - 3
• The Shoot - 7
• The Testament of Sherlock Holmes - 19
• Vanquish - 13
• Virtua Tennis 3 - 4
• Warhawk - 4
• Warriors: Legends of Troy - 19
• Yakuza 3 - 18

PS2

• Capcom Fighting Evolution - 15
• Choro Q - 15
• Extermination - 12
• Silpheed The Lost Planet - 19

PS1

• Batman & Robin - 32
• Bugs Bunny Lost in Time - 32
• Galaga Destination Earth - 9
• RC de Go - 45
• Star Wars Masters of Teras Kasi - 15
• Gundam Battle Assault 2 - 40
• Spider-Man - 40
• Granstream Saga - 30
• CTR Crash Team Racing - 15
• Samurai Shodown III: Blades of Blood - 30
• Spawn The Eternal - 35
• Tenchu 2 - 35
• Tenchu Stealth Assassins - 25
• Mega Man X4 - 25
• Mega Man X5 - 30
• Battlehunter - 20
• Shadow Madness - 20
• Fighting Force - 25
• Road Rash - 20
• Crash Bandicoot Warped - 15
• Spot Goes to Hollywood - 15
• Toca Championship Racing - 7
• Activision Classics - 7

SEGA Genesis Complete in box

• Combat Cars (cardboard variant-damaged) - 5
• Jeopardy! - 5 - 5
• Forgotten Worlds - 32 - 32
• Space Harrier II - 27 - 27
• T2 The Arcade Game - 18 - 18
• Zany Golf (cardboard variant-damaged) - 12 - 12
• Zombies Ate My Neighbors - 42 - 42

SEGA Genesis Boxed, no manuals

• Dynamite Headdy - 39 - 39
• Radical Rex - 44 - 44
• Road Rash II - 15 - 15
• Robocop 3 (water damage) - 15 - 15
• Space Harrier II - 18 - 18
• Starflight - 35 - 35
• The Revenge of Shinobi (Sega Classic) - 24 - 24
• Two Crude Dudes - 48 - 48
• Virtual Bart - 38 - 38
• WWF Royal Rumble - 8 - 8

Consoles, Accessories, Misc.

• Sega Saturn Console in box - 250
• Sega Saturn Arcade Stick complete in box - 55
• Donkey Kong Jungle Beat Congos (boxed, no game) - 70
• Nintendo 64 12-Cart Organizer Drawers (x3) - 40 ea.
• Nintendo 64 Console box only - 70
• Nintendo Virtual Boy in box - 450

• Please comment below if you'd like photos. Offers welcome.
• Accepting PayPal G/S. Shipping cost separate (CONUS).

Thanks for looking!

I am currently located in saudi Arabia and i wanna make a website for a friend in UAE
He wants the payment to be from saudi arabia and emirates for now
Can i add more than one payment method?
In the picture attached are the payment options provided in the UAE
Which one should i chose to make cross-boarder payment possible?

So at the start of my shift we go cashless of the register and at that point, until basically the time I'm clocking out, the only transactions we use the register for are EBT purchases. No cash, no cashback, no lotto, nothing. All cash and card purchases during the night must go through our self checkout, even alcohol and tobacco.
Well we just finished our seasonal store reset and got all of our new deals and sales posted up everywhere. Problem is, our SCO still sometimes rings up last season's sales on a few items. Or better yet, our clearance bins where the prices have been marked down manually usually pricing stickers. Now our SCO is a nice piece of tech but it does not give me the power to go into the system and edit the prices of things.
I know. I've looked.
And management watches how much we use the POS and for what purpose, but not the "why" of it, so if they see me ringing people up, overriding prices, and ignoring corporate policy...
Well my job's not worth that.
So yeah, I have to explain that I can't use the register to someone what feels like half a dozen times a night since May started. FML

Here is a guide on how to fight and defeat Germany and the USSR with Poland, using the left sanation path. But first, why would you want to do this?

• If you play as Poland on historical and don’t give up the east or Danzig, it is you plus the allies against the Axis and the Comintern. Also, you are pretty isolated from the allies. This is an incredibly challenging scenario, and one that I personally find very fun.
• Second, the Sanation left path is very underappreciated that needs some appreciation! In my opinion, this is *kind of* Poland’s strongest path. There are plenty of paths for Poland that are stronger after the war - the Slavic Union comes to mind. But you don’t need to be strong *after* the war, you need to get strong *before* the war, and this is where Sanation left excels.
• LARP lol. Defeating both the Nazis and the Soviets as Democratic Poland?? That is cool as hell.

What makes the Sanation left path strong? Polish militarism + right wing paramilitarism = +4.5% recruitable pop. You will have more manpower than you will ever need with this path - far more than the cores from monarchist paths can give you before the war. Second, common organization of society gives +10% factory output. Third, Walery Slawek as both a leader and advisor is +20% stability. Nothing to turn up your nose at. Fourth, you only spend the equivalent of 6 focuses on your political path to get all of its benefits, giving you more time to use on Poland’s excellent industrial branch.
Ok! So now onto the guide.
Intelligence Agency
You’ll want an intelligence agency as Poland that has Psychological Warfare, and army department. This is used for two important tasks.

• As early as possible, you want to start boosting ideology in Hungary. Hungary gets the “strengthen fascists” spirit, giving them +0.03 daily fascism support until Dec 6 1938. If you can stop them from getting more than 40% fascist support, they can never renounce the treaty of trianon and join Germany. But Germany still gives them carpathian ruthenia. So you can use Hungarian neutrality to block troops moving from the USSR-Romania side to the Germany-Italy side, and this makes a huge difference in making the war manageable.
• Secondly, use spies (probably after dec 6 1938) to infiltrate the German army. This will help you see where their troops are behind the front lines, which will be important to our military strategy.

Army Setup Before the War
You want 6 armies of 18 width infantry, with engineers, artillery, and anti-air support companies. Remember to train them to regulars - this makes a huge difference in their combat effectiveness! You also really want the 1939 engineer technology for the +50% entrenchment. This, plus grand battleplan, will make it so you can hardly be pushed.
2 armies go on the main German boarder, between Slovakia and the Baltic coast. 1 army goes on the Konigsburg pocket border. 1 army goes on the Slovakian border. 2 armies can be held in reserve around the capital to provide additional support where needed and plug gaps, and they will go to the USSR to latvia border a few months befure the USSSR declares war.
So you will need to produce: lots of guns, support equipment, anti-air, artillery, trains, and trucks, before the war.
After the war starts, you will want to focus on winning the air war. Swap to producing fighters (as many as it takes), getting 200 transport planes, getting an army of 10w paratroopers with support artillery, and getting an army of 10w port guards with support artillery to stop soviet navel invasions
Technology and Doctrines
Focus on industrial tech, of course. Here are the strategically important technologies for our strategy

• Fighters. You want Improved Small Airframe as fast as possible, and you want to make sure that the moment you unlock it you already have survivability studies, heavy MG, range improvements, and engines 3.
• Radar. Make sure your radar is at least up to date, and ideally ahead of time! Coordination helps on the defence a fair bit, but more importantly, radar helps you win the air war in a huge way, and having overlapping radar helps you see where your enemies are behind the front line. This is very very helpful for paradropping. I like to have maxed out radar stations in Warszawa, and Plock.
• Paratroopers. You really only just need the first paratrooper tech. But don’t forget it!
• Grand Battleplan. Go for infiltration. The main reason we want grand battleplan is for the entrenchment. You need that early in the war. Once you survive Germany and the USSR banging their heads against your trenches for a while, you have won. Superior firepower, in my opinion in this scenario, will help you ‘win more’ if you would have already won, but Grand Battleplan helps you *not lose* on the day Germany declares war, which is the most important day of the playthrough.
• Paratrooper Special Forces Doctrine - Combat Insertion. This is critical to the strategy - make sure you have 100 air XP saved up to get the first two doctrines in this special forces doctrine before you win the air war.
• Operational Integrity - The best doctrine for fighters, and you will be focusing hard on fighters.

Political Power Priorities
You will need political power to crush resistance in Danzig, so save up initially for that. Aside from that I would prioritize as follows:

1. Partial Mobilization
2. Limited Conscription
3. Defence expert army chief (start building that XP early!)
4. Air reformer airforce chief (you need air XP for those paratroopers!)
5. Improved working conditions. Get that stability! Using this earlier hurts less than using it later.
6. Illusive Gentleman! You need to keep Hungary from going Fascist!
7. Wallery the political advisor for +10% stability.
8. The Leftist Legionary. Extra democracy support is nice, and +15% attack and defence for paratroopers will come in handy when you start going on the offensive.
9. PKP industrial concern. +15% industrial research is nice!
10. Infantry expert & air superiority expert. You don’t need these before the war, of course.

NOTE: Make sure that you have enough political power saved up for the start of the war! You want to instantly switch to total mobilization, and activate women in the workforce). Activating extensive conscription is nice but there is no need to do it instantly.
NOTE: Get a military theorist before you start buying land doctrines, but remember that you don’t need them before the start of the war, so put off the military theorist as long as possible and just bank the xp.
Focus Order Phase 1: Danzig & Agrarian Reforms
(the first number in brackets is whether it is a 35 day focus (0.5) or a 70 day focus (1), the second number is the total number of 70 day focuses done to that point)

1. Clamp down on Danzig (0.5-0.5)
2. The Four Year Plan (0.5-1)
3. Central Region Strategy (0.5-1.5)
4. New Polish Industry (0.5-2)
5. Ban the Nazi Party (0.5-2.5)
6. Integrate Gdansk (1-3.5)
7. Invest in the Old Polish Region (0.5-4)
8. Fill the Railway Gaps (1-5)
9. Agrarian Reform (1-6)

Note: After you clamp down on Danzig, switch your garrison law to “local police force”, make sure you prioritize equipment and manpower to garrisons, switch your garrison template to the horse one, and then delete all your starting cavalry divisions to make sure there is enough equipment for the garrisons. Then, spend political power on “unification propaganda”, and unpause. Right before you are ready to ban the nazi party, take the “raid nazi resistance” decision. This should ensure that you have enough compliance on time, and that the focus will not cancel when you are half way through it (which otherwise can happen and is very annoying)
These focuses give you all of Danzig’s factories, 3 civs and 4 mills, gets you off embargoed economy, and takes care of the peasant’s strike just in the nick of time.
Focus Order Phase 2: Industrial Development

1. Expand the university of warsaw (1-7)
2. Invest in eastern poland (1-8)
3. Modernize congressional factories (1-9)
4. Expand Krakow industries (1-10)
5. Modernize Galician industry (1-11)
6. National Defence fund (1-12)

These focuses give you an extra research slot at a time when you will need it, 8 civs and 5 mils, and a big improvement to partial mobilization through the -35% consumer goods factor that will last two years. This also gives you just enough time to do your political branches before the German invasion.
Focus Order Phase 3: Political Tree

1. Complete the april constitution (1-13)
2. Polish Militarism (0.5-13.5)
3. Consolidate the Sanation Government (0.5-14)
4. The Sanation Left (0.5-14.5)
5. The Sanation Right (0.5-15)
6. Support Right-Wing Paramilitarism (0.5-15.5)
7. Department of Home Defence (0.5-16)
8. The Left Chairman (1-17)
9. Common Organization of Society (0.5-17.5)
10. A New King in the Castle (0.5-18)
11. Prepare for the Next War (0.5-18.5)

This gets you all the benefits of the sanation path, including the massive boost to recruitable population and a lot of stability. You also get the equivalent of 170 military experience.
Military Strategy when Germany Invades

• Keep the air contested and try to win the air war with the Nazis. They will bang their heads against your position, and that’s great. If you've followed this guide and you actively manage your defence (moving adjacent troops to reinforce weak tiles under attack) they shouldn't be able to push you a single tile.
• In my experience, the germans (and eventually Italians) are so busy trying to overcome your defence that they aren’t able to make it through Belgium to capitulate france. This is a huge win.
• The first thing you should do, when you are ready to advance, is to close the Konigsburg pocket. Ideally, try your best to do that before the soviets invade. Try to push here even in yellow air, using the huge planning bonuses from grand battle plan doctrine. It may be costly, but it is necessary.
• When you close the Konigsburg pocket, send that army to the border with Lithuania so that you won’t get a nasty surprise when the soviets annex them. If you like, set them up with an order to advance to Riga and execute it, so that they rush in when the Soviets annex lithuania.
• Try to build up level 2 forts on the entirety of the border with the Soviets. You will be taking focuses that upgrade these fort levels, so getting them to level 2 before these focuses fire off will help immensely. These forts allow you to basically ignore the soviets until the Germans are defeated.

How to take land from Germany:

• After you can get green Air, put out your transport planes and get ready for some paradrops. Find opportunities for paradrop-encirclements. Start by looking at the baltic coast: find a weak tile, and while paused order your adjacent units to attack it, and order a paradrop on that tile to help it break.
• Don’t forget to attack adjacent tiles if they are trying to reinforce the weak one, to slow down their reinforcement.
• When it looks like your units are about to win the battle, pause the game because it is time to order a lot more paradrops. You want to order a single unit to drop on a continuous stretch of tiles between the breech you are about to create and the baltic coast.
• Then order some redundant paradrops on tiles next to your line of tiles, just in case any of them are secretly occupied. It will take time for your paratroopers to lose, and if any of the adjacent tiles are occupied by you, the unit will retreat there instead of being deleted, so make sure that even if the encounter resistance, they will have a title to retreat into!
• Feel free to leave ports inside of the encirclement. Thanks to the royal navy, those ports won’t be of much use in getting supply to the enemy. But you can also, sometimes, feel comfy paradropping on ports that seem lightly guarded, as long as you paradrop many adjacent tiles as well to further de-org the port and ensure that even if you lose your paratroopers have somewhere to retreat to.
• Then, unpause, and watch the chaos. Order your regular units to attack the pocket. Manually order around your dropped paratroopers to hog as many tiles as possible before the enemy is able to reorganize itself.
• Eventually the lines will re-solidify (but with many encircled units destroyed) and you can repeat the paradrop on a new weak spot. I would focus on advancing along the baltic coast. It is easier here thanks to the royal navy, robs germany of important industry, is much nicer than trying to go through the Sudaten forts, and when you do link up with the French/UK lines, you will be in great shape (though don’t expect to do this before the soviets invade).
• I find that by the time that take the baltic coast and link up with France, Germany is so weakened that you can just mass paradrop on their victory points to capitulate them. But it is a very risky maneuver.

Focus order Phase 5: Preparing for the Soviet Invasion

1. Central Defence of Poland (1- 19.5)
2. Plan East (1-20.5)
3. Fortify Ukraine (1-21.5)
4. Fortification of the North (1-22.5)
5. (After this: whatever. Consider ‘local western plans’, polish school of mathematics, air production)

Make sure that before you get ‘fortify ukraine’, you have completed level 2 forts in the entire affected area. Same goes for the fortification of the north focus. Central defence + plan east should speed up your construction by 55%.
Military Strategy When the Soviets Invade
Hopefully when the soviets invade, you have level 3 forts along the whole border. This should make it easy to hold with 2 armies.

• Don’t be caught off guard by Romania invading! Make sure to send a few divisions with a fallback line by the Romanian border, and ensure that the rail network is good enough that division there won’t starve.
• Don’t be caught off guard by the soviets suddenly annexing Lithuania! Gets some kind of army there before they do - ideally the army that took down the Konigsburg pocket.
• Don’t be caught off guard by soviet naval invasions! They will straight up invade places as far afield as Stettin if you don’t guard your ports! Use an army of 10w infantry with artillery - that should be good enough.
• I would not try to advance against the Soviets until Germany and Italy have capitulated. Make good use of those level 3 forts.
• After the axis capitulates, try to make big encirclements, but it won’t be as effective on them as it was on Germany. You can also use paratroopers to capture and camp out along the railway lines. Paratroopers can act like ultra-fast motorized divisions, instantly exploiting a gap in the line to rush forward and capture supply hubs. Make sure to keep building airports and radar stations as you advance.
• It will be slow, but by the time the axis capitulates victory is certain.

Ok! I hope you enjoyed the guide! Now get out there, and help Poland save the world from tyranny!

Since there was an acute lack of info on the mech branch, I am starting this post as a standard guide for those exploring. I invite all mech singlite and dualite juniors and seniors to contribute through replies or dm me if you wish to add anything to this post.
The mechanical department as compared to that of other Indian unis is great. The professors are quite approachable and helpful and you can work under them on projects through a facility known as project type courses. Through research interests you will see that there is a focus on energy sector and especially thermal engineering in the faculty, but there are also professors working on electric/fuel cell vehicles, battery systems, MEMS. Structural research faculty is also quite experienced but their projects are mostly geared towards masters students. One big downfall though is a lack of research in fields like robotics (only 3 professors I know somewhat work on these) and aerospace, however that is the case for even the leading IITs. As an undergrad you can also take masters level courses on CFD, FEM, etc. the professors for which are quite good teachers and could allow you to opt for specialized jobs.
All of this was for core, but a alot of students go for product, finance, and software roles. You have plenty of time to explore this in mech as compared to phoenix branches, there are less evaluatives and in my experience, since the professors are less of pricks as compared to departments like EEE, checking in some of the courses is lenient
PS1 companies are genuinely improving year on year and really good orgs participated this year - ISRO, BARC, DRDO as well as Royal Enfield, Tata, Siemens, IOCL, etc. Juniors can expand this list below in replies. Your exact company will be alloted based on your CGPA, however for core, this is a great (and in most cases fun) learning experience as well as an early profile booster.
For 3rd Year SI you are ineligible for many if not most of the, software/finance companies, but here is a non exhaustive list of companies off that top of my head that you can go for through campus placements with CGPA cutoff varying from 6 to 8 -

1. Software - Goldman Sachs, De Shaw, Uber, Capital One, DMI Finance, PayPal, Accenture, IBM, Simpl, Concentric, Infoedge, Expedia (1-2L/month)
2. Quants - Tower Research, Trexquant, Millenium Management (5-30L/month however only 3-5 people get these and CS people preferred)
3. Finance - DMI Finance, Goldman Sachs, Axis Bank, HDFC Bank (Rs. 50k-1.8L/month)
4. Consulting - BCG, KPMG, Mckinley Rice, ZS Associates, KBR (Rs. 40k to 1.5L)
5. Core - Bajaj, ExxonMobil, Reliance, Tata, Lenskart, Pidilite, JSW, SLB, Jindal (Rs. 25-50k/month)
6. Supply Chain/Product - HUL, P&G, ABInBev (Rs. 1.5-2.5L/month)

Keep in mind that out of the entire batch across all departments (1000 students roughly) only 10-15% get an on-campus SI (atleast in the current market conditions). Other than that, people have bagged research internships in various prestigious universities through off campus applications and cold mailing.
As for placements, I will leave it to my seniors to answer this question. People are getting placed in software, product and core roles with standard packages (some that I know have got 11-18L/annum for core, 10-25L/annum in software and consulting, 30L in SLB, around 25 to 30L in HUL/P&G/Product/Supply chain) but right now there is a heavy downturn in the placement rates. Seniors have also been accepted into prestigious core MS programs in Stanford, Cornell, Carnegie, TUM, NUS, etc.
Clubs and Teams :-

1. CRISS robotics - Was quite active last year and won 1st prize in IRDC and a top 5 finish in International Rover Challenge.
2. Inspired Karters Gravity - Won no. 1 management award (the BITS special lol) in NASA HERC. But current people are actively trying to build a car despite various constraints for either BAJA or Formula Bharat.
3. Team BITS - As good as dead.
4. Team Anant - Participated in CANSAT this year. Quite active and receives lot of funding as well.
5. Inspired Karters Electric - Actively trying to build a car as well but deficiency of active members.
6. Renewable Energy Club- Lite, not sure what they do nowadays.
7. ISHRAE - Works with the professors and has taken on a few projects in HVAC sector. Though only few people in it are actively working.
8. Team Robocon - dead
9. Radio Control club - Conduct drone racing events and workshops in APOGEE but no major undertaking atm.
10. IGCSM - Sustainable manufacturing research partnership between BITS Pilani and TU Braunschweig. Led by Prof. Sangwan of Mech dept. Conduct 1-2 exchange events every year wherein a team of students from TUB visit the campus and vice versa.

Facilities: 1. Thermal Science Lab - the main lab where almost all core course lab sessions are conducted. Has various refrigeration rigs, heat transfer experimental setups, fluid mechanics experiments, standard pumps and turbines,etc. 2. ICE lab - IC Engines lab. Totally outdated with few engines and an air compressor. Requires a complete overhaul 3. New workshop - Decently stacked. Has all the facilities including different types of welding setups, cnc and manual mills, 3d printers (fdm and sla), lathes, furnaces, etc. Though the staff here are stingy when approached with by teams like IKE/IKRG for help. 4. Materials Testing Lab - was under renovation and is getting new equipment. Previously held tensile, hardness testing machines and some other stuff. 5. There are other funded labs for research scholars like the Smart Building Lab and for faculty led teams IGCSM.
If you aren't getting into circuital in top 10 IITs or mech in top 7 IITs, then I would say this is the best option there is.

A delicate, novel, and wonderful bread roll from BBL Foods is the best breakfast for a single person. Right when we take a gander at a tremendous roll, age is insignificant. Beginning with one side of the planet then onto the going with, relish bread rolls have a huge relationship with people, taking into account everything. As a result of their psyche blowing utility, rolls have earned an additional college education of appeal.
Have we at whatever point genuinely analysed the party setup, cost, and different central fixations as we run the bread shop? not a small dab of all time. To wrap things up, the sort of the flour retells a grand story as you would incline in the direction of buds.
Spread and sugar would be the significant embellishments in any party of bread moves that a Biscuit Machine manufacturer would make. Anyway, the moving scene will work with different parts, such as baking norms and consistency; This is another world, in all honesty. We ought to be prepared to consume cash on a variety of making due, fortifying, baking, and other giant stuff.
There are different Biscuit Machine manufacturer beginning with one side of the world then onto the following. As a maker, your decision is a standard-sized moving unit. A potential roll-creation contraption is the going with decision. The party in a brief time frame has a technique for really focusing in on another mechanical party that uses manual design and tangled improvement.
There are eminent bread roll machines, some of which have amassed such a gigantic client base that family stamps should coordinate additional investigation on them. Genuinely, how precisely are treats shown on a roll's full side?
Decisively when the cost of ownership, reasonable size and cutoff, locale and taste of tenants of the took out progress, future and straightforwardness of parts, machines in conveying its life of lodgings as such mix many layers head for see a shocking bread roll arise are considered, it is clearly a sharp cycle.
The basic fixing in your bread that sticks and rules the market is a splendid fixing! Suitably, the blenders, bowls, and blending decisions that the visionary worked with made specialists who work for every association utilise more principal refreshes.
A Biscuit Machine manufacturer should be splendid at everything, near he should be especially famous at things that help him with dealing with his business. By offering a particularly wide get-together of things, they further encourage business errands for producers. No matter what a demand of method plates for making sensitive or hard bread rolls, they offer a safeguarded and sensible player blender.
To guarantee a smooth change, they even stock things without issue. Rotational models can be used to back up decisions by the Bread roll Machine producer. Biscuit Machine manufacturer. Your bread rolls are cut up into their most gigantic parts and perspectives with a turning shaper. The rolls are warmed on an imported burner and turned into solid areas for grilling with a steel baking chamber. The bread rolls were gathered dependably and staggeringly using an unidentified power transport. To go as the crown, the wire-cut treats machine has been completely overhauled. It has different spouts and a moulded screen that can be gotten to by any quick client.
BBL Foods is correct now at the front of the movement of cutting edge moving stuff for the Indian market. They are acquired by using show technique and reasoning plans made for the approach of five-star utilitarian contraptions that have been reestablished to their fantastic structures. These gadgets are made to be utilised continually.
For more details visit our website: Biscuit Machine manufacturer
BBL Foods Private Limited
Contact: 98480 50607
Address: Santosh Nagar 'X' Road,Hyderabad - 500 059,Telangana State, India.
Facebook: https://www.facebook.com/bblfoodsofficial/
Instagram: https://www.instagram.com/bblfoodsofficial/

Context

• my company has decided to adopt events driven architecture and there is a need for analytics, we are currently on DMS + Redshift.
• the implementation of an events lake is brand new to everyone, there is basically no previous experience with implementing this on AWS, everything we have found is from google / reading.
• This is early days, so getting the right collaboration in terms of payload design and ingestion with the producers is in the works.

Technical setup

• There are 5+ streams of data ( Architectural units for those that are familiar)
• each of these streams generate 10+ event types, each with a distinct schema (asyncAPI speced)
• all of this goes into a centralized data store (s3) in the raw format via kinesis, from there, there is some filtering during s3 replication
• the filtered events end up in the analytics_raw bucket in thier raw format(parquet).

Events setup

• each event has an metadata envelope,and then the actual payload within an object, so there is always at least 1 nested object.
• the payload design principles are such that deep nesting / listing should be avoided, and for now, we will be rejecting all events that are nested 2+ or have lists. ( we are planning to send them to a specific bucket for processing and feedback.)

Goal

• take all events that come into the analytics_raw and turn them into iceberg tables
  • the idea is to do a 1 hour micro-batch / batch processing on all new arrivals (incrementally using either paritions or bookmarks.)
• register all this to the glue data catalog, and allow schema evolution, and alert when it would fail.
• Ideally, if a new folder is created (new stream), it should be automatically added to the workflow.

with that, here is where I am asking for help .

1. The glue job takes in a source bucket, and uses it for dynamicFrame creation.. if I have 1 bucket with 5 streams each with 10 event-types, each with it's own schema, would I need 50 jobs? This feels very wrong, and given that you can call glue jobs with arguments, my assumption is that you have 1 job that gets different arguments, likely called from lambda / glue workflows?
2. the visual glue ETL does allow for the creation of the glue data catalog iceberg table, but one of the caveats is that schema evolution is not supported in that way, meaning I will likely have to resort to custom scripting with write_dynamic_frame_from_catalog (https://docs.aws.amazon.com/glue/latest/dg/update-from-job.html). The question becomes in the case of non-compatible schema evolution, will this fail, or can I have control over this ?
3. Is the crawler => glue catalog actually the right way to do this ? the events always have at least 1 nested object, and i'm concerned about the crawler playing nice with this.. not to mention I have a defined asyncAPI spec, so inferring a schema when I have a spec sheet seems wrong, but creating an data catalog iceberg from a stream schema registry schema is not possible at this time it seems.
4. Just reading through the various items, alot of the iceberg stuff seems very manual in that the the table and the schema is created manually in athena SQL, and then populated.. is this the way that it should be done? I was under the impression that having a more dynamic and self-creating + reporting architecture will make things much easier in the long run.

If anyone has any experience with any of this, any advice would be greatly appreciated.

TL;DR: TL;DR: USD+ is a fully collateralized stablecoin pegged to USDC with the collateral being deployed across a portfolio of low-risk yield-farming strategies. Yield-farming strategies generate daily yield, which is passed over to USD+ holders daily, yields follow you wherever you go — be it your wallet, LP, or any other DeFi strategy.. The collateralization with reputable stablecoins aspect allows USD+ to solidify its strong peg against USDC.
Join OvernightFinance for news about what we are up to!

The need for a more Robust Stablecoin

Stablecoins have gained prominence within DeFi and allow users to take advantage of the best of both worlds that they offer: the stability of fiat currencies and blockchain technology.
However, stablecoins aren’t robust and lack a consistent peg. This is mostly fuelled because of them lacking an appropriate collateralization aspect. Even if such a narrative exists, they often lack the rails to convert the corresponding stablecoin to another currency to facilitate arbitrages in an attempt to restore the peg.
Moreover, for a user to earn yields on their stablecoins, they have to devote time, and effort and possess the necessary knowledge of DeFi which can prove a hassle for the novice DeFi user. Not utilizing them for Yield-Farming proves to be Capital Efficient within DeFi.

How USD+ makes Stablecoins More Robust

The scenarios mentioned above are detrimental to the health of such stablecoins and hence most are lacking an established framework/proven model.
On the other hand, this gap is bridged by the USD+ stablecoin that allows users to earn passive income on top of establishing a secure collateralization narrative. The stablecoin is pegged to USDC and always redeemable for the collateral amount (1 USD+ being equal to 1 USDC). To make it more capital efficient, the collateral is deployed across a spectrum of Stable-to-Stable Pools that generate rewards. These rewards are then passed onto holders on a daily via rebase mechanism.

Where do the Yields from USD+ come from?

The yields for USD+ come from the collateral deployed across a spectrum of stable-to-stable pools. The protocol employs unparalleled transparency with complete on-chain activities — users can see the strategies and collateral on Overnight’s dApp.
The Yield-Farming strategies are risk-averse and adopt a diversified approach — safety is prioritized over exorbitant APYs. Similarly, the collateral is limited to prominent, collateralized stablecoins the likes of USDC, USDT & DAI.
A user can invest in the strategies employed by the protocol themselves according to the respective proportions and earn the same APYs assuming that they auto compound daily — though this may prove to be a hassle for some.
The entire process is organic with there being no native inflation/emissions of any sort — the yields are what the rewards are. This means that the yields are proportionate to the rewards earned from the Yield-Strategies, any changes in rewards earned correspondingly affect the APYs earnt. All of this is done while maintaining USD+ as a stable asset that can be minted/redeemed upon demand.

USD+ Advantages

The mechanism mentioned above makes USD+ highly capital efficient and has been generating 8–12% APY as of currently. Compare this with USDC where holding it yields no profit payouts and a user has to partake in the Yield-Farming part themselves; in doing so, they go through the following:

• Possess knowledge of DeFi protocols and handling funds across numerous protocols
• Optimize their returns via compounding (daily & manually)
• Bear exorbitant transaction fees

On the other hand, with USD+ all that hassle is reduced to something as simple as buying a token. In other words, managing stablecoin cash is risky, cumbersome, and costly — this amounts to the stablecoin being:

• A DeFi equivalent of a Money Market fund, with a highly conservative and liquid [DeFi] portfolio
• A fully decentralized protocol performing all of its activities fully on-chain with an unparalleled level of disclosure and transparency
• Your ultimate hedge against inflation
• A readily source of passive incom
• An appreciating collateral
• Hedge against market volatility
• Generating additional yields in Liquidity Provisions

How the Protocol Maintains a Risk-Averse Approach

The Overnight protocol strives to maintain itself as risk-averse and in doing so, uses the following mechanisms.

1. Only Secure Stablecoins are used: like USDC, USDT, and DAI.
2. Funds are deployed on DEXes after a thorough due-diligence process — this involves analyzing the smart contracts.
3. Strategies are tested on devstand to ensure that the yields are what they’re advertised as.
4. The Overnight Protocol is audited by Hacken with more audits to continue as development is continued.

How it works

As said previously, yields from USD+ accrue on a daily horizon and give you an auto-compounded effect whereby you earn yields on top of yields — your USD+ balance grows daily.
The rebase mechanism is triggered manually by the protocol and the entire process happens seamlessly within 6 steps that are as follows:

1. User uses USDC or BUSD to mint USD+ via Overnight’s dApp — BUSD is only applicable for minting USD+ on BSC
2. Overnight’s Smart Contracts devise a logic-automated investment methodology for Yield-Generating Strategies
3. The fees & rewards from step 2 (including inflationary rewards, swap fees, and lending fees earned) are swapped for USDC
4. New USD+ is minted from the earned USDC
5. The minted USD+ goes back into your wallet via a rebase mechanism

What is a Rebase and how does it work?

A rebase mechanism is used to payout the yields earned from strategies. In doing so, the circulating supply expands and is financed by the USDC earned from the Yield-Farming strategies. The mechanism is similar to what’s employed by IB-Tokens (Interest Bearing) the likes of aUSDC from AAVE where your underlying token quantities grow passively proportionate to the lending fees earned.
Smart contracts use the following methodology to determine a user’s rebase rewards:
Rebase Rewards = User Holdings\Rebase Amount / Total Holdings = Rebase for the user for the said day*

The Team behind Overnight

The team behind Overnight is fully doxxed and can be viewed on the website. The team possesses an extensive background involving institutions the likes of Morgan Stanley, BCG, Google, etc.

Use cases for USD+

Since users’ balance of USD+ keeps increasing over time, there lies a unique proposition that protocols, fiat investors, and the crypto community could tap into.

Provide liquidity — AMM

• Liquidity providers can earn both transaction fees from DEX and interest from USD+ by supplying USD+ liquidity.
• An Automated Market Maker (AMM) utilizes USD+ in Liquidity Pools to boost yields for Yield-Farmers (e.g, USD+/USDC, USD+/WETH, trading pairs) as it starts receiving yields on USD+ posted by liquidity providers

Lending

• USD+ can serve as collateral in lending protocols. Users can continue to earn USD+ interest while using it as collateral and therefore serves as appreciating collateral improving their HF.
• For borrowers using USD+ as collateral: Posting USD+ as collateral makes their position “healthier” overtime due to the yields earned
• For lenders: Earn lending fees in addition to USD+ yields — serves as maximizing your returns
• For USD+ borrowers: Receive the USD+ interest so the market interest model should consider this part.

Hedging against Market Volatility

• USD+ can be used to reduce market exposure while continuing to Yield-Farm via it as the strategy would earn considerably more if plain vanilla USDC were to be used. This strategy massively reduces ILs however, it does not negate them.
• A user deposits USD+ into Overnight’s Exchange-Traded-Strategies
• Logic-Automated smart contracts use a portion of the collateral to deposit USDC into AAVE
• MATIC is borrowed via an HF of 1.5x against the collateral
• MATIC is used to LP with the remaining USD+
• Smart contracts rebalance HF upon mints/redeems at least once a day and liquidate rewards
• Rewards are paid out back to users after accounting for the minimal IL

Crypto Community

• The Crypto-Community can utilize USD+ to put their idle assets to work and generate yields via it.
• A crypto-investor temporarily exits their ETH position and holds USD+ as a ‘risk-free yield generating alternative’ until their market view improves
• A new blockchain project raises [Х] m USD in cryptocurrency and stablecoins to fund its 2-year roadmap, and chooses to keep it in USD+ to minimize volatility while earning 8–12% APY from the stablecoin

Fiat-Investors

USD+ can be considered as an alternative to a money market fund but with utmost transparency and a higher-yielding source.

• An online broker, aka Robinhood, lets its clientele buy USD+ from its app as a high-yield alternative to the money market fund
• A Neobank, aka Revolut, builds a savings account, with the rate linked to USD+’s yield
• A qualified investor invests in a registered/regulated fund in a respectable jurisdiction, e.g. Switzerland, Singapore, or the Netherlands, that holds USD+

The above use cases are centered around yield generation. As USD+ is also a stablecoin, there is obviously a multitude of use cases around payments, be that P2P, B2C, or C2B, on-chain or across chains; as UDS+ is pegged to USDC, on-chain to off-chain use cases are also possible.

Closing Comments

USD+ is built owing to the need for enhanced capital efficiency within DeFi and simplifies the concept of Yield-Farming for the novice user — with USD+, this is as simple as buying a token. The use cases mentioned above are game-changers within the ecosystem.
Those interested in learning more about Overnight can reference the following links:
Protocol Docs: ​​https://docs.overnight.fi/
Landing Page: https://overnight.fi/
CoinMarketCap: ​​https://coinmarketcap.com/currencies/usd/
Upvote2Downvote0commentsShareUSD+ is a fully collateralized stablecoin pegged to USDC with the collateral being deployed across a portfolio of low-risk yield-farming strategies. Yield-farming strategies generate daily yield, which is passed over to USD+ holders daily, yields follow you wherever you go — be it your wallet, LP, or any other DeFi strategy.. The collateralization with reputable stablecoins aspect allows USD+ to solidify its strong peg against USDC.

The need for a more Robust Stablecoin

Stablecoins have gained prominence within DeFi and allow users to take advantage of the best of both worlds that they offer: the stability of fiat currencies and blockchain technology.
However, stablecoins aren’t robust and lack a consistent peg. This is mostly fuelled because of them lacking an appropriate collateralization aspect. Even if such a narrative exists, they often lack the rails to convert the corresponding stablecoin to another currency to facilitate arbitrages in an attempt to restore the peg.
Moreover, for a user to earn yields on their stablecoins, they have to devote time, and effort and possess the necessary knowledge of DeFi which can prove a hassle for the novice DeFi user. Not utilizing them for Yield-Farming proves to be Capital Efficient within DeFi.

How USD+ makes Stablecoins More Robust

The scenarios mentioned above are detrimental to the health of such stablecoins and hence most are lacking an established framework/proven model.
On the other hand, this gap is bridged by the USD+ stablecoin that allows users to earn passive income on top of establishing a secure collateralization narrative. The stablecoin is pegged to USDC and always redeemable for the collateral amount (1 USD+ being equal to 1 USDC). To make it more capital efficient, the collateral is deployed across a spectrum of Stable-to-Stable Pools that generate rewards. These rewards are then passed onto holders on a daily via rebase mechanism.

Where do the Yields from USD+ come from?

The yields for USD+ come from the collateral deployed across a spectrum of stable-to-stable pools. The protocol employs unparalleled transparency with complete on-chain activities — users can see the strategies and collateral on Overnight’s dApp.
The Yield-Farming strategies are risk-averse and adopt a diversified approach — safety is prioritized over exorbitant APYs. Similarly, the collateral is limited to prominent, collateralized stablecoins the likes of USDC, USDT & DAI.
A user can invest in the strategies employed by the protocol themselves according to the respective proportions and earn the same APYs assuming that they auto compound daily — though this may prove to be a hassle for some.
The entire process is organic with there being no native inflation/emissions of any sort — the yields are what the rewards are. This means that the yields are proportionate to the rewards earned from the Yield-Strategies, any changes in rewards earned correspondingly affect the APYs earnt. All of this is done while maintaining USD+ as a stable asset that can be minted/redeemed upon demand.

USD+ Advantages

The mechanism mentioned above makes USD+ highly capital efficient and has been generating 8–12% APY as of currently. Compare this with USDC where holding it yields no profit payouts and a user has to partake in the Yield-Farming part themselves; in doing so, they go through the following:

• Possess knowledge of DeFi protocols and handling funds across numerous protocols
• Optimize their returns via compounding (daily & manually)
• Bear exorbitant transaction fees

On the other hand, with USD+ all that hassle is reduced to something as simple as buying a token. In other words, managing stablecoin cash is risky, cumbersome, and costly — this amounts to the stablecoin being:

• A DeFi equivalent of a Money Market fund, with a highly conservative and liquid [DeFi] portfolio
• A fully decentralized protocol performing all of its activities fully on-chain with an unparalleled level of disclosure and transparency
• Your ultimate hedge against inflation
• A readily source of passive incom
• An appreciating collateral
• Hedge against market volatility
• Generating additional yields in Liquidity Provisions

How the Protocol Maintains a Risk-Averse Approach

The Overnight protocol strives to maintain itself as risk-averse and in doing so, uses the following mechanisms.

1. Only Secure Stablecoins are used: like USDC, USDT, and DAI.
2. Funds are deployed on DEXes after a thorough due-diligence process — this involves analyzing the smart contracts.
3. Strategies are tested on devstand to ensure that the yields are what they’re advertised as.
4. The Overnight Protocol is audited by Hacken with more audits to continue as development is continued.

How it works

As said previously, yields from USD+ accrue on a daily horizon and give you an auto-compounded effect whereby you earn yields on top of yields — your USD+ balance grows daily.
The rebase mechanism is triggered manually by the protocol and the entire process happens seamlessly within 6 steps that are as follows:

1. User uses USDC or BUSD to mint USD+ via Overnight’s dApp — BUSD is only applicable for minting USD+ on BSC
2. Overnight’s Smart Contracts devise a logic-automated investment methodology for Yield-Generating Strategies
3. The fees & rewards from step 2 (including inflationary rewards, swap fees, and lending fees earned) are swapped for USDC
4. New USD+ is minted from the earned USDC
5. The minted USD+ goes back into your wallet via a rebase mechanism

What is a Rebase and how does it work?

A rebase mechanism is used to payout the yields earned from strategies. In doing so, the circulating supply expands and is financed by the USDC earned from the Yield-Farming strategies. The mechanism is similar to what’s employed by IB-Tokens (Interest Bearing) the likes of aUSDC from AAVE where your underlying token quantities grow passively proportionate to the lending fees earned.
Smart contracts use the following methodology to determine a user’s rebase rewards:
Rebase Rewards = User Holdings\Rebase Amount / Total Holdings = Rebase for the user for the said day*

The Team behind Overnight

The team behind Overnight is fully doxxed and can be viewed on the website. The team possesses an extensive background involving institutions the likes of Morgan Stanley, BCG, Google, etc.

Use cases for USD+

Since users’ balance of USD+ keeps increasing over time, there lies a unique proposition that protocols, fiat investors, and the crypto community could tap into.

Provide liquidity — AMM

• Liquidity providers can earn both transaction fees from DEX and interest from USD+ by supplying USD+ liquidity.
• An Automated Market Maker (AMM) utilizes USD+ in Liquidity Pools to boost yields for Yield-Farmers (e.g, USD+/USDC, USD+/WETH, trading pairs) as it starts receiving yields on USD+ posted by liquidity providers

Lending

• USD+ can serve as collateral in lending protocols. Users can continue to earn USD+ interest while using it as collateral and therefore serves as appreciating collateral improving their HF.
• For borrowers using USD+ as collateral: Posting USD+ as collateral makes their position “healthier” overtime due to the yields earned
• For lenders: Earn lending fees in addition to USD+ yields — serves as maximizing your returns
• For USD+ borrowers: Receive the USD+ interest so the market interest model should consider this part.

Hedging against Market Volatility

• USD+ can be used to reduce market exposure while continuing to Yield-Farm via it as the strategy would earn considerably more if plain vanilla USDC were to be used. This strategy massively reduces ILs however, it does not negate them.
• A user deposits USD+ into Overnight’s Exchange-Traded-Strategies
• Logic-Automated smart contracts use a portion of the collateral to deposit USDC into AAVE
• MATIC is borrowed via an HF of 1.5x against the collateral
• MATIC is used to LP with the remaining USD+
• Smart contracts rebalance HF upon mints/redeems at least once a day and liquidate rewards
• Rewards are paid out back to users after accounting for the minimal IL

Crypto Community

• The Crypto-Community can utilize USD+ to put their idle assets to work and generate yields via it.
• A crypto-investor temporarily exits their ETH position and holds USD+ as a ‘risk-free yield generating alternative’ until their market view improves
• A new blockchain project raises [Х] m USD in cryptocurrency and stablecoins to fund its 2-year roadmap, and chooses to keep it in USD+ to minimize volatility while earning 8–12% APY from the stablecoin

Fiat-Investors

USD+ can be considered as an alternative to a money market fund but with utmost transparency and a higher-yielding source.

• An online broker, aka Robinhood, lets its clientele buy USD+ from its app as a high-yield alternative to the money market fund
• A Neobank, aka Revolut, builds a savings account, with the rate linked to USD+’s yield
• A qualified investor invests in a registered/regulated fund in a respectable jurisdiction, e.g. Switzerland, Singapore, or the Netherlands, that holds USD+

The above use cases are centered around yield generation. As USD+ is also a stablecoin, there is obviously a multitude of use cases around payments, be that P2P, B2C, or C2B, on-chain or across chains; as UDS+ is pegged to USDC, on-chain to off-chain use cases are also possible.

Closing Comments

USD+ is built owing to the need for enhanced capital efficiency within DeFi and simplifies the concept of Yield-Farming for the novice user — with USD+, this is as simple as buying a token. The use cases mentioned above are game-changers within the ecosystem.
Those interested in learning more about Overnight can reference the following links:
Protocol Docs: ​​https://docs.overnight.fi/
Landing Page: https://overnight.fi/
CoinMarketCap: ​​https://coinmarketcap.com/currencies/usd/

Playing By Ear
Bloodhound Saga
Wakeup Super
-
First Prev Next
-
Memory transcription subject: Wes Gidbrook, Human Refugee
Date [standardized human time]: November 4th, 2136
I just had to phrase it that way didn't I?
“I'll be back here soon as long as nothing crazy happens!”
I really went and set myself up for that one. How foolish of me to think that the insanity would end with the extermination fleet, or maybe with the people-eating crocs actually coming to our rescue. No, of course it couldn't end there. Going to another planet clearly wasn't enough to get away from the lunacy.
Actually, the news probably didn’t even register back on Earth. It’s only really world-shattering for everyone here. Guess I dodged into it.
It wasn’t really that shocking that some of these herbivorous species used to be omnivores. Hell, how many ‘prey’ species on Earth would chomp at a meaty morsel if they had the chance? The real irony was that the Krakotl were a part of that group, the very birds that led the extermination efforts because they thought we were ‘dangerous predators’. That wasn’t to mention the Gojid that jumped at the chance first.
And now there’s a hole in the wall of what was my apartment because aliens won’t leave us the hell alone.
Opinions around the shelter were mixed. Some folks couldn’t help but laugh at the absurdity of it, seeing the reveal like a cosmic joke. Others just seemed to just get more angry, knowing how pointless all of that death was.
The air about the place still reeked of sorrow and frustration. Even the laughter was only there to cope with the pain.
The worst part was that I couldn’t leave to escape it. We were advised to stay in the shelter until initial reactions to the broadcast blew over. The public was in a hell of an uproar, and adding Humans to the mix could be dangerous for both us and them. Tension was high enough as it was.
Of course, that policy seemed a bit inconsistent since Brad apparently got to hop across Venlil Prime however he wanted, but, then again, he was working on infrastructure. It was kind of important that he could actually do his job.
Maybe I should've gone into that field. Probably would've paid better than scrounging up music gigs.
I supposed that was one perk to being at the shelter. All the meals were paid for. They were all vegan, but hey, beggars can't be choosers.
Despite the freely provided rations, the atmosphere still left a lot to be desired. Luckily, a few days (or…paws) after the broadcast, the restrictions were finally lifted, and I was eager to get out of the bleak shelter and back to White Hill.
And so, that was my plan for the paw. Learning from last time, I made sure to send a message in the group chat announcing that I was on my way, though I was yet to hear back from anyone since I did.
It doesn’t matter. Even if they’re all busy, I’d still rather meander around campus alone than stew in the doom and gloom here.
The area around the shelter was devoid of locals as usual. I checked out at the front gate and started the walk to the train station, face hidden behind a mask. But, as I continued onward, I noticed that the quietness extended a lot further than it did before. Even as I approached the station, there weren’t nearly as many people as there were on the first trip to White Hill.
It’s…kinda eerie…
I assumed this was all still fallout from the broadcast. Within the shelter walls, the restrictions seemed like a bit of an overreaction, but I was beginning to realize just how much the public was affected. If they were still hunkered down this many paws after the fact, what were those first hours like?
I hope nobody got hurt. Those stampedes can apparently get pretty nasty.
Even when I entered the station, there was hardly anyone in the vicinity. Unlike my last trip, the wide berth around me felt natural. Most of the seats on the train were left unfilled as I boarded.
There was one Gojid in my car. They sat in the corner and kept their head down, trying to avoid interaction.
Not many people came aboard on the way to White Hill, and I slowly began to worry if maybe the atmosphere around the campus wasn't actually any better than the shelter. Everything felt so uneasy, like the few folks that left their homes regretted the fact they had.
I kept the volume on my earbuds low. Even with the subtle noises of the train, I was worried my music might be audible to the few others in the car. I caught enough suspicion without being judged for my ‘predatory’ song choices too. That, and I wanted to be a little more aware of my surroundings. It was hard to shake the sense of dread when everything was so…stagnant.
The White Hill campus wasn’t very active either. Classes weren’t starting up again for another couple of ‘paws’ according to the others in the group chat. The place was still in sleep mode by the looks of things. Still, there were signs of life here and there. It looked a bit more lively than the town around the shelter, so my outlook was a little more optimistic.
The people here seem to adjust quickly, first to Humans and now to the omnivore revelation. Looks like they’re already bouncing back.
My phone suddenly chimed, a welcome sound given the imposing silence. I fished the device from my pocket and unlocked it to reveal a message from Grace.

Grace: You should swing by Haeli’s place at the edge of campus! She’s cool with it, and it’d be nice to see another familiar human face.

Just below was an address which I quickly searched up directions for. It was on the opposite side of campus, but I actually welcomed the lengthy walk. After all, I was really just trying to spend as little time at the shelter as possible. I actually took a more roundabout way than I needed to, just to check out some of the areas I hadn’t seen yet. This time, I didn’t run into Kila or anyone else, so I could take whichever path I chose.
Of course, I didn’t want to keep Grace waiting too long, so once I saw what I wanted to, I picked up my pace a little bit.
[Fast-forward transcription: 20 minutes]
Haeli’s home wasn’t all that large. It was easy to see why she only offered to house her exchange partner. At least…I was pretty sure it was Haeli’s place. I had to translate the Venscript numbers on the side, so I hoped the references the UN gave us were correct.
Probably wouldn’t be good if I had the wrong house. An unsuspecting Venlil might die of fright if they opened the door and saw me.
Once I felt confident enough that I didn’t have the wrong house, I went ahead and knocked on the door. It didn’t take long for it to crack open, Grace’s unmasked face poking out from behind it. She gave a toothless smile as she saw me, and she motioned for me to enter.
“Good paw, Wes,” she greeted. “Please, come in.”
“How’d you know it was me?” I joked. “I’m wearing this mask to hide my ‘predatory visage’.”
That garnered a chuckle from the Brit.
“Ah, yes, how silly of me to assume your identity. It could have been any Human. There’s so many of us on Venlil Prime.”
“You jest, but there’s certainly a hell of a lot more than there was. Besides, isn’t White Hill a hotspot?”
“Maybe in the Human housing district,” she replied. “Most of those folks seem quite content to play it safe. They only really go where they need to. I suppose you’re the anomaly.”
I removed my mask as soon as the door closed, and we both took a seat on the couch in the quaint little living room. It seemed just a tad short for our builds, but not too much.
“That’s implying that I didn’t need to get out of that shelter,” I shook my head. “At least you seem to be keeping your chin up. The shelter just feels like it’s drowning in depression. I can’t really blame everyone, but being there is really taking a toll.”
“I’d imagine,” Grace sighed. “If not for Haeli, I’d probably still be hanging my head too. I’m still feeling the weight of it all; probably will for a good while. But she’s done her best to support me. I owe her the world.”
“Where is Haeli right now?” I scanned the room. “With how quiet campus is, I figured she’d be here.”
“Ah, she is,” Grace replied. “Right now she’s in her room recording a quick mini-lecture to post online. Just trying to make up for lost class time. She doesn’t particularly like teaching that way, but desperate times and such.”
I nodded and leaned back into the Ven-sized couch.
“You’ve been teaching lately too, right?”
“Indeed. To be honest, I’d never given piano lessons up until arriving here, but I needed some type of task to keep myself busy, something to cope with…everything. I’ve actually been enjoying it a lot! I kind of wish I’d taken a swing at it sooner, but better late than never I suppose.”
“Whatever keeps you moving. I’m still stuck on the ‘stewing in the darkness’ phase. Kila was able to hook me up with an amp for my bass, but it’s not like I really have much to do with it. Hard to lead a performance with just a bass.”
“Any other musicians over there to jam with?”
“Not that I’ve seen.”
Grace turned her eyes up in contemplation.
“Could try to get some little Venlil students to teach. Worked out for me.”
“Yeah, maybe…” I scratched the back of my head. “I think I’d prefer to just play with a band again, though. Besides, I don’t think the bass is going to draw a lot of prospective students. It’s not exactly the most stand-out instrument.”
“What if you taught the regular six-string?”
“For one thing, I’m pretty rusty with it. For another, I don’t even have one with me. Kila could probably make me one, but…I don’t know. In the past, when I gave lessons, it was usually because I was strapped for cash. Didn’t really leave a good taste in my mouth.”
“I hear you. Honestly, playing in a band might not be as far-fetched as you think. There’s so many students taking inspiration from Human music lately. I mean, I’ve stayed quite busy teaching the piano.”
“Bonti was learning the guitar from Janet, wasn’t he?” I recalled him sending a message about it. “Maybe I could convince him to join me for some jams.”
“Perhaps. I think his coursework is quite extensive, but he is rather ambitious.”
“I don’t suppose you’d like to join as well.”
Grace shook her head.
“No. I’m enjoying my new teaching endeavors, and they keep me plenty busy. You might be able to find some capable locals though. Actually, Lanyd has been a student of mine, so you might want to ask her. She’s a very fast learner. Her rate of improvement is unlike any I’ve ever seen before.”
“Really? I never saw her mention anything in the group chat.”
“Well…Lanyd rarely posts in the chat at all, so…”
That was true. The soft-spoken little Venlil wasn’t exactly much for conversation. At least, she wasn’t until someone prompted her to speak, usually Bonti.
“I suppose I could try to get her involved, though I’m not sure if she’s really built for that kind of casual group. She just seems so…formal?”
“Don’t underestimate her,” Grace warned. “She already underestimates herself, and, even then, she progresses so quickly. I assure you, Lanyd can be very adaptable.”
“I’ll make sure to talk to her when I get a chance.”
“That chance might come quite soon,” Haeli’s voice caught me a little off guard. As I whipped my head around in surprise, she flinched at the sudden motion.
“Sorry…I wasn’t thinking,” I quickly turned away. “Looking directly at people is like rule number one on the UN’s list of things not to do.”
“No…it’s fine,” she assured me. “I should really be over it by now. I’m living with a human for Stars’ sake. Grace, I fear that you’ve policed your habits too much. You shouldn’t have to go so easy on me.”
“I’m hardly going to try and make you uncomfortable in your own home, love,” Grace chuckled lightly. “You needn't overcome such deep-rooted fears so quickly. Now, what was that you were saying about Lanyd?”
“Ah, yes,” Haeli straightened herself. “Lanyd agreed to play in our new jazz lounge a couple paws from now. We’re hoping it might breathe a little life back into campus as classes resume.”
“Sounds like a good time,” I replied. “I don’t suppose you need a bass player as well?”
“I’m afraid not, Wes,” Haeli flicked her ears in a motion I assumed meant ‘no’. “I actually already have a student lined up for the performance. Though, if we end up with a gap to fill, you’ll be the first one I call.”
“So there is someone with a love for the low end around here. I’d like to see what this mystery bassist can do, so I’ll drop by for sure. You also said it’ll be a good opportunity to talk to Lanyd?”
“Indeed, though I’m a little wary of you stealing my musicians away! It wasn't easy to convince her to join!
“Oh…uh…”
“I'm just kidding!” she swayed her tail. “Personally, I think Lanyd would do well to gain some more practical experience. That's why I asked her to play. She’s so incredibly skilled, but still so green. It would be great if she joined you, though I’m not sure how easy it will be to recruit her. Lanyd's own doubts seem to be her worst enemy.”
“I got the same impression from the little I've spoken to her,” I agreed. “Still, I’ll see what I can do.”
Grace turned her attention to me.
“I’m a little surprised that you’re trying to form a group here. I assumed you’d want to be back to Earth as soon as possible, regardless of what happened to your apartment. Is there no one else back home to house you?”
“I could probably go back,” I admitted. “But, after everything, all my friends and family are already struggling through their own problems. I’d hate to impose on anyone when there's shelter already being provided here.”
“Fair enough,” she shrugged. “To be honest, I think there’s a lot of opportunities around here anyway. The locals are getting more curious about us, and it’s opening up new avenues for skills that we take for granted back on Earth.”
“Like your piano lessons?”
“Precisely. I agree that you shouldn’t be too eager to leave. It might be a little chancey with exterminators, fearful citizens, and such, but I think it might just be worth the risk.”
I suppose that makes sense. Kila's club has taken off as well. Human culture might take the area, or even the planet, by storm just by virtue of being new and exciting.
“Speaking of opportunities, how have your lessons actually been going?” I queried. “It sounds like you've been really successful.”
“It can be trying at times,” Grace sighed. “But it's very rewarding.”
She continued to recount her teaching experience as Haeli got us some tea. It was nice to have a more optimistic conversation after being stuck in the hell that was the shelter. Despite everything and everyone that Grace lost in the bombing, she was making the most of the opportunities in front of her.
I need to do the same thing. If I'm going to put a band together here on Venlil Prime, I need to do things right. Best get started right away. I can ask Bonti to be our guitarist, and Lanyd to be our keyboardist. Hopefully they agree, but I'll still need a drummer even then. Where's Mitch when you need him?
Admittedly, I fell in and out of attention as Grace and Haeli spoke. In my mind, I was churning through prospective options.
I'll just have to keep my eyes peeled. That’s all I can do…
-
Memory transcription subject: Linev, Venlil General Studies Student (First Term) White Hill University
Date [standardized human time]: November 4th, 2136
The knock on my door caught me off guard. Was it Indali? Most of the places around campus were only just opening up again. Certainly, she wasn’t about to drag me around to clubs already. Maybe it was Mezil?
The easiest way to solve the mystery was to open the door, so that’s what I did. To my surprise, it was neither Indali nor Mezil. Rather, it was Kila pushing a big box on a dolly.
“Kila?” I tilted my ears in confusion.
“Hey, Linev!” she beeped. “Say, you’re not busy are you? I should have sent you a message before I came here, but I got a bit ahead of myself.”
“I’m not busy, but…why are you here? How did you even know this is my room?”
She was pushing the dolly into my room before she bothered answering.
“Mezil told me where your room was. It’s a good thing you’re not busy. I really wanted to set this up in person.”
“Mezil’s just…giving away my room number?”
“Relax! He only told me, and I’m only going to pester you this once. I take it you already know what’s in this box.”
“I’m surprised you finished it so quickly,” I closed the door behind me as she shimmied the dolly out from under the package. “Given some of the other instrument lead times, I thought this would take longer.”
“Well, I kinda expedited it just a little,” Kila replied as she began to open the box. “We were already developing some sensors for another device, and the stars just aligned for it. I might’ve let you skip in line a bit, but what’s the point of running the club if I can’t move my friends forward in the queue?”
She gradually started unpacking bits of metal tubing, drum pads, and faux cymbals.
“I could’ve just come and picked it up, you know,” I sighed.
“Yes, but I wanted to make sure it was put together properly. That, and I want to see what a real percussionist can do with it.”
“I feel like Mezil has talked my skills up more than they deserve.”
“It doesn’t matter. Just come over here and I’ll show you how to assemble it.”
She walked me through each step of the drum kit’s construction, showing me how to fix the stands and where each connection needed to be made. Being electronic, it was a lot less bulky than a regular kit. It would fit better in my not-so-spacious dorm room that way, and it would also be easier to transport if and when I needed to.
“It’ll need to be connected to an app on your pad to actually function,” Kila informed me. “All each drum does is send signals that say how hard it’s been hit. The sound comes from a virtual instrument. Luckily, I already had some of the comp sci folks porting over keyboard sounds, so getting drum sounds was pretty easy. The app they made is still fairly new, but I think they’ve crunched most of the bugs already. If it starts freaking out, call them, not me!”
“Sounds good,” I replied as we finished the last bits of setup. “So, I suppose it’s ready for a test run.”
“Go for it,” she encouraged. “Let’s see if it holds up for a real musician.”
I sat myself down at the kit with a stick in each paw. I wasn’t sure if there was any particular grip Humans typically used, but I just went with what I was familiar with. The first test was a simple one. Drums needed to be hit, and to get more volume, I needed more force.
BOOMWHACKTHWACK
One by one, I hit each piece of the kit as hard as I could.
“STARS, LINEV!” Kila recoiled in shock. “Isn’t that a bit excessive?!”
“Very excessive,” I answered. “But it still held together. You really do make quality stuff, Kila.”
“Of course I do! That’s the whole point!”
Reigning in my intensity, I tapped out some light rhythms, causing sound to emanate from the virtual instrument on my pad. To get real volume, I’d need to feed that output through a speaker, but this was fine for testing.
I hit each drum with differing intensity, making sure the volume matched up. Gradually, I got a feel for the sticks and the foot pedal, and I began to delve into some more complex rhythms, weaving between the beats as tightly as I could. I put polyrhythms within polyrhythms, and the device proved itself responsive through each and every block.
Tight…
“Is it up to your standards?” Kila asked with an expectant sway of her tail.
I looked over the kit, feeling the comfortable weight of the sticks in my paws.
“Hell yeah.”
-
First Prev Next