THE LIE BEHIND STANDARDIZED TESTING #OptOut# #OptOut2018# “This year, it looked like a single tear running down the face of one of my sweetest students. When I asked her afterwards why she was crying, she told... https://t.co/g4wZ925xNw

Test boycotts top 50% on LI as large opt-outs continue #OptOut# #OptOut2018# #LIOptOut# Local school leaders say the pattern of resistance, established over several years, will be hard to break... https://t.co/UwNuaaIw7x

RAISE YOUR TEACHER/PARENT VOICE! Please take this very important NEW survey from Columbia Teachers College on Opting out of Testing. https://t.co/UK7DLUbUbS #OptOut# #OptOut2018# https://t.co/UK7DLUbUbS

NY Superintendent Mike Hynes -> Parents, we respect your rights to opt your child(ren) out of 3-8 state assessments. #OptOut2018# #OptOut# Here are some thoughts for your consideration....... https://t.co/MJ1Pd9LZ7j

Genesis Update: Developer Vesting Now Visible + Auto-Lock Feature Live We’ve added a new feature to the Genesis Launch: developers can now opt into auto-locking and vesting schedules for their token allocations, directly within the launch interface. More importantly, Virgens can now view these vesting choices in full detail, helping them make informed decisions about which projects to back. ---- Why This Matters Our mission with Genesis Launch has always been twofold: 1. Ensure fair, transparent launches, no snipers, no cabals. 2. Make it effortless for Virgens to navigate projects, assess risk, and support what aligns with their values. By surfacing developer vesting schedules, we provide an added layer of transparency. For supporters with more risk-aware preferences, the absence of token locking may influence their decision to pledge. This update helps them filter projects with greater clarity. At the same time, we’ve automated the backend process of token distribution, so developers can focus on what they do best: building great agents. Virtuals handles the infrastructure. Developers handle the vision. ---- How It Works (Virgen Side) All Genesis Launch pages will now show: •Whether the developer opted for locking •Full vesting breakdown and timelines •A visualized chart of token release schedules This allows users to assess commitment, risk, and alignment before pledging. ---- How It Works (Developer Side) Developers can now allocate and lock up to 50% of their unallocated developer supply. Developers will be prompted to: •Set categories (e.g., “Core Team”, “Marketing & Operations”) •Enter recipients and amounts •Choose a vesting schedule: •Immediate: Tokens unlock at a fixed date post-TGE •Linear: Tokens unlock gradually from a set start date By default, locking is recommended. If developers opt out, developers will be required to provide a recipient wallet address for immediate transfer. Once finalized, the vesting schedule is implemented and executed. Developers will have 24 hours post-submission to make changes, after that, the schedule is locked in. This is another step toward making Genesis a launchpad where real projects thrive, and rugs don’t. More transparency. Less risk. Virgens, do your research. Developers, build with confidence.

🚨 Chelsea must pay Manchester United £5m if Jadon Sancho loan is not turned permanent in summer. 24yo winger left #MUFC# on temporary basis with buy obligation worth up to £25m but #CFC# can opt out for set fee. W/ @liam_twomey @SJohnsonSport @TheAthleticFC https://t.co/nT2qAoJ1Sr

Prysm Release v5.1.2 is here with improvements and new features! 1. The feature flag --enable-experimental-state has been flipped to "opt out" via --disable-experimental-state, bringing significant memory usage improvements at runtime. 2. Updates to libp2p’s gossipsub for better bandwidth stability and support for IDONTWANT control messages 3. The gRPC gateway has been deprecated. For JSON data, please switch to the standardized beacon-APIs 4. This is our first release utilizing pull request authors' entries directly from our https://t.co/HIMZiOS1PV 5. This also contains a hotfix for a bug in the implementation of the beacon api streaming events endpoint of 5.1.1. It's recommended to update to v5.1.2 at your convenience. Check out GitHub for more details or join the conversation on Discord. https://t.co/etoS69nLdt

SOUNDCLOUD JUST FED YOUR SONGS TO THE BOTS Congrats, your mixtape might now be training a robot—because SoundCloud changed its rules without making a big deal about it. Unless you're signed to a major label, the platform can now use your uploads to power its AI, with no clear opt-out in the settings. They swear it’s just for stuff like better playlists and stopping scammers—not making robot rappers. Still, artists aren’t loving the idea that their tracks are now AI snacks. Source: TechCrunch