Hmmmm, this seems very wrong

2024.11.26 12:30 Entityperson0085 Hmmmm, this seems very wrong

submitted by Entityperson0085 to MandJTV [link] [comments]

2024.11.26 12:30 XT2020-02 GRIII | Foggy evening

GRIII | Foggy evening submitted by XT2020-02 to ricohGR [link] [comments]

2024.11.26 12:30 Waste_Diet_5394 Australian TRS Claim

Hi there, what is your experience on claiming Tourist Refund Scheme at Melbourne Airport?Were you checked on the flight back in?
submitted by Waste_Diet_5394 to AskAnAustralian [link] [comments]

2024.11.26 12:30 Sad-Sea-1824 Why do wilds monsters dont feel like mh monsters

Why do wilds monsters dont feel like mh monsters People are gonna kill me for this quit. It has to be said none of the monsters actually nearly none of the monsters feel like something you find in monster Hunter I feel like something you would find in different games.
submitted by Sad-Sea-1824 to MonsterHunter [link] [comments]

2024.11.26 12:30 Behindstef84 Nein, er war das Opfer. Das Gericht in Virginia hat sie zur Geldstrafe verurteilt aufgrund von Diffamierung liebe Leute. Das Gericht in England hat schlampig gearbeitet und war beweisbar biased.

Nein, er war das Opfer. Das Gericht in Virginia hat sie zur Geldstrafe verurteilt aufgrund von Diffamierung liebe Leute. Das Gericht in England hat schlampig gearbeitet und war beweisbar biased. submitted by Behindstef84 to InfluencerBS [link] [comments]

2024.11.26 12:30 riddleman01 Naam van de klungelige luiaard in Ice Age. (3) letters

Naam van de klungelige luiaard in Ice Age. (3) letters
Antwoord: https://www.puzzelwoordenboeknu.com/puzzel-woensdag-27-november-antwoorden/
submitted by riddleman01 to dailytriviaanswers [link] [comments]

2024.11.26 12:30 Round_Win8376 (FREE) SHIVA TYPE BEAT "OPPS"

(FREE) SHIVA TYPE BEAT submitted by Round_Win8376 to Promote_Your_Channel [link] [comments]

2024.11.26 12:30 YouAreNotMeLiar Kingdom Come Deliverance 2 Features Multiple Endings, Story Involves Protagonist's Journey From "Man To Warrior"

Kingdom Come Deliverance 2 Features Multiple Endings, Story Involves Protagonist's Journey From submitted by YouAreNotMeLiar to rpg_gamers [link] [comments]

2024.11.26 12:30 AutoModerator Get Access to Canva Pro with Updated Rotating Links [November 2024]

submitted by AutoModerator to CanvaLinkPro [link] [comments]

2024.11.26 12:30 how_uh_devin Suggestion for gokarna trip

I'm solo, so I'm thinking of joining a group(group of strangers formed for a trip kind of thing) for gokarna trip please suggest me some good organisers I know bhatakna but there are no reviews about them ... Suggest me some genuine organisers it'll be big help. Thank you!
submitted by how_uh_devin to india_tourism [link] [comments]

2024.11.26 12:30 Difficult-Highlight8 My last card to finish my album can anyone help me?

My last card to finish my album can anyone help me? Play MONOPOLY GO! with me! Download it here: https://mply.io/4aqUQawdj3o
submitted by Difficult-Highlight8 to Monopoly_GO [link] [comments]

2024.11.26 12:30 AutoModerator Finding Balance: Reflect, Recharge, and Refocus 🌟

Hey Superchargers!
Sometimes Tuesday hits hard—Monday’s energy fades, and the weekend still feels so far away. Instead of letting the midweek slump win, let’s take a moment to reframe and refocus.
What’s one thing you’re grateful for today? Or one small thing you can do to make the rest of your week smoother? Maybe it’s organizing your desk, prepping tomorrow’s outfit, or even just pausing to breathe.
Drop your mini-reset in the comments—let’s recharge together! 🌟
submitted by AutoModerator to ADHDSupercharge [link] [comments]

