TechnicalTrader

في عام 2013، قال رجل يدعى دافنشي جيريمي، الذي كان يوتيوبر ومستخدمًا مبكرًا لعملة البيتكوين، للناس أن يستثمروا فقط 1 دولار في البيتكوين. في ذلك الوقت، كانت تكلفة البيتكوين حوالي 116 دولار. قال إن هذا كان مخاطرة صغيرة لأنه حتى لو أصبحت البيتكوين بلا قيمة، فلن يخسروا سوى 1 دولار. ولكن إذا زادت قيمة البيتكوين، فقد يجلب ذلك مكافآت كبيرة. للأسف، لم يستمع الكثير من الناس إليه في ذلك الوقت.
اليوم، ارتفع سعر البيتكوين كثيرًا، حيث وصل إلى أكثر من 95,000 دولار في أعلى نقطة له. الأشخاص الذين أخذوا نصيحة جيريمي وشراء البيتكوين أصبحوا الآن أغنياء جدًا. بفضل هذا الاستثمار المبكر، يعيش جيريمي الآن حياة فاخرة مع اليخوت والطائرات الخاصة والسيارات الفاخرة. قصته تظهر كيف أن الاستثمارات الصغيرة في أشياء جديدة يمكن أن تؤدي إلى مكاسب كبيرة.

في الآونة الأخيرة، أثناء تناول串 مع بعض الأصدقاء الذين يركزون على نظام Solana البيئي، تحدثنا عن موضوع جعلني أشعر بالحنين، حيث كان الجميع يشتكي من أن مسار Layer 1 الحالي عالق في نوع من "حلقة مفرغة من الرتابة". سواء كان Ethereum القديم أو الشبكات الثانوية التي تشهد رواجًا، عندما تواجه تقلبات السوق الحقيقية، فإن تلك السعة المحدودة والتأخيرات التي تسبب ضغط الدم المرتفع تُعتبر سخرية من عبارة "التمويل اللامركزي". بينما أشاهد عرض النطاق الترددي البائس لـ Ethereum الرئيسي الذي يبلغ بضع عشرات من TPS، أو تلك الحلول التوسعية التي تدعي الأداء العالي ولكنها تنهار بشكل جماعي أو تتعرض للازدحام الجنوني أمام 5000 TPS، أشعر دائمًا أننا بعيدون عن قوة الصناعة التي تصل إلى مئة ألف عملية في الثانية مثل Nasdaq. هذه الضعف الجوهري، عند مواجهة المنافسات ذات التردد العالي في النظام المالي العالمي، يبدو كما لو أنك تحمل أسلحة قديمة في مواجهة صفوف الدبابات، ليس فقط بفعالية منخفضة، بل يجعل ما يُسمى السيولة المتقدمة كالشبح في الماء، وزهرة في المرآة.

