#Public Events APIs

[mariacallous]

Palantir, facing mounting public scrutiny for its work with the Trump administration, took an increasingly defensive stance toward journalists and perceived critics this week, both at a defense conference in Washington, DC, and on social media.

On Tuesday, a Palantir employee threatened to call the police on a WIRED journalist who was watching software demonstrations at its booth at AI+ Expo. The conference, which is hosted by the Special Competitive Studies Project, a think tank founded by former Google CEO Eric Schmidt, is free and open to the public, including journalists.

Later that day, Palantir had conference security remove at least three other journalists—Jack Poulson, writer of the All-Source Intelligence Substack; Max Blumenthal, who writes and publishes The Grayzone; and Jessica Le Masurier, a reporter at France 24—from the conference hall, Poulson says. The reporters were later able to reenter the hall, Poulson adds.

The move came after Palantir spokespeople began publicly condemning a recent New York Times report titled “Trump Taps Palantir to Compile Data on Americans” published on May 30. WIRED previously reported that Elon Musk’s so-called Department of Government Efficiency (DOGE) was building a master database to surveil and track immigrants. WIRED has also reported that the company was helping DOGE with an IRS data project, collaborating to build a “mega-API.”

The public criticism from Palantir is unusual, as the company does not typically issue statements pushing back on individual news stories.

Prior to being kicked out of Palantir’s booth, the WIRED journalist, who is also the author of this article, was taking photos, videos, and written notes during software demos of Palantir FedStart partners, which use the company’s cloud systems to get certified for government work. The booth’s walls had phrases like “REAWAKEN THE GIANT” and “DON’T GIVE UP THE SHIP!” printed on the outside. When the reporter briefly stepped away from the booth and attempted to re-enter, she was stopped by Eliano Younes, Palantir’s head of strategic engagement, who said that WIRED was not allowed to be there. The reporter asked why, and Younes repeated himself, adding that if WIRED tried to return, he would call the police.

After the conference ended, Younes responded to a photo from the conference that the reporter posted on X. “hey caroline, great seeing you at the expo yesterday,” he wrote. “can't wait to read your coverage of the event.” Palantir did not respond to WIRED’s request for comment.Got a Tip?Are you a current or former government employee who wants to talk about what's happening? We'd like to hear from you. Using a nonwork phone or computer, contact the reporter securely on Signal at 785-813-1084.

Poulson tells WIRED that he, Blumenthal, and Le Masurier were also watching demos at Palantir’s booth prior to being kicked out. After a Tuesday panel with Younes and Palantir engineer Ryan Fox, Poulson says Le Masurier approached Younes near Palantir’s booth and asked about the company’s work for Immigrations and Customs Enforcement. A Palantir employee stepped between them and claimed that Palantir had asked her to leave “multiple times,” according to a video of the interaction viewed by WIRED, and she was escorted out of the conference hall shortly after.

“Apparently, Palantir was so annoyed that they not only kicked her out, but demanded that Max and I be kicked out as well,” Poulson says. “So the security guards came and got us.”

The group was allowed back inside the conference hall after explaining their situation to friendly security guards, Poulson says. The guards asked them to respect any requests from attendees to stop filming.

Some conference organizers appeared to be on high alert after a pro-Palestine demonstrator interrupted a panel with Palantir’s head of defense, Mike Gallagher, on Monday. The demonstrator was subsequently ejected from the conference, Poulson reported. A handful of pro-Palestine activists were also thrown out on Tuesday after disrupting a panel with Eric Schmidt and Thom Shanker, a former Pentagon reporter at the The New York Times. (Palantir formed a partnership with the Israeli military in January 2024, and Google is part of a $1.2 billion cloud contract with the Israeli government.) Poulson tells WIRED that on Wednesday, the conference began mandatory bag-checks at at least one talk.

During Younes’ Tuesday panel with fellow Palantir employee Fox, which was focused on what the two men do at Palantir and why they like working there, Younes made passing references to perceived critics of the company. When talking about the reasons he joined Palantir, he said, “I was sick and tired of people with bad intentions,” Younes said, “many of them who are actually here.” He later added that he’s a “big believer” in the views of Palantir’s cofounders, particularly those of CEO Alex Karp. (Karp is known for his nonapologetic stance toward Palantir’s work with military and defense agencies and immigration authorities.) “Playing a role in helping them, to prove the doubters and the haters wrong, that just feels really good,” Younes said.

On Tuesday, Palantir posted on X claiming the Times article was “blatantly untrue” and said that the company “never collects data to unlawfully surveil Americans.” The Times article did not claim that Palantir buys or collects its own data, though it’s a common misconception that the company does so.

The New York Times did not immediately respond to a request for comment by WIRED.

On Wednesday, Palantir’s official X account continued posting about the Times article on X. “Want to meet Dr. Karp?” the post read. “In 90 seconds, identify the technical errors in this article. DM us a video in the next 24 hours - whoever finds the most inaccuracies gets an interview with him.”

[lukas-biggest-fan]

Black Diamond Pool just erupted (05/30)

For anybody who was following the news last summer, you may remember this unexpected event on July 23rd. In the aftermath, the park service shut down the boardwalk area (which was completely destroyed). Park Service, USGS, and University of Utah geologists set up monitoring instruments immediately after.

In the time since the event, there hasn't been much news (at least that i've heard). Until today.

Last week, USGS went public with a webcam for monitoring Black Diamond Pool. It takes a snapshot every 15 minutes - you can see the most recent snapshot here (links to previous snapshots can be found on the USGS AshCam API).

Today (05/30/2025), we noticed the first signs of activity. A disturbance in the left side of the pool (relative to the webcam) starting at 13:45 (local time):

Followed by periods of increased convection, and finally...

at 20:45 we see the water level drop daramtically, indicating the end of an "eruption." (At the time of posting, it is not clear whether this activity meets the definition of an actual eruption. Will update). The event had enough force to move those rocks all the way on the right. Heres a before and after:

Safe to say they probably aren't opening this thing up anytime soon. But, for anybody interested in this kind of stuff, this is a landmark event, signalling continued (and possibly regular) activity at Black Diamond. This is a long-awaited continuation of what is probably the biggest national-park related news in recent history.

Happy pride month.

[notwiselybuttoowell]

Oil interests have funded cultural institutions such as museums, youth organizations and athletic groups in recent years, new research shows, in what appears to be a public relations effort to boost their image amid growing public awareness of the climate crisis.

Top US fossil fuel lobby group the American Petroleum Institute (API) sponsored a 2017 workshop for the Pennsylvania Girl Scouts, featuring “activities that mimicked work in the energy industry”. Energy giant BP in 2016 sponsored Washington DC’s National Gallery of Art and continues to fund the British Museum in London.

The new evidence of sponsorships was found in internal communications from 2015 to 2021 subpoenaed from big oil via a US congressional investigation last year. They were uncovered by Rebecca John, a researcher at the Climate Investigations Center, and published in the climate outlet DeSmog.

The documents also shed light on the particular value the companies see in the partnerships. In a 2017 email, for instance, the then CEO of API said the Girl Scouts sponsorship came as part of an effort to partner with “nontraditional local allies”, which he described as “some of the best and most influential voices with targeted policymakers on industry issues” who can help the lobby group overcome “policy issues”. API has a large lobbying presence in Pennsylvania, which is the country’s second-largest gas producer.

The British Museum has previously defended its partnership with BP, including after the company scaled back its climate goals this past February. The museum needs “corporate and private donations from companies like BP to ensure that the magnificent collection stays on display to the public for centuries to come”, a spokesperson told the Guardian at the time.

The documents indicate that in Shell’s 2020 “reputation plan” it said it would “secure partnerships with credible external influencers” in an effort to overcome “low credibility and trust” in the company.

The oil giant has partnered with a wide variety of major museums, sporting events, concert halls and other arts and cultural institutions. It could not be reached for comment, but its spokespeople previously said institutions can maintain their freedom even as they receive funding from Shell.

A 2017 internal memo from BP America says the relationships could provide a shield from “threats to BP’s reputation”, including “overall negative sentiment about the oil and gas industry” and the “policy and politics of climate change”. A separate 2016 document assessing the company’s “position” instructed staff to emphasize the message that more than 50 million people in the UK had “engaged with a BP-supported activity” due to its funding of institutions such as the British Museum and Royal Shakespeare Company.

The revelations come as activists have increasingly pressured arts and cultural institutions to cut ties with fossil fuel interests. The Royal Shakespeare Company, for instance, ended its BP partnership in 2019 after eight years, following months of protests over the partnership. At the time, BP said it was “disappointed and dismayed” by the decision.

DeSmog found evidence of dozens of other cultural sponsorships from the energy companies between 2015 and 2021, including of libraries, music festivals, gender justice initiatives and theaters. There have been hundreds of similar partnerships through history, from a children’s radio show funded by Standard Oil in the 1930s, to the current sponsorship of a media podcast by BP.

The relationships illustrate a decades-long industry strategy known as “affinity of purpose advertising”, said Robert Brulle, an environmental sociologist at Brown University. The term was coined by Herbert Schmertz, the late executive of Mobil Oil (now ExxonMobil).

“It’s the idea that if a corporation is associated with a high-value, cultural activity that prestige rubs off on the corporation,” said Brulle. In one well-known historical example, Mobil in the 1970s began sponsoring the television drama series Masterpiece Theater.

“Apparently this works quite well,” said Brulle, noting that Mobil evaluated the approach in a 1980 study and decided it was worthwhile. “It [has] now become a commonplace activity to burnish their corporate reputation and goodwill by sponsoring these types of cultural activities.”

[pentesttestingcorp]

Symfony Clickjacking Prevention Guide

Clickjacking is a deceptive technique where attackers trick users into clicking on hidden elements, potentially leading to unauthorized actions. As a Symfony developer, it's crucial to implement measures to prevent such vulnerabilities.