2024.11.26 12:30 MaoGo La première image de l’Univers | Balade mentale

submitted by MaoGo to physiquechimie [link] [comments]

2024.11.26 12:30 bensyverson Encinitas, CA [iPhone 15 Pro, ProRAW Max]

Encinitas, CA [iPhone 15 Pro, ProRAW Max] submitted by bensyverson to iPhoneography [link] [comments]

2024.11.26 12:30 PonPonky clearing up some doubts...

clearing up some doubts... So, currently, my only really useful DPS is Firefly, so the general content of the game is not so easy due to the lack of a second team...
I really like Jing Yuan too and with his return I'm considering going after him and Sunday, I'm at pity 20 and with 101 wishes saved, if by some luck of fate I get both and have some wishes left for Lightcone, which one would it be better to get? Jing Yuan's or Sunday's? Or are both dispensable?
And with the characters I have, what would be the ideal team for them?
https://preview.redd.it/68esvx17p83e1.png?width=1600&format=png&auto=webp&s=4af111f88c6f8e146cf4d481a43364b615631304
submitted by PonPonky to SundayMainsHSR [link] [comments]

2024.11.26 12:30 Just4Digits Tax Residency and Address Requirements for Remote Worker in Ireland

Hi everyone, I’m an Italian citizen working remotely as a full-time employee in Ireland since February 2024 for a local Irish company. My current rental agreement ends in February 2025, and I’m considering traveling within the EU for a few months before securing a new rental here.
During this time, I’d continue paying taxes through my employer as PAYE, but I wouldn’t have a new rental address immediately. What concerns me is whether I’m unintentionally avoiding some rules by not updating my address. Could Revenue question why someone paying taxes here doesn’t have a valid address anymore? Could they even contact my previous landlord to ask about unpaid taxes on a non-existent rent?
Maybe I’m overthinking, but I’d like some reassurance. Does anyone know if this is compliant with Revenue and Irish tax regulations? Is it mandatory to maintain a continuous rental address in Ireland to meet residency requirements? And since I am paying all I own to Revenue what am I avoiding paying?
Also, if anyone knows a type of professional who could help with this (tax accountant, advisor, etc.), I’d really appreciate the recommendation.
Thanks!
submitted by Just4Digits to irishpersonalfinance [link] [comments]

2024.11.26 12:30 chara____dreemurr What’s the craziest thing that happened to you while you were in UTPR?

For me it was a normal utpr day I was enjoying my new X!chara skin when this pretty pro dude attacked me
i was kinda rude that I lost but then I decided to be nice
and I told him my dream of having customizable skins
anyways his friend joins and talks to me a bit
he says “you want customizable skin?”
i said “yeah so bad :(“
Then then he says “oh okay then just go back to what your doing”
then the unthinkable happens
he gifted me customizable skins gamepass
i was so happy I was spaming in the chat “OMG” and “HANSHSHSBSHWIWJWHW” just random words
and that’s basically it
submitted by chara____dreemurr to UTPR [link] [comments]

2024.11.26 12:30 Visible-Bear-4838 Palkia Raid - 3276 7572 7665

submitted by Visible-Bear-4838 to PokemonGoRaids [link] [comments]

2024.11.26 12:30 Huge-Commission6335 Last ball you look at

Yesterday I came across a video of Jayson Shaw explaining his aiming method, and what ball he looks at last before the shot. So he finds the line of CB before going down, then proceeds to find the center of the CB, checks the line of the CB twice, and then he keeps looking at the CB as he shoots. He also gave some pretty valid arguments about it, as he said that if you already found the line of your CB, its pointless to look at the OB as you shoot, and that it can only take your precision down. I personally look at the OB last, because that is what I was taught when I started playing pool, and most of the trainers teach you to do the same. What do you guys look at? Is looking at the CB better, does it vary on different shots?
submitted by Huge-Commission6335 to billiards [link] [comments]

2024.11.26 12:30 readingrachelx Housewife highlights/Daily shit talk - November 26th, 2024

BEVERLY HILLS

POTOMAC
NEW YORK
ATLANTA
MIAMI
ORANGE COUNTY
DALLAS
BRAVO
FROM THE BRAVO ARCHIVES
Links to this week’s episode discussion posts:
submitted by readingrachelx to RHDiscussion [link] [comments]

2024.11.26 12:30 Purple-Reignn silverstone hotel (any year)

for anyone whose been silverstone what did u pay for hotel thinking of paying 1100 for a hotel in milton keynes but is that expensive or should i wait closer to the day or do i book it?
submitted by Purple-Reignn to GrandPrixTravel [link] [comments]

2024.11.26 12:30 Lost-Pride7676 Problem with sort

Hi, I'm a first year college student and I've been trying to make a line in a code to sort a list and i haven't been able to finish it correctly. I have to sort a list of items each eith 5 subitems so that the list goes from the item with the bigest subitem to the one with the smallest one without using lambda or definitions.
I've tried the following but failed:
- works but it's maybe to "chunky" or not to tidy
for i in range(len(resul)):
for j in range(i + 1, len(resul)):
if resul[i][5] < resul[j][5]:
resul[i], resul[j] = resul[j], resul[i]
- works but it sorts it according to the first subitem and not the 5th
ordresul=sorted(resul[perc])
If you have any suggestions I'd appreciate it. Thank you (Note: sorry for my english... I'm not very fluent)
submitted by Lost-Pride7676 to learnprogramming [link] [comments]