I was looking through some old digital files the other day and realized how many things I have lost over the years because a service shut down or I forgot to pay a monthly bill. It is a strange feeling to realize your personal history is held by companies that do not really know you. I started using Walrus because I wanted a different way to handle my data that felt more like owning a physical box in a real room. It is a storage network that does not try to hide the reality of how computers work behind a curtain.
You know how it is when you just want a file to stay put without worrying about a middleman. In this system everything is measured in epochs which are just blocks of time on the network. When I put something into storage I can choose to pay for its life for up to two years. It was a bit of a reality check to see a countdown on my data but it makes sense when you think about it. If you want something to last forever you have to have a plan for how to keep the lights on.
"Nothing on the internet is actually permanent unless someone is paying for the electricity."
I realized that the best part about this setup is that it uses the Sui blockchain to manage the time. I can actually set up a shared object that holds some digital coins and it acts like a battery for my files. Whenever the expiration date gets close the coins are used to buy more time automatically. It is a relief to know I can build a system that takes care of itself instead of waiting for an email saying my credit card expired and my photos are gone.
The rules for deleting things are also very clear which I appreciate as a user who values my space. When I upload a blob I can mark it as deletable. This means if I decide I do not need it later I can clear it out and the network lets me reuse that storage for something else. It is great for when I am working on drafts of a project. But if I do not mark it that way the network gives me a solid guarantee that it will be there for every second of the time I paid for.
"A guarantee is only as good as the code that enforces the storage limits."
One thing that surprised me was how fast I could get to my data. Usually these kinds of networks are slow because they have to do a lot of math to put your files back together. But Walrus has this feature called partial reads. It stores the original pieces of the file in a few different spots. If the network can see those pieces it just hands them to me directly without any extra processing. It makes the whole experience feel snappy and responsive even when I am dealing with bigger files.
I also had to learn how the network handles stuff it does not want to keep. There is no central office that censors what goes onto the network. Instead every person running a storage node has their own list of things they refuse to carry. If a node finds something it does not like it can just delete its pieces of that file and stop helping. As long as most of the nodes are fine with the file it stays available for everyone to see.
"The network decides what to remember and what to forget through a messy democratic process."
It is interesting to see how the system gets better as it grows. Most platforms get bogged down when too many people use them but this one is designed to scale out. When more storage nodes join the network the total speed for writing and reading actually goes up. It is all happening in parallel so the more machines there are the more bandwidth we all get to share. It feels like a community effort where everyone bringing a shovel makes the hole get dug faster.
"Capacity is a choice made by those willing to pay for the hardware."
I think the reason I keep using this project is because it treats me like an adult. It does not promise me magic or tell me that storage is free when it clearly is not. It gives me the tools to manage my own digital footprint and shows me exactly how the gears are turning. There is a certain peace of mind that comes from knowing exactly where your data is and how long it is going to stay there. It makes the digital world feel a little more solid and a little less like it could vanish at any moment.
"Data ownership is mostly about knowing exactly who is holding the pieces of your life."
I have started moving my most important documents over because I like the transparency of the whole process. I can check the status of my files through a light client without needing to trust a single company to tell me the truth. It is a shift in how I think about my digital life but it is one that makes me feel much more secure. Having a direct relationship with the storage itself changes everything about how I value what I save.
what you think about this? don't forget to comment 💭
Follow for more content 🙂
$WAL #Walrus @WalrusProtocol

اكتشفت بالطريقة الصعبة لماذا والروس مختلف. حدث ذلك يوم الثلاثاء عندما كانت شبكتي المحلية تعمل ككارثة كاملة. كنت أحاول تحميل ملف كبير وتوفي نصف اتصالي أثناء البث. عادةً ما يعني ذلك أن الملف تالف أو يجب أن أبدأ من جديد من الصفر لأن البيانات لم تصل إلى كل الأماكن التي كان من المفترض أن تذهب إليها.
في معظم الأنظمة إذا تعطل عقدة أو تعطلت الإنترنت أثناء حفظ شيء ما، تبقى البيانات في هذا الفراغ الغريب. لكن مع والروس لاحظت شيئًا غريبًا. على الرغم من أن اتصالي كان يفشل، استمر النظام في العمل. شعرت أن الشبكة كانت تساعدني فعليًا في تصحيح أخطائي في الوقت الفعلي.

I have been looking for a way to save my files without relying on the big tech companies that seem to own everything we do online. I finally started using Walrus and it changed how I think about digital storage. You know how it is when you upload a photo to a normal cloud service and just hope they do not lose it or peek at it. This feels different because it is a decentralized secure blob store which is just a fancy way of saying it breaks your data into tiny pieces and scatters them across a bunch of different computers. I realized that I do not have to trust one single person or company anymore because the system is designed to work even if some of the nodes go offline or act up.