🔍 Understanding Clickjacking

Clickjacking involves embedding a transparent iframe over a legitimate webpage, deceiving users into interacting with hidden content. This can lead to unauthorized actions, such as changing account settings or initiating transactions.

🛠️ Implementing X-Frame-Options in Symfony

The X-Frame-Options HTTP header is a primary defense against clickjacking. It controls whether a browser should be allowed to render a page in a <frame>, <iframe>, <embed>, or <object> tag.

Method 1: Using an Event Subscriber

Create an event subscriber to add the X-Frame-Options header to all responses:

// src/EventSubscriber/ClickjackingProtectionSubscriber.php namespace App\EventSubscriber; use Symfony\Component\EventDispatcher\EventSubscriberInterface; use Symfony\Component\HttpKernel\Event\ResponseEvent; use Symfony\Component\HttpKernel\KernelEvents; class ClickjackingProtectionSubscriber implements EventSubscriberInterface { public static function getSubscribedEvents() { return [ KernelEvents::RESPONSE => 'onKernelResponse', ]; } public function onKernelResponse(ResponseEvent $event) { $response = $event->getResponse(); $response->headers->set('X-Frame-Options', 'DENY'); } }

This approach ensures that all responses include the X-Frame-Options header, preventing the page from being embedded in frames or iframes.

Method 2: Using NelmioSecurityBundle

The NelmioSecurityBundle provides additional security features for Symfony applications, including clickjacking protection.

Install the bundle:

composer require nelmio/security-bundle

Configure the bundle in config/packages/nelmio_security.yaml:

nelmio_security: clickjacking: paths: '^/.*': DENY

This configuration adds the X-Frame-Options: DENY header to all responses, preventing the site from being embedded in frames or iframes.

🧪 Testing Your Application

To ensure your application is protected against clickjacking, use our Website Vulnerability Scanner. This tool scans your website for common vulnerabilities, including missing or misconfigured X-Frame-Options headers.

Screenshot of the free tools webpage where you can access security assessment tools.

After scanning for a Website Security check, you'll receive a detailed report highlighting any security issues:

An Example of a vulnerability assessment report generated with our free tool, providing insights into possible vulnerabilities.

🔒 Enhancing Security with Content Security Policy (CSP)

While X-Frame-Options is effective, modern browsers support the more flexible Content-Security-Policy (CSP) header, which provides granular control over framing.

Add the following header to your responses:

$response->headers->set('Content-Security-Policy', "frame-ancestors 'none';");

This directive prevents any domain from embedding your content, offering robust protection against clickjacking.

🧰 Additional Security Measures

CSRF Protection: Ensure that all forms include CSRF tokens to prevent cross-site request forgery attacks.

Regular Updates: Keep Symfony and all dependencies up to date to patch known vulnerabilities.

Security Audits: Conduct regular security audits to identify and address potential vulnerabilities.

📢 Explore More on Our Blog

For more insights into securing your Symfony applications, visit our Pentest Testing Blog. We cover a range of topics, including:

Preventing clickjacking in Laravel

Securing API endpoints

Mitigating SQL injection attacks

🛡️ Our Web Application Penetration Testing Services

Looking for a comprehensive security assessment? Our Web Application Penetration Testing Services offer:

Manual Testing: In-depth analysis by security experts.

Affordable Pricing: Services starting at $25/hr.

Detailed Reports: Actionable insights with remediation steps.

Contact us today for a free consultation and enhance your application's security posture.

[laviniaplei]

hi all yesterday i made a self-hostable tumblr blocker that blocks anyone who liked a list of specifiable posts

how it works:

first, you have to register an app at https://www.tumblr.com/oauth/apps for access to the tumblr api

then, to be able to obtain access tokens for your blog, it sets up two endpoints at <hosted ip:port>/authorize and <hosted ip:port>/callback- the former will show you a link to authorize the above app to your blog, and the latter receives the resulting access tokens

tumblockr then uses the tumblr api to obtain a list of people who have liked each of the posts specified in the .env file, and adds them to a queue for processing (blocking). both obtaining likers & blocking operate on a periodic schedule, also configurable in the .env

in the event that it runs up against tumblrs api rate limits, the queue/list of blocked users/various tokens and such are kept in storage so that operation can resume an hour later (that is, after the hourly rate limit expires)

all you need is a docker-capable device with a public facing ip (like a vps or some other cloud computing solution, ideally, but a personal desktop will do in a pinch as long as you dont keep it exposed)

[this-week-in-rust]

This Week in Rust 593

Hello and welcome to another issue of This Week in Rust! Rust is a programming language empowering everyone to build reliable and efficient software. This is a weekly summary of its progress and community. Want something mentioned? Tag us at @ThisWeekInRust on X (formerly Twitter) or @ThisWeekinRust on mastodon.social, or send us a pull request. Want to get involved? We love contributions.

This Week in Rust is openly developed on GitHub and archives can be viewed at this-week-in-rust.org. If you find any errors in this week's issue, please submit a PR.

Want TWIR in your inbox? Subscribe here.

Updates from Rust Community

Newsletters

The Embedded Rustacean Issue #42

This Week in Bevy - 2025-03-31

Project/Tooling Updates

Fjall 2.8

EtherCrab, the pure Rust EtherCAT MainDevice, version 0.6 released

A process for handling Rust code in the core kernel

api-version: axum middleware for header based version selection

SALT: a VS Code Extension, seeking participants in a study on Rust usabilty

Observations/Thoughts

Introducing Stringleton

Rust Any Part 3: Finally we have Upcasts

Towards fearless SIMD, 7 years later

LLDB's TypeSystems: An Unfinished Interface

Mutation Testing in Rust

Embedding shared objects in Rust

Rust Walkthroughs

Architecting and building medium-sized web services in Rust with Axum, SQLx and PostgreSQL

Solving the ABA Problem in Rust with Hazard Pointers

Building a CoAP application on Ariel OS

How to Optimize your Rust Program for Slowness: Write a Short Program That Finishes After the Universe Dies

Inside ScyllaDB Rust Driver 1.0: A Fully Async Shard-Aware CQL Driver Using Tokio

Building a search engine from scratch, in Rust: part 2

Introduction to Monoio: A High-Performance Rust Runtime

Getting started with Rust on Google Cloud

Miscellaneous

An AlphaStation's SROM

Real-World Verification of Software for Cryptographic Applications

Public mdBooks

[video] Networking in Bevy with ECS replication - Hennadii

[video] Intermediate Representations for Reactive Structures - Pete

Crate of the Week

This week's crate is candystore, a fast, persistent key-value store that does not require LSM or WALs.

Thanks to Tomer Filiba for the self-suggestion!

Please submit your suggestions and votes for next week!

Calls for Testing

An important step for RFC implementation is for people to experiment with the implementation and give feedback, especially before stabilization.

If you are a feature implementer and would like your RFC to appear in this list, add a call-for-testing label to your RFC along with a comment providing testing instructions and/or guidance on which aspect(s) of the feature need testing.

No calls for testing were issued this week by Rust, Rust language RFCs or Rustup.

Let us know if you would like your feature to be tracked as a part of this list.

Call for Participation; projects and speakers

CFP - Projects

Always wanted to contribute to open-source projects but did not know where to start? Every week we highlight some tasks from the Rust community for you to pick and get started!

Some of these tasks may also have mentors available, visit the task page for more information.

If you are a Rust project owner and are looking for contributors, please submit tasks here or through a PR to TWiR or by reaching out on X (formerly Twitter) or Mastodon!

CFP - Events

Are you a new or experienced speaker looking for a place to share something cool? This section highlights events that are being planned and are accepting submissions to join their event as a speaker.

* Rust Conf 2025 Call for Speakers | Closes 2025-04-29 11:59 PM PDT | Seattle, WA, US | 2025-09-02 - 2025-09-05

If you are an event organizer hoping to expand the reach of your event, please submit a link to the website through a PR to TWiR or by reaching out on X (formerly Twitter) or Mastodon!

Updates from the Rust Project

438 pull requests were merged in the last week

Compiler

allow defining opaques in statics and consts

avoid wrapping constant allocations in packed structs when not necessary

perform less decoding if it has the same syntax context

stabilize precise_capturing_in_traits

uplift clippy::invalid_null_ptr_usage lint as invalid_null_arguments

Library

allow spawning threads after TLS destruction

override PartialOrd methods for bool

simplify expansion for format_args!()

stabilize const_cell

Rustdoc

greatly simplify doctest parsing and information extraction

rearrange Item/ItemInner

Clippy

new lint: char_indices_as_byte_indices

add manual_dangling_ptr lint

respect #[expect] and #[allow] within function bodies for missing_panics_doc

do not make incomplete or invalid suggestions

do not warn about shadowing in a destructuring assigment

expand obfuscated_if_else to support {then(), then_some()}.unwrap_or_default()

fix the primary span of redundant_pub_crate when flagging nameless items

fix option_if_let_else suggestion when coercion requires explicit cast

fix unnested_or_patterns suggestion in let

make collapsible_if recognize the let_chains feature

make missing_const_for_fn operate on non-optimized MIR

more natural suggestions for cmp_owned

collapsible_if: prevent including preceeding whitespaces if line contains non blanks

properly handle expansion in single_match

validate paths in disallowed_* configurations

Rust-Analyzer

allow crate authors to control completion of their things

avoid relying on block_def_map() needlessly

fix debug sourceFileMap when using cppvsdbg

fix format_args lowering using wrong integer suffix

fix a bug in orphan rules calculation

fix panic in progress due to splitting unicode incorrectly

use medium durability for crate-graph changes, high for library source files

Rust Compiler Performance Triage

Positive week, with a lot of primary improvements and just a few secondary regressions. Single big regression got reverted.

Triage done by @panstromek. Revision range: 4510e86a..2ea33b59

Summary:

(instructions:u) mean range count Regressions ❌ (primary) - - 0 Regressions ❌ (secondary) 0.9% [0.2%, 1.5%] 17 Improvements ✅ (primary) -0.4% [-4.5%, -0.1%] 136 Improvements ✅ (secondary) -0.6% [-3.2%, -0.1%] 59 All ❌✅ (primary) -0.4% [-4.5%, -0.1%] 136

Full report here.

Approved RFCs

Changes to Rust follow the Rust RFC (request for comments) process. These are the RFCs that were approved for implementation this week:

No RFCs were approved this week.

Final Comment Period

Every week, the team announces the 'final comment period' for RFCs and key PRs which are reaching a decision. Express your opinions now.

Tracking Issues & PRs

Rust

Tracking Issue for slice::array_chunks

Stabilize cfg_boolean_literals

Promise array::from_fn is generated in order of increasing indices

Stabilize repr128

Stabilize naked_functions

Fix missing const for inherent pointer replace methods

Rust RFCs

core::marker::NoCell in bounds (previously known an [sic] Freeze)

Cargo,

Stabilize automatic garbage collection.

Other Areas

No Items entered Final Comment Period this week for Language Team, Language Reference or Unsafe Code Guidelines.

Let us know if you would like your PRs, Tracking Issues or RFCs to be tracked as a part of this list.

New and Updated RFCs

Allow &&, ||, and ! in cfg

Upcoming Events

Rusty Events between 2025-04-02 - 2025-04-30 🦀

Virtual

2025-04-02 | Virtual (Indianapolis, IN, US) | Indy Rust

Indy.rs - with Social Distancing

2025-04-03 | Virtual (Nürnberg, DE) | Rust Nurnberg DE

Rust Nürnberg online

2025-04-03 | Virtual | Ardan Labs

Communicate with Channels in Rust

2025-04-05 | Virtual (Kampala, UG) | Rust Circle Meetup

Rust Circle Meetup

2025-04-08 | Virtual (Dallas, TX, US) | Dallas Rust User Meetup

Second Tuesday

2025-04-10 | Virtual (Berlin, DE) | Rust Berlin

Rust Hack and Learn

2025-04-15 | Virtual (Washington, DC, US) | Rust DC

Mid-month Rustful

2025-04-16 | Virtual (Vancouver, BC, CA) | Vancouver Rust

Rust Study/Hack/Hang-out

2025-04-17 | Virtual and In-Person (Redmond, WA, US) | Seattle Rust User Group

April, 2025 SRUG (Seattle Rust User Group) Meetup

2025-04-22 | Virtual (Dallas, TX, US) | Dallas Rust User Meetup

Fourth Tuesday

2025-04-23 | Virtual (Cardiff, UK) | Rust and C++ Cardiff

**Beyond embedded - OS development in Rust **

2025-04-24 | Virtual (Berlin, DE) | Rust Berlin

Rust Hack and Learn

2025-04-24 | Virtual (Charlottesville, VA, US) | Charlottesville Rust Meetup

Part 2: Quantum Computers Can’t Rust-Proof This!"

Asia

2025-04-05 | Bangalore/Bengaluru, IN | Rust Bangalore

April 2025 Rustacean meetup

2025-04-22 | Tel Aviv-Yafo, IL | Rust 🦀 TLV

In person Rust April 2025 at Braavos in Tel Aviv in collaboration with StarkWare

Europe

2025-04-02 | Cambridge, UK | Cambridge Rust Meetup

Monthly Rust Meetup

2025-04-02 | Köln, DE | Rust Cologne

Rust in April: Rust Embedded, Show and Tell

2025-04-02 | München, DE | Rust Munich

Rust Munich 2025 / 1 - hybrid

2025-04-02 | Oxford, UK | Oxford Rust Meetup Group

Oxford Rust and C++ social

2025-04-02 | Stockholm, SE | Stockholm Rust

Rust Meetup @Funnel

2025-04-03 | Oslo, NO | Rust Oslo

Rust Hack'n'Learn at Kampen Bistro

2025-04-08 | Olomouc, CZ | Rust Moravia

3. Rust Moravia Meetup (Real Embedded Rust)

2025-04-09 | Girona, ES | Rust Girona

Rust Girona Hack & Learn 04 2025

2025-04-09 | Reading, UK | Reading Rust Workshop

Reading Rust Meetup

2025-04-10 | Karlsruhe, DE | Rust Hack & Learn Karlsruhe

Karlsruhe Rust Hack and Learn Meetup bei BlueYonder

2025-04-15 | Leipzig, DE | Rust - Modern Systems Programming in Leipzig

Topic TBD

2025-04-15 | London, UK | Women in Rust

WIR x WCC: Finding your voice in Tech

2025-04-19 | Istanbul, TR | Türkiye Rust Community

Rust Konf Türkiye

2025-04-23 | London, UK | London Rust Project Group

Fusing Python with Rust using raw C bindings

2025-04-24 | Aarhus, DK | Rust Aarhus

Talk Night at MFT Energy

2025-04-24 | Edinburgh, UK | Rust and Friends

Rust and Friends (evening pub)

2025-04-24 | Manchester, UK | Rust Manchester

Rust Manchester April Code Night

2025-04-25 | Edinburgh, UK | Rust and Friends

Rust and Friends (daytime coffee)

2025-04-29 | Paris, FR | Rust Paris

Rust meetup #76

North America

2025-04-03 | Chicago, IL, US | Chicago Rust Meetup

Rust Happy Hour

2025-04-03 | Montréal, QC, CA | Rust Montréal

April Monthly Social

2025-04-03 | Saint Louis, MO, US | STL Rust

icu4x - resource-constrained internationalization (i18n)

2025-04-06 | Boston, MA, US | Boston Rust Meetup

Kendall Rust Lunch, Apr 6

2025-04-08 | New York, NY, US | Rust NYC

Rust NYC: Building a full-text search Postgres extension in Rust

2025-04-10 | Portland, OR, US | PDXRust

TetaNES: A Vaccination for Rust—No Needle, Just the Borrow Checker

2025-04-14 | Boston, MA, US | Boston Rust Meetup

Coolidge Corner Brookline Rust Lunch, Apr 14

2025-04-17 | Nashville, TN, US | Music City Rust Developers

Using Rust For Web Series 1 : Why HTMX Is Bad

2025-04-17 | Redmond, WA, US | Seattle Rust User Group

April, 2025 SRUG (Seattle Rust User Group) Meetup

2025-04-23 | Austin, TX, US | Rust ATX

Rust Lunch - Fareground

2025-04-25 | Boston, MA, US | Boston Rust Meetup

Ball Square Rust Lunch, Apr 25

Oceania

2025-04-09 | Sydney, NS, AU | Rust Sydney

Crab 🦀 X 🕳️🐇

2025-04-14 | Christchurch, NZ | Christchurch Rust Meetup Group

Christchurch Rust Meetup

2025-04-22 | Barton, AC, AU | Canberra Rust User Group

April Meetup

South America

2025-04-03 | Buenos Aires, AR | Rust en Español

Abril - Lambdas y más!

If you are running a Rust event please add it to the calendar to get it mentioned here. Please remember to add a link to the event too. Email the Rust Community Team for access.

Jobs

Please see the latest Who's Hiring thread on r/rust

Quote of the Week

If you write a bug in your Rust program, Rust doesn’t blame you. Rust asks “how could the compiler have spotted that bug”.

– Ian Jackson blogging about Rust

Despite a lack of suggestions, llogiq is quite pleased with his choice.

Please submit quotes and vote for next week!

This Week in Rust is edited by: nellshamrell, llogiq, cdmistman, ericseppanen, extrawurst, U007D, joelmarcey, mariannegoldin, bennyvasquez, bdillo

Email list hosting is sponsored by The Rust Foundation

Discuss on r/rust

[sibyl-of-space]

The San Francisco tech scene is completely beyond satire. I'm in a discord server for game developers based in SF because even though I don't live in the bay area anymore it's still the closest hub for indie developers near me. I went to one of their meetups once, the talk itself was completely useless and I left about 30 mins in, but I did get two people to playtest my demo beforehand so it was still worthwhile. One of those things where you're in a sea of 50 people who annoy you and are able to find maybe one or two people who are cool to talk to.

Anyway, I just received a ping about their next meetup, which is-- I literally could not make up something more on the nose than this if I tried--

brought to you

by

✨ J.P. Morgan ✨

.

Actual quote from the event page:

Are you a developer looking to accept payments and monetize your users effectively? We are excited to announce this unique opportunity to get in on the ground floor and learn about how to monetize your payment flow for your gaming applications at scale. As you may be aware, the Apple App Store and other stores are now allowing outside payment methods within iPhone apps due to "anti-competitive" laws in the EU. As a result, if you are part of Apples small business program, you may be eligible for a discounted percentage fee on IAP instead of the normal 30% fee. We hope you can attend to explore these concepts and learn how you can save money on payment processing fees with J.P. Morgan Payments.

Food is sponsored by J.P. Morgan and drinks are available for purchase at the DNA Lounge bar. All proceeds from drink sales go directly to the venue which helps them keep the lights on, and also helps us continue to host events in their space. DNA Lounge is over 3,000 sqft and is the largest venue we've ever hosted our events at. Speakers will go on stage at 7:00pm. This is an all ages event, is open to the public and is a professional networking event for game developers, artists, students, indies, or really anyone interested in game development. ASL Interpretation services available upon request via email.

Speaker Lineup:

Alan Lee | Developer Relations at J.P. Morgan Payments

Enhance your Payment Experience with J.P Morgan’s Payment Developer Platform

In this session, The J.P Morgan Payments developer relations team will showcase how the Online Payments API allows you to seamlessly accept, process and settle payments from the large suite of supported payment methods. We’ll explore the extended capabilities like tools for fraud prevention, recurring payments and demonstrate how these features can help you improve authorization rates, secure transactions, and gain valuable insights into your payment flow.