2024.11.26 12:30 ansi09 "Timely Vote Credits" (TVC) Has Now Been Enabled On Solana, Since The Start Of Epoch 703

Source: https://x.com/laine_sa_/status/1861364613838934506
Today at the start of epoch 703 a new milestone was achieved on Solana!
⏱️🏎️ **Timely Vote Credits*\*
This feature has now been enabled. It is a major change to on-chain accounting of validator's voting credits that incentivizes fast consensus and penalizes vote lagging.
🧵
​
Developed by @ShinobiSystems and having undergone audits and many years of review and patient waiting, the new accounting system rewards validators that participate in consensus quickly!
This is also the first major feature that was approved through on-chain governance.
​
The previous system awarded 1 credit for 1 successul vote. A vote could be submitted tens and even hundreds of slots late, meaning validators could wait to see which slots are on the correct forks before voting, ensuring they achieve a higher success rate. This delays consensus.
​
Credits are important because this determines how much stakers get in inflationary rewards. A validator with 2% higher vote credits will get 2% more inflationary rewards.
With vote lagging you could get that higher percentage, but it meant your votes weren't meaningfully contributing to consensus (achieving 66.66% votes on a slot).
​
With TVC the max credits per slot is now 16, not 1. This means the total max credits per epoch a validator can achieve is now about 6.9m whereas before it was 432k.
For a given slot X the earliest a validator can vote on it is X+1, this is a vote latency of 1. As long as a validator votes within X+1 or X+2 they receive the full TVC vote credits
If you need more than 2 slots to submit your vote you start leaking credits, 1 credit for each additional slot of latency.
​
It will be interesting to see how this settles in validator APY rankings but it incentivizes fast voting which is good for the network.
A big shoutout to Zantetsu from Shinobi Systems who conceptualized, built and drove this all the way to implementation and activation.
​
A shoutout as well to @Ashwinningg who led the efforts from @anza_xyz's side as well as @jstrry who has also build a great dashboard at https://app.vx.tools and wrote this great spotlight:
https://www.anza.xyz/blog/feature-gate-spotlight-timely-vote-credits
https://preview.redd.it/ehl0ixcbo83e1.png?width=680&format=png&auto=webp&s=e685c13e5534aaf86e0960c090d932abced3e331
Feature Gate Spotlight: Timely Vote Credits Summary Timely Vote Credits (TVC) refers to a new feature designed and approved by Solana validator operators to incentivize validators to submit consensus votes in a timely manner. To do accomplish this goal, TVC will award extra vote "credits" to validators whose votes are included in blocks with relatively low latency. Earned vote credits are directly tied to the proportion of inflation rewards that are awarded to validators.
Motivation Before the activation of this new feature, validators have always earned a full vote credit for each correct vote as long as their vote was received within approximately 2.5 minutes after the voted block was produced. This has led to some validators lagging their consensus votes to earn more vote credits by waiting until the supermajority confirms a block. This avoids the opportunity cost of voting on a block that was not confirmed. This behavior hurts consensus because as more validators lag their votes, confirmation latency gets worse. In the worst case, everyone is waiting for everyone else to make the first move and a supermajority can never be reached to confirm blocks.
Implementation When recording votes, the vote program will record the slot difference of the voted slots and the slot of the block the votes were recorded in. For every recorded vote that gets rooted, the amount of awarded vote credits is a function of slot latency. There is a grace period of 2 slots meaning that votes with a slot latency of 2 slots or less will receive the maximum of 16 credits. Each additional slot of latency will result in a deduction of 1 vote credit down to a minimum of 1 credit per rooted vote.
Aside: How Do Vote Credits Map to Inflation Rewards? The goal of inflation reward distribution is to deliver rewards to each delegated stake account proportionally to how many credits the delegated vote account earned as well as the amount of actively delegated stake. So at the end of each epoch, the Solana protocol calculates "reward points" for each actively delegated stake account by multiplying the stake delegation amount by the amount of vote credits earned by their delegated vote account. Each epoch, the amount of total distributed inflation rewards is calculated by multiplying the latest inflation rate by the amount of active stake in the network. This amount is then distributed to validators in proportion to each active stake account's earned reward points.
If every validator earned the exact same number of vote credits, inflation rewards would be distributed proportionally to active stake. But even before activating TVC there has actually been quite a bit of vote credit variance across each cluster due to how accurately each validator votes on confirmed blocks. There are consensus rules against voting on competing forks, so if a validator votes on a fork that isn't confirmed, their incorrect vote causes them to miss the vote credits on the correct fork until they're allowed to switch back to the correct fork. With TVC, an extra dimension of vote latency is taken into consideration and the amount of vote credits earned for each vote depends on how soon after the voted block the vote was included. So for example, let's say Validator A votes slowly and often votes on the wrong fork while Validator B votes quickly and accurately. Validator B will earn proportionally more vote credits than Validator A and so any stake delegated to validator A will be distributed a higher reward rate on their delegated stake than stake delegated to validator A.
Expectations Faster Confirmation Times Once a block has been fully produced, validators have less than a second to receive, validate, and vote on the produced block to earn full vote credits.
This has a few implications:
  1. Validators have to validate produced blocks very quickly
