Marzio Stanziola

Web developer, WordPress evangelist, practicing maidiac.  

"Second star to the right, and straight on 'till morning" - James T. Kirk

[Cipher @Cipher_twt]

Lmao 🤣

[le.hl @0xleegenz]

How job hunting look likes in 2026:

The office: Closed
The recruiter: Autobot
The interview: Auto reject email
The salary: low to 0
The roaster: 7 days/week till 10 PM
The job description: Fake
The job position: 20 years experience for entry level
Your data: Sold for AI company

[Spill The Memes @SpillTheMemes]

😂

[openSUSE Linux @openSUSE]

🌍 #Digital #sovereignty isn't a niche concern anymore; it's the new norm. Find out what executives across industries are saying about #AI, #resilience & autonomy. #oSC26 #openSUSE #Linux #OpenSource https://t.co/a4EEY7pHzD

[Twonks @twonkscomics]

Grown up

[Proton VPN @ProtonVPN]

We hope everyone in Guinea is able to evade the social media blackout, times like these are exactly why Proton VPN remains free.

[LinkedIn Lunatics @LinkedInLunat1c]

Trees are overrated.

[openSUSE Linux @openSUSE]

Coming to this year's #openSUSE Conference? Use our community sponsor #Mapforge's map of #oSC26 to get familiar with the layout of the venue. #OpenSource #Linux https://t.co/5NGtO4Z2y6

[Bitcoin Teddy @Bitcoin_Teddy]

Corporation: "We made $4B but spent $3.9B so we only owe taxes on $100M."
Government: "Totally reasonable."

You: "I made $60K but spent $58K on survival."
Government: "You owe taxes on $60K."
You: "That's not—"
Government: "File by May 15."

[Then vs Now @ThenvsNowPic1]

Phones back then vs Phones now

[Tuta @TutaPrivacy]

Today is the day: The European Commission is expected to publish the EU Tech Sovereignty Package. 🇪🇺

And the demand is clear. When purchasing software products, European authorities must prioritize

- Open source
- Buy European

The Americans buy American, the Chinese buy Chinese, when will Europe start to support its own industry?

The EU Tech Sovereignty Package can be a turning point for #digital #sovereignty.

But will they be bold enough?

👉 Find out more here: https://t.co/1g4kC5hvLR
📝 Read the letter and co-sign: https://t.co/tqV6lk8ID0

#OpenSourceFirst #DigitalSovereignty #TechSovereignty

[IT Guy @T3chFalcon]

Most people pay with their phones at checkout without thinking twice. But Apple and Google handle these payments in different ways, and those differences can affect your privacy.

Here’s how it works.

Apple Pay: Your Card Never Leaves the Device

When you add a credit card to Apple Pay, your real card number is never stored on Apple’s servers. Instead, Apple sends your card information to a secure chip inside your device called the Secure Enclave, which turns it into a Device Account Number (DAN).

The DAN acts like a temporary identity for your card. It is unique to your device, cannot be used by anyone else, and is kept separate from your real card number. When you make a payment, your iPhone sends the DAN to the payment terminal or online store. The bank then matches the DAN to your real account and completes the transaction.

Your real card number never goes to a server or travels over a network. It stays encrypted on a chip in your device, and Apple cannot access it.

This is a real example of privacy by design. There is little risk for hackers because even if someone breaks into a retailer’s payment system, all they get is a DAN that won’t work on any other device.

Google Pay: Convenient, But With a Tradeoff

Google Pay works well but uses a different system. When you add your card, your information is sent to and stored on Google’s servers. Google then creates a Payment Token used for your transactions.

That token goes from your phone to the online store, then back to Google’s servers. Finally, your real card information is sent to your bank to complete the purchase.

Your data is tokenized and encrypted. Google’s security is excellent, and the risk for most people is low. But privacy advocates should consider:

Google holds your card data. On their servers. Indefinitely.

This means your financial information is stored by one of the world’s biggest advertising and data companies. Even if Google never misuses your data, it becomes a valuable target. If Google’s payment system were breached, the impact would be much bigger than a breach at a single store.

Architecture Is Privacy
This isn’t just about Apple and Google as brands. It’s about two very different ways of handling your data.

Apple’s approach is decentralized and keeps your data on your own device. Google’s approach is cloud-based, so your data is stored on their servers.

As someone who cares about privacy, I always ask: Where does the data live? Who controls it? What happens if something goes wrong? On these questions, Apple Pay’s design is stronger because of how it’s built.

What You Should Actually Do
If you use an iPhone, you can trust Apple Pay. Its tokenization system is one of the best ways to protect your payment privacy right now.

If you use Android, Google Pay is still safer than swiping your physical card since tokenization protects you from most retail data breaches. Just remember the tradeoff: your card data is stored on Google’s servers, so keep that in mind when considering your overall digital privacy.

In both cases, try to use mobile payments instead of physical cards whenever you can. You shouldn’t have to give your full card number to a checkout system anymore.

[SHILL HOUSE @shillhousecom]

😂😂