When I first tried to upload something I noticed the process is a bit more involved than just dragging and dropping a file. It starts with something called Red Stuff which sounds like a brand of soda but is actually an encoding algorithm. It takes my file and turns it into these things called slivers. I found out that the system also uses something called RaptorQ codes to make sure that even if some pieces get lost the whole file can still be put back together.
"The biggest lie in the cloud is that your data is ever truly yours."
That is the first thing I realized when I started diving into how this works. With this project I actually feel like I have control. After my computer finishes the encoding it creates a blob id which is basically a unique fingerprint for my file. Then I have to go to the Sui blockchain to buy some space. It is like paying for a parking spot for my data. I tell the blockchain how big the file is and how long I want it to stay there. Once the blockchain gives me the green light I send those little slivers of data out to the storage nodes.
I learned that these nodes are just independent computers sitting in different places. Each one takes a piece and then sends me back a signed receipt. I have to collect a specific number of these receipts to prove that my file is actually safe. Once I have enough I send a certificate back to the blockchain. This moment is what they call the point of availability. It is the exact second where I can finally breathe easy and delete the file from my own hard drive because I know it is living safely on the network.
"Storage is not just about keeping files but about proving they still exist."
Using this system makes you realize that most of our digital lives are built on pinky promises. With this project the blockchain acts like a manager that keeps everyone honest. If a node forgets my data or tries to delete it early the blockchain knows. There is a lot of talk about shards and virtual identities in the technical documents but as a user I just see it as a giant safety net. Even if a physical storage node is huge it might be acting as many smaller virtual nodes to keep things organized. It is just the way things are in this new kind of setup.
When I want my file back the process is surprisingly fast. I do not have to talk to every single node. I just ask a few of them for their slivers and once I have enough I can reconstruct the original file. The cool thing is that the math behind it makes sure that if the file I put together does not match the original fingerprint the system rejects it. This means no one can secretly swap my cat video for a virus without me knowing immediately.
"A system is only as strong as the math that keeps the nodes in line."
I used to worry about whether decentralized stuff would be too slow for regular use. But they have these things called aggregators and caches that help speed things up for popular files. If everyone is trying to download the same thing the system can handle the traffic without breaking a sweat. It feels like the internet is finally growing up and moving away from the old way of doing things where everything was stored in one giant warehouse that could burn down or be locked away.
"You should not have to ask for permission to access your own memories."
Every time I upload a new project or a batch of photos I feel a little more secure. It is not about being a computer genius or understanding every line of code in the Merkle trees or the smart contracts. It is about the reality of knowing that my data is not sitting on a single server in a basement somewhere. It is spread out and protected by a committee of nodes that have a financial reason to keep my stuff safe.
"True privacy is found in the pieces that no one person can read alone."
I like that I can go offline and the network just keeps humming along. The nodes are constantly listening to the blockchain and if they realize they are missing a piece of a file they go through a recovery process to fix it. It is like a self-healing library. As a consumer I just want my stuff to be there when I need it. This project gives me a way to do that while staying away from the typical gatekeepers of the web. It is a bit of a shift in how we think about the internet but it feels like the right direction for anyone who values their digital freedom.

$WAL #Walrus @WalrusProtocol