Validators running on slow hardware will struggle to validate blocks fast enough to vote with low enough latency to earn full vote credits.
Validators who optimize block validation by improving transaction processing scheduling algorithms will be able to submit their votes sooner.
  1. Validators can no longer lag their votes for multiple slots
Some validators have been using different voting behavior modifications that lag their votes to ensure that they earn optimal vote credits. This strategy will no longer be viable once TVC is enabled if the lagging would cause their votes to have latency that is too high.
  1. Validators need to ensure their votes are delivered
It's not always straightforward to know which leader is current producing the next block that will be confirmed by consensus, especially during times of forking.
Vote transactions are primarily delivered over UDP to the current leader. Packet loss could therefore impact latency.
Concerns Geographic Stake Centralization Some validators located outside of North America and Europe will likely decide to move their servers closer to areas where stake is already concentrated to decrease network latency. This is obviously far from ideal. Core developers are considering reducing this centralization risk by increasing the slot latency grace period beyond the current configuration of 2 slots to give validators in sparse stake weight regions more time to send their votes.
Validator Stake Centralization Validators are incentivized to include votes for higher staked nodes in their blocks first to increase the stake weight of their fork. This means that higher staked nodes will tend to have lower vote latency than other nodes. Again, this is the reason we have a grace period for vote inclusion.
Voting Censorship Once TVC is enabled, block producers may be tempted to censor or delay votes to decrease the vote credits earned by their competitors. This temptation shouldn't be a big issue for several reasons. First, any leader who completely censors votes from being included in their blocks is forgoing the transaction fees for those vote transactions. Second, any leader who consistently delays votes from particular validators can be publicly shamed or retaliated against because this behavior is publicly observable onchain. Lastly, the actual impact of targeted censorship is fairly minimal. Votes can earn up to 16 credits for low latency inclusion and there is a grace period of a few slots. So even if a leader censors votes for a few slots, they will only lose a small portion of the total possible credits.
How Can Validators Track Vote Latency? The Vortex dashboard has features for analyzing the timely vote credits earned by each validator:
How Can Validators Improve Vote Latency? Improve Replay Times
  1. Experiment with block verification methods.