so anyway if anybody needs me I will be basically anywhere except at this particular event

[pawank27342]

Tumblr API

In the digital age, APIs (Application Programming Interfaces) have become crucial tools for developers, enabling them to build richer, more dynamic experiences by integrating and leveraging external services. One such API that has garnered attention is the Tumblr API, which allows developers to access the vast functionalities of Tumblr's microblogging platform to create custom applications and solutions. Tumblr, a platform known for its vibrant community and highly customizable blogs, offers an API that provides programmatic access to its features. This enables developers to read and write Tumblr data, including posts, likes, follows, and more. By using the Tumblr API, developers can automate processes or create entirely new applications that interact with Tumblr in innovative ways. The Tumblr API is RESTful, meaning it follows the representational state transfer architectural style. This makes it straightforward for developers to work with, as it uses standard HTTP methods like GET, POST, PUT, and DELETE. The responses from the API are returned in JSON format, which is lightweight and easy to parse in various programming languages. To start using the Tumblr API, a developer must first obtain credentials by registering their application with Tumblr. This process involves creating an app on the Tumblr website, which provides the necessary OAuth consumer key and secret needed for authentication. OAuth is a standard protocol for authorization that ensures secure access to server resources without exposing user credentials. Once authenticated, developers can make requests to the API to perform different actions. For example, they can fetch public information about a blog, retrieve posts by type (text, photo, quote, link, chat, audio, or video), or even post new content directly to a Tumblr blog programmatically. This opens up possibilities for apps that integrate features like live blogging events, managing multiple blogs simultaneously, or curating content automatically based on specific criteria. Moreover, the Tumblr API supports several useful endpoints. The `/user/info` endpoint retrieves information about the authenticated user, while `/blog/{blog-identifier}/info` gets information about a specific blog. There are also endpoints for retrieving or posting likes and follows, which can be particularly useful for social media analytics and engagement tools. One of the strengths of using the Tumblr API is its flexibility. Developers can build a wide range of applications, from simple scripts that automate daily tasks to complex systems that analyze and interact with Tumblr data in real-time. Additionally, since Tumblr hosts a diverse array of content and communities, applications built with the Tumblr API can cater to niche interests or broad audiences alike. However, working with any API comes with challenges. Rate limits are a common issue; these are restrictions on the number of requests that can be made to the API within a certain time frame. Exceeding these limits can result in temporary blocks or slower response times. Therefore, developers need to handle these limits gracefully in their applications by implementing proper error handling and possibly queuing requests. Security is another critical aspect when dealing with APIs. Since applications using the Tumblr API might handle sensitive user data, ensuring data privacy and security through encryption and secure storage practices is paramount. Furthermore, maintaining compliance with data protection regulations like GDPR is essential when operating in or targeting users from certain regions. In conclusion, the Tumblr API offers extensive capabilities for developers looking to harness the power of social blogging for their applications. Whether it's enhancing existing products with Tumblr integration or building specialized tools for tumblr users, the potential uses are as varied as they are exciting. As with any development project involving third-party services, success often hinges on understanding and navigating the technical requirements and limitations effectively. wordpress By embracing these technologies and adhering to best practices in software development and data security, developers can unlock new creative potentials and deliver exceptional value to users.

wordpress

[the-sleepy-archivist]

Online Privacy and Security Tips

I am a firm believer that people should be able to be anonymous and secure online. Over a lifetime of trial and error, I've slowly learned the best ways to protect myself, and I'd like to pass on that knowledge to anyone who wants to hear it.

Last updated May 2024 (added links to news articles about PimEyes being used to identify someone in real life)

Switch to Firefox for your main browser on Windows and Android

Avoid any browser based on the Chromium project (like Microsoft Edge or Google Chrome), as Google has a major conflict of interest that prevents it from truly having users' privacy interests at heart. It makes ~70-80% of its revenue from its highly targeted advertising business, for which it must collect as much information about you as possible. That means that no matter how badly certain parts of Google want to build privacy into the browser, business interests and pressure will always supersede them, or at least force a compromise that still enables some tracking. Firefox is owned and maintained by a non-profit, so it does not have that same conflict, and it shows in the features it builds (and does not build) and the way it treats its users.

I made a list of my favorite Firefox extensions if you want to make your internet experience more pleasant and/or more secure!

Note: on iOS (i.e. iPhones), Firefox' functionality is limited by Apple restrictions and I do not recommend it - using Safari with Extensions like Adguard or 1Blocker is more secure and will give you a better experience. I made a list of my favorite iOS Safari extensions too!

Use a reputable password manager