Have you ever wondered how big data stays safe and accessible in a decentralized world. When we look at the Walrus protocol we are really looking at a clever way to store information so that it never gets lost even if some computers go offline. I want to walk you through how the Read Protocol works within Walrus because it is quite different from your average file download. In this system we use things called nodes to hold pieces of data.
When you want to read a blob of data in Walrus you start by asking for commitments. These commitments are like digital fingerprints that prove the data is real. You do not just take one person word for it. Instead you check these fingerprints against the original record to make sure nobody is trying to trick you. This is the first step in making sure the Walrus network remains honest and reliable for every user involved.
Once you have the right fingerprints you move on to requesting the actual pieces of the file. In the Walrus system these pieces are called primary slivers. You might not get them all at once because the system can send them gradually to save on internet speed. This smart way of handling data is what makes Walrus feel so smooth even when the files are massive.
How Walrus Decodes and Verifies Your Information
The magic happens when you collect enough of these slivers. In the Walrus environment we typically need a specific number of correct pieces to put the puzzle back together. Once you have these pieces you decode them to see the original file. But the Walrus protocol does not stop there. It actually re-encodes the data one more time to double check that everything matches the original post on the blockchain.
If the re-encoded data matches what was originally promised then you get your file. If something is wrong the system simply outputs an error. This rigorous checking is why we can trust Walrus with important information. It ensures that what you write into the system is exactly what you get out of it later. We are basically using math to create a shield around our digital content.
This process might sound complicated but it happens behind the scenes to keep your experience simple. By using these mathematical proofs Walrus avoids the typical risks of central servers. You are not relying on one company but rather on a network of nodes that all verify each other. This transparency is the core strength of the Walrus storage solution.
The Power of Sliver Recovery in the Walrus Network
One of the coolest features of the Walrus protocol is how it handles missing pieces. Sometimes a computer might go offline before it gets its share of the data. In a normal system that might be a problem. However Walrus uses a method called Red Stuff which allows nodes to recover their missing slivers from their neighbors. It is like asking a friend for the notes you missed in class.
Nodes can recover their secondary slivers by asking other honest nodes for specific symbols. Because of the way Walrus organizes data in rows and columns these nodes can rebuild what they are missing quite easily. This means that over time every honest node in the Walrus network will eventually have the full set of information they need to be helpful.
This recovery process is very efficient. Even though nodes are sharing and rebuilding data the cost stays low. The Walrus design ensures that the total communication needed is not much more than a regular read or write. This efficiency is what allows Walrus to grow very large without slowing down or becoming too expensive for the people using it.
Smart Optimizations for Better Performance in Walrus
We are always looking for ways to make things faster and Walrus has some great tricks up its sleeve. One big optimization involves something called source symbols. These are pieces of the real data that have not been scrambled by complex math yet. If you can read these source symbols directly you save a lot of time and computer power.
In the original design of systems like this some data might only live on one node. If that node went to sleep you would have to do a lot of extra work. Walrus fixes this by shuffling where these symbols go. By using a random process Walrus spreads the data out more evenly across the network. This load balancing makes sure no single node gets overwhelmed with requests.
Another smart move in Walrus is reversing the order of symbols during encoding. This means every piece of original data actually exists in two different places. If one node is busy or offline you can just grab the data from the second node. This redundancy makes reading from Walrus much more reliable without adding a lot of extra weight to the system.
Reliability and Fault Tolerance in Walrus
The ultimate goal of the Walrus protocol is to be a truly dependable storage system. Because of the way it handles slivers it is very hard for the system to fail. Even if some nodes act up or go offline the remaining honest nodes have enough information to keep the Walrus network running perfectly. This is what we call being fault tolerant.
When you write data to Walrus the system makes sure that enough nodes have received their pieces before it considers the job done. This guarantees that the data is anchored safely. If a reader comes along later they are guaranteed to find enough pieces to recover the original file. This bond between the writer and the reader is the foundation of the Walrus community.
We also have a rule for consistency. If two different people try to read the same file from Walrus they will always get the same result. They might use different sets of slivers from different nodes but the math ensures the final file is identical. This consistency is vital for any system that wants to replace traditional cloud storage with something more modern and decentralized.
Why Scalability Matters for the Future of Walrus
As more people join the Walrus network the system needs to stay fast. Traditional protocols often get slower as they add more nodes but Walrus is built differently. Because the cost of recovering files is independent of the total number of nodes the system can scale up to massive sizes. This makes Walrus a perfect candidate for global data storage.
We also see that Walrus is very smart about how it uses hardware. It can store the main data on fast drives and keep the recovery pieces on slower cheaper storage. Since the recovery pieces are only needed when something goes wrong this saves money for everyone involved. It is a practical approach to building a high tech storage network.
I think the most exciting part of Walrus is how it combines complex math with a very human goal of keeping our data safe and accessible. It gives us the freedom to store our digital lives without fear of censorship or loss. As we continue to build and improve this protocol the potential for what we can achieve together only grows larger.
what you think about this? don't forget to comment 💭
Follow for more content 🙂
$WAL #Walrus @WalrusProtocol