For example, the new "unified scheduler" is available for use on Agave v2 and can be enabled via the following CLI parameter:
agave-validator --block-verification-method unified-scheduler
  1. Upgrade and configure hardware
Solana validator operators should ensure that they are running sufficiently performant hardware and that their validators are configured according to the latest recommendations.
  1. Use the default full snapshot interval
The Agave validator client has degraded block production and validation during full snapshot creation but this affects all validators. If a validator uses a custom interval, their voting could be degraded when the rest of the cluster is validating and voting on blocks at normal speeds. Validators with a custom full snapshot interval should consider removing the following CLI parameter:
agave-validator --full-snapshot-interval-slots XXXX
Improve Vote Delivery
  1. Votes are sent over UDP and therefore do not receive acks
Validators may want to consider resending votes every 100ms to ensure they weren't dropped. There is no Agave configuration parameter for this yet. PR's welcome!
  1. Send votes to the current leader
Votes are ideally sent to the current leader but that's not always straightforward. Agave currently delivers votes by fanning them out over the next few expected leader slots. This behavior might not be sufficient. If validators find a more effective strategy or can collect some metrics on this, PR's are welcome!
Aside: How Do Vote Mods Earn More Vote Credits? Several different categories of modified voting behaviors have been observed on mainnet. But before discussing those modifications, the Anza core dev team would like to warn validator operators against running unaudited code on mainnet. This has the potential to cause unrecoverable failures in their validators or lead to slashable actions.
Vote Lagging The first category is vote lagging. Rather than using the default behavior of attempting to voting on the most-likely-to-be-confirmed fork, some validators have implemented mods that simply delay voting until the rest of the cluster has already confirmed a block. The benefit of this strategy is obvious, such validators never vote incorrectly and miss out on vote credits due to voting on an incorrect block. But the drawback is clear too: if enough validators lag their votes, eventually everyone will be waiting to see what everyone else will vote on and confirmation times get much worse which can even result in the cluster failing to reach consensus on any new blocks. This modification strategy is clearly bad for the Solana protocol and is why TVC was implemented. TVC is designed to penalize vote laggers by awarding proportionally fewer vote credits to votes that were received with a delay.
Vote Backfilling The second category of modifications is vote backfilling. If for some reason a validator stops voting for awhile or falls behind the cluster, they may skip voting on quite a few blocks until they catch up. If a validator modifies their voting behavior, they can attempt to vote on past blocks that were already confirmed by the cluster in order to earn more credits. The stock Agave validator behavior is not optimized to do this sort of backfilling because it doesn't really improve the health of consensus on a cluster. By default, the Agave validator creates vote transactions with the "recent blockhash" set to the blockhash of the block they are voting on. Even if they are voting on a block which is recent enough to earn vote credits, the blockhash could be old enough that the transaction is dropped. In this type of situation, modified validators that fetch a recent blockhash have an opportunity to earn some vote credits that they otherwise would have missed. After TVC is activated, these extra vote credits will be pretty negligible but still offer a slight benefit to validators that implement this mod. But this category of modification has a roughly neutral effect on cluster consensus health since block finalization doesn't require validators to vote on each block in a fork, a vote on one block of a fork is effectively a vote on all ancestor blocks as well.
Vote Lockout Adjustments The third category of modifications is vote lockout adjustments. To understand this class of modification, one must first understand how the "tower" data structure in Solana's Tower BFT algorithm works. Every time a vote is recorded in a validator's local tower structure, any "expired" votes are removed from the tower before pushing the new vote and these expired votes do not earn any credits. This behavior comes from the mechanism used to force validators to wait until votes on an incorrect fork expire before they're allowed to start voting on a competing fork. Vote recording on-chain is done essentially the same way as tower vote updates despite it being impossible to process a vote for a competing fork in a block produced on a separate fork. In order to avoid votes expiring, validators can choose to increase the lockout expiration time of their previous votes. By doing so, they are increasing their commitment to that fork in order to avoid missing out on credits.
Vote Accuracy Lastly, we have modifications for vote accuracy. There are likely multiple strategies in use by different competing validators but the basic idea is that validators attempt to make a more informed decision on how likely a block will be confirmed or not. They could assign scores to different leaders and predict which slot leaders are likely to have their blocks skipped or confirmed based on the scores of the current and following block leaders. These types of modifications are likely (but not necessarily) helpful rather than harmful to consensus health as long as they don't involve lagging. Ideally some of these strategies are eventually upstreamed into the default voting heuristics to improve vote accuracy across the cluster.
Upcoming Protocol Improvements The Anza core dev team is also actively working on protocol improvements to help validators reduce their vote latency. Here are a few of the upcoming improvements that will be applied soon or are being considered for the future:
  1. Partitioned epoch rewards