I suggest 1Password (avoid LastPass and all of the password managers built into browsers, they're not safe). A good password manager increases your online safety by:

Helping you avoid password reuse (a common cause of account hacking)

Generating complex passwords that are difficult to guess or brute-force, and

Allowing you to keep records of all the different sites you have accounts on (so you can quickly change passwords in the event of a breach or delete your accounts on them when they outlive their usefulness)

Delete old accounts you no longer need

If your data has been deleted, no one can steal and leak it if they manage to hack the company.

Sign up for alerts from HaveIBeenPwned (HIBP) to be notified when your data is leaked in a site hacking.

This allows you to quickly change your password, hopefully before anyone is able to decrypt it (if it wasn't stored properly) or use it (if it was easy to guess). If you have reused that password on other sites, be sure to change your password on those sites either.

Note that some leaks don’t actually have any info about what website they were stolen from; if criminals just dump a huge text file onto a hacking forum that has your username and an accompanying password in it, HIBP doesn’t necessarily know what site they hacked to get that info. This is where a password manager like 1Password will come in handy, because 1P can actually use HIBP’s API to check each of your passwords and see if any of them have been leaked before. It will alert you if you need to change a specific password, even if you weren’t aware that site had been hacked.

Note: 1P only sends the first 5 characters of the password hashes to HIBP, not the passwords themselves. You can read more about the feature and how it preserves your privacy here.

Assume all profile pictures on any site are public, and avoid using your face for them if possible

New AI-powered sites like PimEyes can take an image of you, identify your face, and search for it in other, unrelated images around the internet. I searched for myself using a recent image that had never been posted to the internet before, and it immediately identified me in completely separate images I was using as my profile pictures on Facebook and LinkedIn and provided links to my accounts there. In this new AI era, assume anyone who snaps a picture of you can link you to your identity on any website where you have publicly posted your face before. This is not hyperbole; fans used PimEyes to identify a cameraman at a Taylor Swift concert using nothing more than a screenshot of a video taken of him by a concertgoer. Note: for what it's worth, you can submit an opt-out request to PimEyes if you are worried about someone using it to find your accounts online, but it requires you to submit images of your face and your government ID to the company...

Never post the same (original) image on two accounts that you do want to keep separate

Even a simple reverse image search can allow someone to link your different sites together (i.e. don't post the same vacation sunset photo on both Facebook and Tumblr because anyone can use that to link those sites together. Even if your Facebook or Instagram images are private, a follower of yours on one of those sites could still find the Tumblr you are not comfortable sharing with anyone. Marking your Tumblr as hidden only discourages search engines from indexing it; shady companies can and will ignore that and index it anyway.

[javacrypto22]

The Moxy Platform uses blockchain technology to provide a trustworthy Global eSport Token

INTRODUCTION

Moxy claims to be the first and only eSports gaming platform to solve this gap in the industry. There are primarily two components needed for this to occur:

First, developers need access to a simple web3-free tech stack that allows them to add eSport game types to their games.

Second, there has to be a way for the eSport-ready players to get their hands on the game's eSport-enabled build. Nowhere. There is currently no eSports platform accessible to the general public.

You can get both of these features and more via the Moxy Platform. The Moxy Platform uses blockchain technology to provide a trustworthy Global eSport Token, MOXY, which allows instantaneous transactions and safeguards players and publishers against fraud, hacking, and other forms of cybercrime. The Moxy Platform is well-positioned to pioneer this emerging subgenre of video games, as seen by its rapidly expanding user base, novel approaches to game integration, and almost limitless competitive game types offering real prizes in actual games.

THE ECOSYSTEM OF MOXY

Making a platform for esports requires more than just adding a competitive mode to a game. The Moxy Ecosystem is comprised of numerous interdependent parts, such as:

Player Verification for eSports - For legal and safety reasons, players need to be "eSport ready" before they can take part in "Real Competition." A verification process is obligatory for all Moxy Club users.

MOXY - The Global eSports Token, a universal medium of exchange for competitive video gaming.

Moxy's Admin Dashboard - Members, statistics, collectibles and games that members want to be funded and published are all managed here.

The Moxy Club - Moxy Club provides eSport-ready players, the game marketplace, and the game launcher, centralizes all transactions from all games, lets players purchase and administer MOXY, and simplifies governance through voting.

Forge Moxy - This is the primary set of APIs that facilitates communication between games and allows for the creation of eSports.

Founded on Moxy - As a developer, you'll have access to Foundry. To get their games into the Forge, developers must first publish them to Foundry and receive an API key.

Rewarding Moxy Governance - The development of the Moxy Platform relies on the votes cast by Moxy Club members. Members of the Moxy Club who are actively participating and meeting their responsibilities will earn MOXY.

Platform for Moxy- Economy based on the MOXY token and the Flow network. The Moxy Platform is a token economy developed from the ground up, complete with patented smart contracts and an offline signature system written in Cadence.

Token of Play - Secure token balance that no one can hold. As the player base increases, the Moxy Ecosystem converts PLAY tokens into fresh MOXY.

KEY POINTS OF THE MOXY PLATFORM

The following claims are assumed to be correct and empirically verifiable:

• Global eSports can't happen without MOXY, the Global eSport Token.

• There will soon be a fourth subgenre of video games, and it's competitive online play known as eSports. There are now three types of gaming devices on the market: consoles, computers, and smartphones.

• Only blockchain technology offers any hope of ensuring the safety of esports games played in front of an international audience.

• The continued interest in video games depends on the inclusion of eSports game types where players may compete for cash prizes.

PROOF OF PLAYTM, PLAY SCORE, PLATFORM ENGAGEMENT REWARDS SYSTEM

There are three components of the Moxy Ecosystem that must be in sync for the "Proof of Play" incentive system to be implemented. There are three main components: the PLAY token, the SCORE token, and Proof of PlayTM events.

First is the PLAY token. A system must provide daily prizes for Moxy Club members' involvement. That mechanism is PLAY token. It's a worldwide balance that all Moxy Club members can see and generates a daily variable payout to qualified members. As Moxy Club membership grows, so will distribution. No one can own or sell PLAY tokens. PLAY token holders create MOXY, which must be delivered to Moxy Club members because the PLAY token wallet cannot retain it.

Moxy Club members only earn SCORE tokens. SCORE tokens are untradeable. SCORE is acquired through playing games, voting, participating in eSport events, buying games, and more. These behaviors receive different SCORE. Daily incentives increase with SCORE. This rewards active Club members most.

TECHNOLOGY OF MOXY

The Moxy Platform was developed with the Flow Ecosystem in mind. By partnering with Dapper Labs, Moxy is able to take use of the robust and resilient Flow ecosystem. The Moxy Platform could only accept Flow since it fulfilled all of the necessary criteria. The Moxy Platform is based on Flow because of its extensive technology stack, token mechanisms, pre-existing stablecoin and collectibles ecosystem, smart contract architecture, developer tools, and customer support.

Token Flow: The Moxy Foundation keeps MOXY reserves and will sell new MOXY to Moxy Club members based on events and milestones. The inaugural public sale distributes MOXY to the first Moxy Club members who want to play eSports. MOXY will be introduced if new games increase membership demand. For new Moxy Club members to play eSport game types, the Moxy Foundation will assign tokens from the appropriate internal wallet to the "Sale" wallet.

Token Flow Synopsis: The Moxy Club's "hot" wallet is the Moxy Foundation's sale wallet. This wallet accepts credit cards and USDC for MOXY purchases. Moxy Club members may always check the Sale wallet balance and MOXY pricing. Moxy Foundation funds the Sale wallet. The Moxy Foundation may transfer one million MOXY from the Treasury to the Sale wallet. In conclusion, the Moxy Foundation will distribute MOXY and move it from internal cold wallets to public "Sale" wallets.

Token Lifecycle: A Moxy Club member often purchases MOXY through the Sale wallet. Next, the user must deposit MOXY for eSport gaming into their wallet's "Authorized Gaming Balance." The Authorized Gaming Balance's MOXY can be used in any Moxy-enabled game. When the user opens a game, a specific amount of this balance will be shown in the game and utilized, at the player's discretion, when they engage an eSport game mode.

eSport User Flow: Moxy Club membership is required. They must submit KYC paperwork after logging in. The user will automatically receive a wallet after verification. The wallet will pay membership fees. The first MOXY placed to the wallet will cover the Association membership fee. If the membership criterion is 5 MOXY, the member's wallet will redirect the initial 5 MOXY to the Moxy Foundation treasury wallet. One transaction or several transactions.

TOKENOMICS

For more information visit:

WEBSITE: https://moxy.io/ WHITEPAPER: https://moxy.io/whitepaper/ TWITTER: https://twitter.com/moxyio TELEGRAM: http://t.me/moxyofficial INSTAGRAM: https://www.instagram.com/moxy.io/ LINKEDIN: https://www.linkedin.com/company/Moxyio/ DISCORD: http://discord.gg/moxyio

AUTHOR

Forum Username: Java22 Forum Profile Link: https://bitcointalk.org/index.php?action=profile;u=3443255 BEP-20 Wallet Address: 0x39aEF5f1cf37c0f1d015435F592Ce632720cB713

[tapmora]

6 Micro-SaaS Ideas You Can Build (Solo!) in a Weekend

Let’s be real: not everyone wants to raise VC money, build a startup with 10 employees, or grind for years before seeing a dollar.

Sometimes, you just want a simple, tiny software product that solves a problem, and pays you monthly. That’s the magic of Micro-SaaS.

And the best part? With the right idea (and tools like AI + no-code), you can launch one this weekend. Solo.

Here are 6 Micro-SaaS ideas that are beginner-friendly, useful, and (yep) monetizable.

1. AI-Powered Email Summarizer for Gmail

People are drowning in emails. Build a simple tool that connects to Gmail and uses GPT to summarize unread emails daily into bullet points.

Tech stack: Google API + GPT API + simple frontend Monetize: $5–10/month Target user: Busy professionals, founders, freelancers

2. “Quiet Booking” Tool for Freelancers

Let clients book time with you, without showing your full calendar. Only show available blocks you want, with intake questions.

Tech stack: TidyCal + automation tools like Zapier + Stripe No-code possible: Yep Monetize: Monthly or per-booking fee

3. Habit Tracker with AI Accountability

A dead-simple habit tracker that lets users set goals and receive weekly AI-generated encouragement or nudges based on their inputs.

Bonus: Offer a “chat with your habit coach” GPT chatbot.

4. AI Resume Tailor

Upload your resume + job post → get a tailored version instantly. Could work as a Chrome extension or web app.

People will 100% pay to skip tailoring resumes over and over.

5. Podcast Show Notes Generator

Upload an MP3 → get clean, SEO-optimized show notes + timestamps + quote pullouts. Add GPT auto-titling and summaries.

Great for: Indie podcasters and agencies

6. Local Deal Finder (Location-Based)

Use public APIs to pull local discounts/deals/events into one dashboard or newsletter. Let people filter by interests or location.

Think: “Skyscanner but for local life.”

Tools You Can Use:

No-code: Softr, Glide, Bubble, Carrd

AI: ChatGPT API, Claude, ElevenLabs

Payments: Gumroad, Lemon Squeezy, Stripe

Automation: Zapier, Make, Pipedream

Final Thoughts

You don’t need a co-founder. You don’t need $50K. You need:

a real problem

a simple solution

a weekend

and some caffeine (probably)

Launch it small. Charge early. Iterate later. Micro-SaaS isn’t just possible solo, it’s ideal solo.

[elizabethiiregina]

Below is a technical prototype outline of a Logic Wiki system that organizes and distills human perceptual experience, summaries, and derived logic into a structured, queryable knowledge base. This system is designed for both human readability and machine digestibility.

🧠 Logic Wiki — Technical Prototype v0.1

🔧 Purpose

To capture perceptual events, summarize them in natural language, and extract actionable logic or reasoning patterns into modular, linkable articles — in a format usable by AI systems and human users alike.

🏗️ System Architecture Overview

🧱 Core Components

Component Description Event Ingestor Takes raw input (video, audio, biometric data, timestamped logs) Summary Generator Converts sequences into natural language descriptions Logic Extractor Converts summarized experience into structured rules or procedures Article Builder Stores perceptual summaries and logic in modular wiki-style format Knowledge Graph Engine Cross-links entities, tags, and topics across articles Query Interface Enables humans and AIs to search, filter, or simulate logic structures

📦 Data Structure (YAML-Based Schema Example)

Each wiki article is stored as a versioned YAML or JSON file with attached media references.id: article_0231 title: Responding to a Crying Infant created_at: 2025-07-17T14:23:00Z perceptual_data: video: /data/video/0231.mp4 audio: /data/audio/0231.wav biometrics: heart_rate: [78, 92, 110] galvanic_skin_response: [0.02, 0.05, 0.07] eye_tracking: /data/eye_gaze/0231.json summary: text: > At 2:13 PM, the subject heard a baby crying in a crowded room, paused conversation, approached the infant, and used calming speech and gestures. The crying subsided after 45 seconds. logic: conditions: - if: "audio.contains('crying_baby')" - and: "no_adult_in_range(2m)" - and: "subject.available == true" actions: - "approach(target=source_of_sound)" - "speak_tone('calming')" - "gesture('soothe')" reflection: emotion_label: concern intention: protect vulnerable life decision_rationale: > The subject recognized a distress cue and prioritized immediate social response over continuing the conversation. linked_articles: - article_0129 # Empathic Intervention - article_0083 # Infant Vocalization Responses - concept_emotion_concern

🔄 Logic Extraction Model

Can be based on:

Transformer-based event-to-logic converters (e.g., fine-tuned GPT)

Causal reasoning model: Perceptual Event → Intent → Action → Outcome

Predefined logic templates for common situation types

Example Output (from logic extractor):

def handle_crying_baby(perceptual_input): if perceptual_input.audio.contains("crying") and not perceptual_input.context.has_adult_nearby(): perform("approach") perform("speak", tone="calm") perform("gesture", type="soothe")

🔍 Query Layer

Human or AI agents can:

Ask: “How did the subject typically respond to emergencies?”

Filter: emotion_label: concern, context: social

Search: keyword, similarity match, logic chain pattern

Simulate: use logic chains as input for reinforcement learning or inference engines

🧠 Knowledge Graph & Linking

Each article contributes to a broader semantic map, linking:

Concepts (e.g., “concern,” “childcare,” “intervention”)

Situations (e.g., “conflict resolution,” “danger recognition”)

Decision rules and emotional signatures

Cross-individual patterns (when using this across multiple users)

Uses tools like:

Neo4j / GraphDB

RDF / OWL ontologies (for logic and context representation)

Embedding-based semantic linking (e.g., FAISS + sentence transformers)

🖼 Interface Design (High-Level UI)

Home Dashboard:

Search bar: “Show articles involving fear in public spaces”

Recent updates

Person profile summaries (per individual if system is multi-user)

Article View:

Video playback synced with:

Gaze heatmap

Emotion overlay

Logic block viewer

Edit/suggest logic rules (for humans)

AI Integration:

REST API for ingest and export

Chat-style QA for logic analysis (“What logic governs this decision?”)

🧪 Prototype Stack Suggestion

Layer Tool(s) UI React + TailwindCSS Backend API FastAPI or Flask DB / Storage PostgreSQL + S3 / GridFS Embeddings/Search FAISS, OpenAI embeddings, Haystack Logic Extraction LangChain / GPT-4 fine-tune Knowledge Graph Neo4j / RDFLib Media Sync OpenCV + ffmpeg + HTML5

🛡️ Ethics and Permissions Layer

Each article and perceptual record includes:

Consent metadata (consent_granted, scope, revokable)

Anonymization toggle

Access control (private, public, AI-use-only, etc.)

✅ Summary

This prototype describes a system that:

Accepts perceptual data from a human subject

Summarizes and organizes it into wiki-style logic articles

Extracts structured reasoning and decision logic

Links ideas semantically into a growing network of distilled intelligence

Enables learning, search, and simulation by both humans and AIs

Would you like a sample interface mockup, a code stub, or help implementing one component (like the article schema or logic extractor)?

[mantabridge]

Manta Bridge Explained: Architecture, Validators, Supported Tokens, and Use Cases

Manta Bridge is one of the most innovative privacy-focused cross-chain solutions in the crypto space today. Built on the principles of zero-knowledge proofs and decentralized infrastructure, it enables seamless and private asset transfers between blockchain networks—without sacrificing speed, decentralization, or scalability.

In this article, we explore the architecture, use cases, advantages, and ecosystem surrounding Manta Bridge, including Manta Pacific, Manta Airdrop, and the broader Manta Network.

🔍 What is Manta Bridge?

Manta Bridge is a cross-chain messaging and asset transfer protocol developed by the Manta Network to enable private and secure transfers of crypto assets between major blockchains such as Ethereum, BNB Chain, Polkadot, and Cosmos.

Unlike traditional bridges that expose user data and wallet history, Manta Bridge leverages zk-SNARKs (zero-knowledge succinct non-interactive arguments of knowledge) to encrypt and conceal transaction details—including wallet addresses, token amounts, and metadata.

Its privacy-first bridging mechanism is supported by a decentralized network of relayers who are incentivized to maintain the system’s efficiency, security, and censorship resistance.

⚙️ How Manta Bridge Works

The bridge operates using a three-step mechanism often referred to as Lock-Prove-Mint:

Lock: Assets on the source chain are either locked (in the case of wrapped assets) or burned (in the case of native bridging), and a zk-proof is generated off-chain to attest the event occurred.

Prove: Decentralized relayers validate and submit this proof to the destination chain’s smart contract without revealing any sensitive information.

Mint: Once the proof is verified on-chain, the asset is minted or unlocked on the destination chain.

This ensures full confidentiality while maintaining a strict 1:1 peg of the asset across chains.

🌉 Why Manta Bridge Matters

✅ Privacy by Design

Where most cross-chain platforms expose transactional data on public ledgers, Manta Bridge ensures all data is cryptographically hidden. It's the only major bridge designed with zk-native privacy from the ground up.

✅ High Throughput & Low Fees

Thanks to batched zk-Rollup architecture, Manta Pacific—an L2 solution built atop the bridge—reduces transaction costs dramatically, making Manta one of the most gas-efficient bridges on the market.

✅ Multi-Chain Support

Manta Bridge connects over a dozen blockchains, including:

Ethereum

BNB Smart Chain

Polkadot parachains

Cosmos zones

Polygon, Arbitrum, Optimism, and others

✅ Support for NFTs & Data

The bridge doesn't just handle fungible tokens. Users can transfer:

ERC-721 and ERC-1155 NFTs

Arbitrary on-chain data (e.g., governance payloads)

Cross-chain credentials and private metadata

🌐 Exploring the Manta Ecosystem

🔵 Manta Network

Manta Network is a modular blockchain ecosystem focused on privacy, scalability, and interoperability. It supports smart contracts, private DeFi, identity, and cross-chain bridges like Manta Bridge.

🟣 Manta Pacific

Manta Pacific is a ZK-powered Layer 2 chain that works natively with the bridge, supporting fast private dApps and DeFi protocols. It enables builders to deploy EVM-compatible smart contracts with full privacy support.

🪂 Manta Airdrop

The Manta Airdrop distributed tokens to early adopters and contributors in 2024, helping decentralize protocol governance. The airdrop incentivized relayer nodes, liquidity providers, and bridge testers—fueling rapid adoption.

🛠️ Features of Manta Bridge

🔐 zk-SNARK Privacy: Conceals sender, receiver, and asset amounts

⛓️ Cross-chain Token Transfers: ETH, USDC, BNB, DOT, NFTs, and more

🧩 Cross-chain Messaging: Governance proposals, DAO votes, etc.

⚙️ Permissionless Relayers: Anyone can run a node to help process bridges

🧪 Testnet & DevTools: SDKs, APIs, and a developer playground

Explore their GitHub Repository to learn more.

📖 How to Use Manta Bridge

Using Manta Bridge is straightforward and accessible:

Welcome to Manta Bridge

Connect your wallet (MetaMask, Keplr, Polkadot.js)

Select the source and destination chains

Choose the asset and amount

Approve the bridge contract to lock your token

Wait for zk-proof generation and relayer submission

Confirm redemption on the destination chain

📚 Authoritative Sources & Mentions

The Manta ecosystem has been featured across major crypto media outlets, including:

CoinDesk – Zero-Knowledge Privacy Comes to Cross-Chain Bridges

CoinMarketCap – MANTA Token Price & Analytics

CoinGecko – Manta Pacific Overview

These sources confirm Manta’s reputation as one of the most secure and scalable privacy bridges in Web3.

📌 Final Thoughts

Manta Bridge is revolutionizing the future of private cross-chain transfers. As DeFi continues to scale across chains, Manta delivers one of the few protocols that respects user privacy, developer composability, and security by design.

Whether you're bridging stablecoins between chains, transferring NFTs privately, or developing cross-chain dApps on Manta Pacific, the protocol provides the privacy infrastructure the blockchain world has been waiting for.

[justtryblockchain]

The Common Challenges in Smart Contract Development and How to Overcome Them

The Common Challenges in Smart Contract Development and How to Overcome Them

The blockchain revolution has ushered in a new era of automation and trustless transactions. At the core of this disruption lie Web3 smart contracts, self-executing programs that run on decentralized networks. These digital protocols offer immense transformative potential, yet they come with unique complexities. Unlocking their full power requires addressing the multifaceted challenges of blockchain smart contract development.

Inadequate Understanding of Smart Contract Logic

Many developers transitioning to blockchain misinterpret its architecture. The immutability of smart contracts means logic errors cannot be easily corrected after deployment.

How to overcome it:

Learn patterns like Checks-Effects-Interactions

Apply formal verification early

Start with modular, testable contract designs

Vulnerabilities and Security 

Even small mistakes in smart contract code can cause large-scale losses. Common flaws include reentrancy bugs, overflows, and front-running.

How to overcome it:

Follow secure design standards

Use vetted libraries like OpenZeppelin

Integrate tools such as Slither and MythX for audits

Testing and Audit 

Testing is often rushed or skipped, which leaves systems open to failure. Security audits are non-negotiable for production-ready code.

How to overcome it:

Build robust test suites with Hardhat or Truffle

Perform edge-case simulations

Conduct external audits from trusted firms

Scalability and Performance 

High gas fees and limited throughput affect how smart contracts perform on public blockchains.

How to overcome it:

Optimize logic for gas efficiency

Use Layer 2 solutions like Optimistic or zkRollups

Offload heavy computations using oracles

Integration Issues with Existing Systems

Smart contracts must often integrate with traditional systems and web services. This introduces interoperability challenges.

How to overcome it:

Use middleware like Chainlink or The Graph

Leverage event-driven designs

Secure all external APIs and data channels

Smart Contract Legal Issues and Compliance

Smart contract legal issues arise when code conflicts with legal expectations. Laws are interpretive; code is deterministic.

How to overcome it:

Involve legal professionals early

Include logic for dispute resolution

Stay compliant with regional blockchain regulations

Challenges in Solidity Smart Contract Development

Solidity is powerful but error-prone. Developers often struggle with memory handling, inheritance, and optimization.

How to overcome it:

Follow official Solidity best practices

Learn from community forums and code reviews

Use proven templates and gradually introduce complexity

Why Choose Justtry Technologies

As a leading smart contract development company, Justtry Technologies delivers secure, scalable, and industry-compliant solutions.

We specialize in:

Web3 applications built across DeFi, gaming, healthcare, and logistics

Deep security knowledge and best practices in Solidity smart contract engineering

Transparent development milestones and client collaboration

End-to-end smart contract development services tailored for your business

In a world where code replaces traditional contracts, are you ready to build with resilience and foresight?

Visit: https://justtrytech.com/web3-smart-contract-development-company/, https://justtrytech.com/smart-contract-development-company/

Contact us: +91 9500139200

Mail address: justtrytechnologies@gmail.com

[scrapegg]

How Can You Extract Data from Twitter Without Breaking the Rules?

In the age of data-driven decision-making, Twitter has become a goldmine of real-time insights. Whether you're a marketer, researcher, or developer, the ability to extract data from Twitter can open doors to better analysis, strategy, and audience understanding. But how exactly can you do this effectively—and ethically?

Why Extract Twitter Data?

Twitter holds massive value in its public tweets, trends, hashtags, and user behavior. From tracking brand mentions to analyzing sentiment or monitoring events, accessing this data can fuel smarter business or academic strategies.

Method 1: Use the Twitter API

One of the most reliable and scalable ways to extract data from twitter api is through the Twitter API. Twitter offers multiple APIs—such as the standard, academic, and premium tiers—that allow you to retrieve structured data like tweets, user profiles, trends, and more.

If you're a developer, using the API to scrap data from Twitter gives you control over the type and volume of data you collect. It also ensures compliance with Twitter's terms of service, provided you follow rate limits and usage policies.

🔧 Tip: Always register a developer account and authenticate using OAuth tokens to access the API securely.

Method 2: Twitter Web Scraping

While APIs are ideal, they can be limited based on access levels and data caps. This is where Twitter web scraping comes into play. Web scraping involves programmatically accessing Twitter’s public-facing web pages and extracting the visible content.

However, web scraping must be handled with caution. Twitter's terms of service generally discourage automated scraping without permission. Still, for academic or light usage scenarios, it’s possible to gather basic tweet data—like tweet text, usernames, and timestamps—using tools like Python with BeautifulSoup or Selenium.

💡 Twitter Web Scraping Tip: Always respect robots.txt files, avoid scraping too frequently, and rotate IPs to avoid getting blocked.

Choosing Between API and Scraping

When deciding whether to use the Twitter API or go with Twitter web scraping, ask yourself:

Do I need real-time or historical data?

What kind of data am I after (tweets, users, hashtags)?

Am I comfortable coding with APIs, or do I prefer a scraping script?

Tools That Can Help

Here are a few tools and libraries that simplify Twitter web scraping and API data extraction:

Tweepy – A Python library for easy API integration.

SNScrape – Ideal for scraping tweets without using the Twitter API.

BeautifulSoup + Selenium – Useful for building custom scrapers for the web interface.

Final Thoughts

Whether you're using an API to scrap data from Twitter or relying on Twitter web scraping, the key is to stay compliant, ethical, and efficient. The ability to extract data from Twitter has countless applications, but it's crucial to understand the limitations and risks of each method.

By following the right approach, respecting platform guidelines, and using the best tools, you can unlock valuable insights from one of the most influential social platforms in the world.

[this-week-in-rust]

This Week in Rust 562

Hello and welcome to another issue of This Week in Rust! Rust is a programming language empowering everyone to build reliable and efficient software. This is a weekly summary of its progress and community. Want something mentioned? Tag us at @ThisWeekInRust on X (formerly Twitter) or @ThisWeekinRust on mastodon.social, or send us a pull request. Want to get involved? We love contributions.

This Week in Rust is openly developed on GitHub and archives can be viewed at this-week-in-rust.org. If you find any errors in this week's issue, please submit a PR.

Want TWIR in your inbox? Subscribe here.

Updates from Rust Community

Official

2024 Leadership Council Survey

Embedded Working Group Community Micro Survey

Foundation

What's in Store at RustConf 2024

Project/Tooling Updates

git-cliff 2.5.0 is released!

Ferrocene 24.08.0 now available!

Go wild: Wildcard support in Rules and a new open-source wildcard crate

Why am I writing a Rust compiler in C?

Current zlib-rs performance

Bon builder generator 2.0 release 🎉

Meilisearch 1.10

Observations/Thoughts

Rust dylib rabbit holes

I sped up serde_json strings by 20%

Using StringView / German Style Strings to Make Queries Faster: Part 1 - Reading Parquet

Rust as My First Language

Doctests - How were they improved?

MiniJinja: Learnings from Building a Template Engine in Rust

Standards for use of unsafe Rust in the kernel

Rust vs C++: A Real-World Perspective (interview with Tyler Weaver)

A Piece of UNIX History in Rust

Why Amazon, Cloduflare and Discord are building servers in Rust but you should probably not

Rust Walkthroughs

Let the API protect you

Packaging a Rust Program for Fedora

Building a Bevy Plugin for Rolling Dice

[video] Implementing a Lox interpreter in Rust

[video] Command line tools: Implementing wc in Rust

[video] Explore Linux TTY, process, signals w/ Rust - Part 1/3 (background info)

Research

On the Impact of Memory Safety on Fast Network I/O

Miscellaneous

Can DARPA’s TRACTOR Pull C to Rust for Memory-Safe Overhaul?

Crafting a Blockchain in Go and Rust: A Comparative Journey — Private keys, Public Keys and Signatures [Part 1]

[video] A Multiplatform Mobile Navigation SDK with Rust at the Core

Crate of the Week

This week's crate is wtx, a batteries-included web application framework.

Thanks to Caio for the self-suggestion!

Please submit your suggestions and votes for next week!

Calls for Testing

An important step for RFC implementation is for people to experiment with the implementation and give feedback, especially before stabilization. The following RFCs would benefit from user testing before moving forward:

RFCs

No calls for testing were issued this week.

Rust

No calls for testing were issued this week.

Rustup

No calls for testing were issued this week.

If you are a feature implementer and would like your RFC to appear on the above list, add the new call-for-testing label to your RFC along with a comment providing testing instructions and/or guidance on which aspect(s) of the feature need testing.

Call for Participation; projects and speakers

CFP - Projects

Always wanted to contribute to open-source projects but did not know where to start? Every week we highlight some tasks from the Rust community for you to pick and get started!

Some of these tasks may also have mentors available, visit the task page for more information.

No Calls for participation were submitted this week.

If you are a Rust project owner and are looking for contributors, please submit tasks here or through a PR to TWiR or by reaching out on X (formerly Twitter) or Mastodon!

CFP - Events

Are you a new or experienced speaker looking for a place to share something cool? This section highlights events that are being planned and are accepting submissions to join their event as a speaker.

No Calls for papers or presentations were submitted this week.

If you are an event organizer hoping to expand the reach of your event, please submit a link to the website through a PR to TWiR or by reaching out on X (formerly Twitter) or Mastodon!

Updates from the Rust Project

429 pull requests were merged in the last week

add Trusty OS as tier 3 target

CFI: erase regions when projecting ADT to its transparent non-1zst field

add missing module flags for CFI and KCFI sanitizers

repr_transparent_external_private_fields: special-case some std types

add a special case for CStr/CString in the improper_ctypes lint

avoid extra cast()s after CStr::as_ptr()

const checking: properly compute the set of transient locals

ctfe: make CompileTimeInterpCx type alias public

detect * operator on !Sized expression

do not ICE on non-ADT rcvr type when looking for crate version collision

don't consider locals to shadow inner items' generics

don't generate functions with the rustc_intrinsic_must_be_overridden attribute

don't trigger refinement lint if predicates reference errors

fix extern crates not being hidden with doc(hidden)

fix handling of macro arguments within the dropping_copy_types lint

implement -Z embed-source (DWARFv5 source code embedding extension)

improve diagnostic-related lints: untranslatable_diagnostic & diagnostic_outside_of_impl

interpret: immTy: tighten sanity checks in offset logic

lint on tail expr drop order change in Edition 2024

llvm-wrapper: adapt for LLVM 20 API changes

make ArgAbi::make_indirect_force more specific

make writes_through_immutable_pointer a hard error

more work on zstd compression

mv build_reduced_graph_for_external_crate_res into Resolver

pal/hermit: correctly round up microseconds in Thread::sleep

panicking: improve hint for Miri's RUST_BACKTRACE behavior

point at explicit 'static obligations on a trait

pretty-print own args of existential projections (dyn-Trait w/ GAT constraints)

print the generic parameter along with the variance in dumps

remove invalid TyCompat relation for effects

safe transmute: gracefully bubble-up layout errors

skip updating when external binding is existed

use assert_unsafe_precondition! in AsciiChar::digit_unchecked

use a LocalDefId in ResolvedArg

use old ctx if has same expand environment during decode span

use subtyping for UnsafeFnPointer coercion, too

miri: provenance_gc: fix comment

miri: readdir_r shim: assume FreeBSD v12+

miri: avoid extra copy by using retain_mut and moving the deletion into the closure

miri: disable tree traversal optimization that is wrong due to lazy nodes

miri: epoll: add a EINVAL case

miri: epoll: handle edge case for epoll_ctl

miri: fix a misleading comment in tests/pass/tree_borrows/tree-borrows.rs

miri: fix calling pipe, pipe2, socketpair with a pointer-to-array

miri: implement SHA256 SIMD intrinsics on x86

miri: make Tree Borrows Provenance GC no longer produce stack overflows

miri weak memory emulation: put previous value into initial store buffer

stabilize opaque type precise capturing (RFC 3617)

stabilize const_fn_floating_point_arithmetic

stabilize iter::repeat_n

stabilize feature char_indices_offset

implement debug_more_non_exhaustive

add Box::as_ptr and Box::as_mut_ptr methods

add const_cell_into_inner to OnceCell

add f16 and f128 inline ASM support for aarch64

add a precondition check for Layout::from_size_align_unchecked

add implementations for unbounded_shl/unbounded_shr

change neutral element of <fNN as iter::Sum> to neg_zero

library: move unstable API of new_uninit to new features

fix thread::sleep Duration-handling for ESP-IDF

fix: fs::remove_dir_all: treat internal ENOENT as success

put Pin::as_deref_mut in impl Pin<Ptr> / rearrange Pin methods

implement ptr::fn_addr_eq

hashbrown: deprecate the raw entry API in favor of HashTable

hashbrown: rework the Entry API

cargo: mdman: Normalize newlines when rendering options

cargo resolve: Dont show locking workspace members

cargo: be more permissive while packaging unpublishable crates

cargo: add matches_prerelease semantic

cargo: -Cmetadata includes whether extra rustflags is same as host

cargo: doctest respects Cargo's color options

cargo: limiting pre-release match semantics to use only on OptVersionReq::Req

cargo: log details of failure if no errors were seen

cargo: more helpful missing feature error message

rustdoc-search: use tighter json for names and parents

rustdoc: animate the :target highlight

rustdoc: show exact case-sensitive matches first

rustdoc: Generate source link on impl associated types

clippy: declare_interior_mutable_const: Ignore pointer types

clippy: add new too_long_first_doc_paragraph first paragraph lint

clippy: add new lint: used_underscore_items

clippy: check std::panic::panic_any in panic lint

clippy: diverging subexpression lint should not fire on todo!()

clippy: fix manual_range_patterns case with one element at OR

clippy: fix confusing message in double_must_use lint

clippy: fix suggestion unnecessary_lazy_eval

clippy: ignore underscore-prefixed args for needless_pass_by_value lint

clippy: rewrite empty_line_after_doc_comments and empty_line_after_outer_attr, move them from nursery to suspicious

clippy: start removing snippet_opt in favor of get_source_text

rust-analyzer: add new assist toggle_macro_delimiter

rust-analyzer: allow declaring cfg groups in rust-project.json, to help sharing common cfgs

rust-analyzer: add workspace level config to ratoml

rust-analyzer: always show error lifetime arguments as '_

rust-analyzer: don't enable the search fast path for short associated functions when a search scope is set

rust-analyzer: expand proc-macros in workspace root, not package root

rust-analyzer: fix "Unwrap block" assist with block modifiers

rust-analyzer: fix Return Type Syntax to include .. (i.e. method(..) and not method()) as specified in the RFC

rust-analyzer: fix metadata retrying eating original errors

rust-analyzer: fix trait method completions not acknowledging Deref impls

rust-analyzer: improve proc-macro panic message and workspace loading failure diagnostic

rust-analyzer: run flycheck without rev_deps when target is specified

rust-analyzer: rust-analyzer should watch build files from rust-project.json

rust-analyzer: wrong Self: Sized predicate for trait assoc items

rust-analyzer: wrong Sized predicate for generic_predicates_for_param

rust-analyzer: implement floating point casts in const eval

rust-analyzer: perf: speed up search for short associated functions, especially very common identifiers such as new

rust-analyzer: remove the ability to configure the user config path

Rust Compiler Performance Triage

Approved RFCs

Changes to Rust follow the Rust RFC (request for comments) process. These are the RFCs that were approved for implementation this week:

No RFCs were approved this week.

Final Comment Period

Every week, the team announces the 'final comment period' for RFCs and key PRs which are reaching a decision. Express your opinions now.

RFCs

[disposition: merge] crates.io: Remove dev-dependencies from the index

[disposition: merge] Mergeable rustdoc cross-crate info

[disposition: merge] Guard Patterns

Tracking Issues & PRs

Rust

[disposition: merge] Proposal: stabilize const_refs_to_static

[disposition: merge] Check WF of source type's signature on fn pointer cast

[disposition: merge] rustdoc: add header map to the table of contents

[disposition: merge] doc: Make block of inline Deref methods foldable

Cargo

No Cargo Tracking Issues or PRs entered Final Comment Period this week.

Language Team

No Language Team Tracking Issues or PRs entered Final Comment Period this week.

Language Reference

No Language Reference RFCs entered Final Comment Period this week.

Unsafe Code Guidelines

No Unsafe Code Guideline Tracking Issues or PRs entered Final Comment Period this week.

New and Updated RFCs

[new] #[derive(Default)] on enum variants with fields

[new] [RFC] Default field values

[new] Simplify lightweight clones, including into closures and async blocks

Upcoming Events

Rusty Events between 2024-08-28 - 2024-09-25 🦀

Virtual

2024-08-28 | Virtual (Tel Aviv, IL) | Code Mavens

Command Line Tools: Implementing wc in Rust (English, Virtual)

2024-08-29 | Virtual (Berlin, DE) | OpenTechSchool Berlin + Rust Berlin

Rust Hack and Learn | Mirror: Rust Hack n Learn Meetup

2024-08-29 | Virtual (Tel Aviv, IL) | Code Mavens

Rust Source Code Reading: The thousands crate (English)

2024-09-03 | Virtual (Buffalo, NY, US) | Buffalo Rust Meetup

Buffalo Rust User Group

2024-09-04 | Virtual (Indianapolis, IN, US) | Indy Rust

Indy.rs - Typestate Pattern in Rust: With a Strict Builder Example

2024-09-05 | Virtual | LambdaClass

Meetup Rust Septiembre [Spanish]

2024-09-05 | Virtual (Charlottesville, NC, US) | Charlottesville Rust Meetup

Crafting Interpreters in Rust Collaboratively

2024-09-05 | Virtual (Nürnberg, DE) | Rust Nuremberg

Rust Nürnberg online

2024-09-10 | Virtual (Dallas, TX, US) | Dallas Rust

Second Tuesday

2024-09-10 - 2024-09-13 | Hybrid: Virtual and In-Person (Montreal, QC, CA) | Rust Conf

Rust Conf 2024

2024-09-12 | Virtual (Berlin, DE) | OpenTechSchool Berlin + Rust Berlin

Rust Hack and Learn | Mirror: Rust Hack n Learn Meetup

2024-09-12 | Virtual (Rotterdam, NL) | Bevy Game Development

Bevy Meetup #6

2024-09-16 | Virtual | Women in Rust

👋 Community Catch Up

2024-09-17 | Virtual (Washington, DC, US) | Rust DC

Mid-month Rustful

2024-09-18 | Virtual and In-Person (Vancouver, BC, CA) | Vancouver Rust

Cells

2024-09-18 - 2024-09-20 | Hybrid - Virtual and In-Person (Vienna, AT) | Linux Plumbers Conference

Rust Microconference in LPC 2024

2024-09-19 | Virtual (Charlottesville, NC, US) | Charlottesville Rust Meetup

Crafting Interpreters in Rust Collaboratively

2024-09-19 | Virtual and In-Person (Seattle, WA, US) | Seattle Rust User Group

September Meetup

2024-09-24 | Virtual (Dallas, TX, US) | Dallas Rust

Last Tuesday

Africa

2024-09-06 | Kampala, UG | Rust Circle Kampala

Rust Circle Meetup

Asia

2024-09-09 | Ramat Gan, IL | Coralogix

Rust as Scale

2024-09-14 | Bangalore, IN | Rust Bangalore

September 2024 Rustacean meetup

Europe

2024-08-28 | Frankfurt (Main), DE | Rust Rhein Main

Rust Frankfurt WebAssembly

2024-08-29 | Berlin, DE | OpenTechSchool Berlin + Rust Berlin

Rust and Tell - The social Beergarden.

2024-08-29 | Copenhagen, DK | Copenhagen Rust Community

Rust meetup #50 sponsored by Adapt Agency

2024-09-04 | Oxford, UK | Oxfrod Rust Meetup Group

More Rust - Generics, constraints, safety.

2024-09-11 | Reading, UK | Reading Rust Workshop

Reading Rust Meetup

2024-09-17 | Leipzig, DE | Rust - Modern Systems Programming in Leipzig

Topic TBD

2024-09-17 | Trondheim, NO | Rust Trondheim

Making AI-models perform tasks, in Rust!

2024-09-18 | Moravia, CZ | Rust Moravia

Rust Moravia Meetup (September 2024)

2024-09-18 | Vienna, AT + Virtual | Linux Plumbers Conference

Rust Microconference in LPC 2024 (Sep 18-20)

2024-09-23 | Bratislava, SK | Bratislava Rust Meetup Group

Rust Meetup by Sonalake #6

North America

2024-08-28 | Austin, TX, US | Rust ATX

Rust Lunch - Fareground

2024-08-29 | Nashville, TN, US | Music City Rust Developers

Music City Rust Developers : placeholder

2024-08-29 | Chicago, IL, US | Deep Dish Rust

Rust Hack Night/Happy Hour

2024-08-31 | Cambridge, MA, US | Boston Rust Meetup

Central Cambridge Rust Lunch, Aug 31

2024-09-05 | Mountain View, CA, US | Mountain View Rust Meetup

Rust Meetup at Hacker Dojo

2024-09-05 | Portland, OR, US | PDX Rust

PDX Rust September!

2024-09-05 | St. Louis, MO, US | STL Rust

Lifetimes

2024-09-07 | Longview, TX, US | Longview Code and Coffee

Longview Code and Coffee

2024-09-08 | Cambridge, MA, US | Boston Rust Meetup

Northeastern Rust Lunch, Sep 8

2024-09-10 - 2024-09-13 | Hybrid: Virtual and In-Person (Montreal, QC, CA) | Rust Conf

Rust Conf 2024

2024-09-11 | Boulder, CO, US | Boulder Rust Meetup

Boulder Elixir Meetup

2024-09-16 | Cambridge, MA, US | Boston Rust Meetup

Somerville Union Square Rust Lunch, Sep 16

2024-09-17 | San Francisco, CA, US | San Francisco Rust Study Group

Rust Hacking in Person

2024-09-18 | Virtual and In-Person (Vancouver, BC, CA) | Vancouver Rust

Cells

2024-09-19 | Virtual and In-Person (Seattle, WA, US) | Seattle Rust User Group

September Meetup

2024-09-21 | Longview, TX, US | Longview Code and Coffee

Longview Code and Coffee

2024-09-24 | Detroit, MI, US | Detroit Rust

Rust Community Meetup - Ferndale

2024-09-25 | Austin, TX, US | Rust ATX

Rust Lunch - Fareground

Oceania

2024-08-28 | Sydney, NSW, AU | Rust Sydney

Stuff ⚡ And Crabs 🦀

If you are running a Rust event please add it to the calendar to get it mentioned here. Please remember to add a link to the event too. Email the Rust Community Team for access.

Jobs

Please see the latest Who's Hiring thread on r/rust

Quote of the Week

... opaque number sequences (\<GitHub> "issue numbers") are not very informative about what is behind that pointer, and pretending they are is harmful. People could provide, instead, actual reasons for things, which do not require dereferencing random pointers, which thrashes cache.

– Jubilee on rust-internals

Thanks to Anton Fetisov for the suggestion!

Please submit quotes and vote for next week!

This Week in Rust is edited by: nellshamrell, llogiq, cdmistman, ericseppanen, extrawurst, andrewpollack, U007D, kolharsam, joelmarcey, mariannegoldin, bennyvasquez.

Email list hosting is sponsored by The Rust Foundation

Discuss on r/rust