The digital world is heavy.
Every photo you take, every contract you sign, and every line of code you commit adds to a global mountain of data that never stops growing. We’ve been told for decades that the "Cloud" is this magical, weightless place where things live forever. But honestly? That’s a bit of a myth.
The current version of the internet is actually quite fragile. We rely on a handful of massive companies to hold our digital lives. If they decide to change their terms, or if their servers go dark, our data is at their mercy. That doesn’t feel like freedom. It feels like we’re renting our own memories.
That’s why Walrus exists.
Walrus isn't just another storage locker in the sky. It’s a complete reimagining of how data survives in a decentralized world. When we talk about Walrus, we aren't talking about "traditional" storage. We are talking about a system built to be unshakeable, even when the world around it is in flux.
Walrus is designed to be the backbone of a new internet—one where your data belongs to you, stays available forever, and doesn’t cost a fortune to maintain.
"Data isn't just information; it’s the heartbeat of the modern world, and Walrus is here to make sure that heart never stops beating."
The Problem with Being "Online" Forever
Before we get into the "how" of Walrus, we have to talk about the "why."
In a perfect world, a storage node—a computer that holds a piece of your file—would stay online forever. It would never crash, its hard drive would never fail, and the person running it would never get bored and turn it off.
But we don't live in a perfect world. We live in a world of "churn."
In the tech world, "churn" is what happens when nodes leave the network. Maybe a server in Singapore loses power. Maybe a validator in London decides to upgrade their hardware. In a decentralized system like Walrus, this happens all the time. It’s natural.
The traditional way to fix this is "Replication." If Node A leaves, you copy everything it had over to Node B. But if you have petabytes of data, moving that much info across the internet every time someone’s Wi-Fi blinks is prohibitively expensive. It’s slow. It’s clunky.
Walrus saw this problem and decided to solve it with math that feels a bit like magic.
Actually, it’s called "Red Stuff." And it’s the secret sauce that makes Walrus so incredibly resilient.
Meet "Red Stuff": The DNA of Walrus
At the heart of Walrus is a protocol known as "Red Stuff."
If you want to understand Walrus, you have to understand how it views a file. Most systems see a file as a single block. Walrus sees a file as a two-dimensional puzzle.
Instead of just splitting a file into a few pieces and hoping for the best, Walrus uses something called 2D-encoding. Imagine taking a document and turning it into a grid.
The Vertical and the Horizontal
In the Walrus ecosystem, every blob of data is split into two dimensions:
1- Primary Slivers (The Columns): This is the vertical dimension.
2- Secondary Slivers (The Rows): This is the horizontal dimension.
When a writer sends a file to Walrus, they don't just send one version. They encode it so that every single storage node in the Walrus network holds a "Sliver Pair"—one primary and one secondary.
Why go to all this trouble? Because of recovery.
Imagine a storage node—let’s call it Node 4—suddenly goes offline. It loses its data. In a normal system, Node 4 would have to download the entire file again to get back to work. That’s a massive waste of bandwidth.
But in Walrus, Node 4 can talk to its neighbors. Because Walrus uses this 2D grid, Node 4 only needs to collect a tiny amount of data from other nodes to "math" its way back to its original state.
It’s like if you lost a piece of a crossword puzzle, but you could reconstruct the missing word just by looking at the letters that cross through it. That is the efficiency of Walrus.
"Efficiency isn't just about speed; it's about the intelligence of the system. Walrus doesn't work harder; it works smarter."
How a "Write" Happens in the Walrus World
Actually, the way Walrus handles a new piece of data is pretty cool to see in action. It’s a process built on radical transparency and mathematical certainty.
When you want to store something on Walrus, you (the "Writer") become the architect.
The Encoding: You take your blob of data and perform the Red Stuff 2D-encoding. You create those primary and secondary slivers we talked about. The Commitments: This is where the trust comes in. For every sliver, Walrus computes a "commitment." Think of this as a digital fingerprint. If even one bit of data changes, the fingerprint won't match. The Handshake: You send the slivers to the nodes. But you don't just send the data; you send the commitments too. Each node in the Walrus network checks its specific sliver against the commitment. The Consensus: Once a node is happy, it signs off. When you get enough signatures (2f + 1, for the math nerds out there), Walrus generates a certificate.
This certificate is then posted on-chain. It is a public, unchangeable promise that your data is safe within the Walrus network.
Honestly, it’s a beautiful dance. The writer doesn't have to keep re-sending data forever. Once those signatures are collected, the Walrus protocol takes over. Even if the writer disappears the next second, the data lives on.
The "Referees": Security and Rewards
One of the most common questions we get is: "Why would anyone want to store data for Walrus?"
It’s a fair question. Storing data takes electricity, hardware, and time. In the Walrus philosophy, trust isn't given; it's built through incentives.
The nodes in the Walrus network aren't doing this out of the goodness of their hearts. They are part of a robust economic system. They act as the network's referees.
If a node does its job—if it keeps its slivers safe and responds quickly to read requests—it gets rewarded. But here’s the kicker: because of the 2D-encoding, Walrus can prove if a node is lying.
If a node tries to serve "fake" data, the commitments (those digital fingerprints we mentioned) will immediately flag it. The rest of the Walrus network will see the mismatch. In this way, Walrus creates a self-healing, self-policing environment.
It’s real security. Not the kind of security that relies on a "Terms of Service" agreement, but the kind of security that relies on the laws of mathematics.
"In a world of uncertainty, Walrus provides the one thing we all crave: a guarantee that doesn't depend on a human's word."
Reading from Walrus: Speed Meets Accuracy
Storing data is only half the battle. You also need to get it back.
Reading from Walrus is designed to be as seamless as possible. When a "Reader" wants to find a file, they don't need to talk to every single node.
They start by checking the on-chain certificate. This tells them what the "blob commitment" should be. Then, they ask the nodes for the primary slivers.
The reader only needs to collect a fraction of the slivers (f + 1) to reconstruct the entire file. Once they have those pieces, they decode them, re-run the math, and check it against the original commitment.
If it matches? Success. You have your file.
If it doesn’t? The reader knows exactly which node sent bad data and can ignore it.
Walrus makes sure that even if a third of the network is having a bad day (or being intentionally difficult), your data still comes home to you.
The Self-Healing Miracle
Let’s go back to our friend Node 4 who went offline. This is where Walrus really shines as a storyteller.
In a traditional system, Node 4 is a liability. In Walrus, Node 4 is just a temporary gap that the rest of the family helps fill.
When Node 4 comes back online and realizes it’s missing its data, it doesn't panic. It reaches out to its peers—say, Node 1 and Node 3.
Intersection: Node 1 and Node 3 don't send Node 4 their entire data sets. That would be too much. Instead, they only send the tiny "intersections" where their rows and columns meet Node 4's missing pieces. Recovery: Node 4 takes these tiny fragments and uses the Walrus encoding rules to "re-grow" its secondary sliver. Completion: Once the secondary sliver is back, Node 4 can use it to reconstruct its primary sliver.
It’s like a lizard regrowing a tail. The Walrus network is a living organism. It’s decentralized, yes, but it’s also deeply connected. Every node supports the whole, and the whole supports every node.
Why Walrus Matters for the Future
We are entering an era of AI, massive media, and decentralized finance. The "old" way of storing things—on a central server owned by a billion-dollar company—is becoming a bottleneck.
We need a system that can handle the "Red Stuff"—the faults, the churn, and the scale of the future.
Walrus is that system.
It’s actually pretty cool when you think about it. By using 2D-encoding, Walrus has solved the "Recovery Problem" that has plagued decentralized storage for years. It has made it cheap to be resilient. It has made it easy to be secure.
But beyond the math and the slivers, Walrus represents a shift in how we relate to the digital world. It’s about moving from "renting" to "owning."
When you put your data on Walrus, you aren't asking a company for a favor. You are placing your information into a protocol that is mathematically incapable of forgetting you.
"The future isn't something that happens to us; it's something we build. And we are building it on Walrus."
Final Thoughts: The Heavy Lifter
The name Walrus was chosen for a reason.
In nature, a walrus is a creature of immense strength, capable of thriving in the harshest environments. It is steady. It is resilient. It is a "heavy lifter."
The Walrus protocol is no different. It is designed to carry the weight of the internet's data without breaking a sweat. It handles the "churn" of the world with a calm, mathematical grace.
Whether you are a developer looking for a place to host your dApp, a creator wanting to preserve your art, or just someone who believes the internet should be more open—Walrus is built for you.
It’s real. It’s here. And it’s changing the game.
The digital world might be heavy, but with Walrus, we finally have the shoulders to carry it.
$WAL #Walrus @WalrusProtocol