Epoch boundaries are notoriously slow but this affects every validator right now. Partitioned epoch rewards will help alleviate this slowness and should be activated soon.
  1. Faster snapshot creation
Full snapshot creation is very compute and memory intensive and noticeably slows down block validation and confirmation times. Solana core developers are actively working on transitioning to a faster approach which can be followed on SIMD-0125.
  1. Vote ingestion via QUIC
This change is still in the proposal review process and can be followed on SIMD-0195. The motivation for migrating to QUIC for vote ingestion is to improve vote delivery guarantees.
  1. Voting grace period increase
This change has been proposed by a few folks in the Solana validator community. Due to increased network latency, he current grace period of 2 slots is seen as unfair to nodes located outside of North America and Europe.
  1. Vote credit algorithm improvements
Due to the risk of validators running unaudited code to modify voting behavior, the Anza core dev team aims to improve the vote credit algorithm to eliminate the advantage of certain voting mods such as backfilling and lockout adjustments.
Links Timeline Credits Thanks to everyone who took the time to give feedback on this post:
submitted by ansi09 to solana [link] [comments]

2024.11.26 12:30 Rare-Winter3355 Anyone needing a Referral link for $2600 off? Please DM me!

submitted by Rare-Winter3355 to teslacanada [link] [comments]

2024.11.26 12:30 AutoModerator FAKE BANS ARE BACK

The accounts u/Friendly-Ad6745 and u/K_ntAguero have been taken over by scammers. Do not do business with them. FAKE BANS ARE BACK.
These same scammers from last year are back. These scammers will message you saying you are banned from this group.
Then they try to get your personal info to “verify” that you were not scamming and then they hijack your accounts.
Specifically asking to get into your Reddit account to “view your messages to make sure you’re not a scammer” and then they takeover that account, in order to scam people using your account.
Please disregard and don’t respond to any messages you may receive from these scammers. Please Report any of these messages to the modmail.
Messages from mods appear as the subreddit itself… if you need clarification message one of the mods.
The scammers will try and contact you from fragranceswapmodmail or something similar. When we message you it is just fragranceswap
* We will never ask for any account passwords or for you to change yours. Do not give them out \*
\** Below is what they will message you word for word **\**
"You have been permanently banned from participating in fragranceswap. You can still view and subscribe to fragranceswap, but you won't be able to post or comment.
Note from the moderators:
You have been banned for violating the rules of our subreddit. (Reason - Scamming)
https://www.reddit.com/fragranceswap/about/rules/
If you have a question regarding your ban, you can contact the moderator team for fragranceswap by replying to this message."
submitted by AutoModerator to fragranceswap [link] [comments]

https://yandex.ru/