أنت تعرف كيف يكون الأمر عندما ترفع ملفًا إلى السحابة وتفترض فقط أنه سيبقى هناك لأنك تدفع ثمنه. كنت أعتقد نفس الشيء عن التخزين اللامركزي حتى بدأت في البحث حول كيفية الحفاظ على نزاهة العقد في والروس. إن قول إن بياناتك آمنة على مجموعة من أجهزة الكمبيوتر المختلفة هو شيء واحد، لكن التأكد من أن هؤلاء الأشخاص ليسوا مجرد متظاهرين بالاحتفاظ بملفاتك لجمع الأجر هو شيء آخر تمامًا.
أدركت أن أكبر مشكلة في هذا النوع من التقنية هي الكسل. إذا كان بإمكان عقد التخزين التخلص من بياناتك لتوفير المساحة بينما لا يزال يخبر الشبكة بأن لديهم تلك البيانات، فمن المحتمل أنهم سيفعلون ذلك. لإيقاف ذلك، يستخدم والروس شيئًا يسمى بروتوكول التحدي، وهو في الأساس تفتيش مفاجئ يحدث طوال الوقت.

بالأمس جلست على الطاولة وكنت أحاول أن أفهم أين يجب أن تُخزن جميع صوري الرقمية وملفات العمل الخاصة بي. هل تعلم كيف يكون الأمر عندما تدرك فجأة أن "السحابة" ليست سحابة على الإطلاق، بل مجرد كمبيوتر شخص آخر تدفع ثمنه كل شهر. بدأت أدرس Walrus لأنني كنت أريد شيئًا أكثر ديمومة لا يبدو كأنه فخ آخر بترتيب اشتراك شهري.