Authenticus

authenticus

I really like 's AARRR to defining your company objectives. tability.io funnel-based approach What is the AARRR funnel? The the AARRR funnel (aka “Pirate Metrics”) is, in internet time at least, an framework that divides your users' journey — into 5 steps: age-old 🪰 how do people discover you? Acquisition: 🕷️ how many of those people actually try your product? Activation: 🕸️ how many of those users come back? Retention: 🐜 how many of those users tell their networks about you? Referral: 🦟 how many of those users convert into paying customers? Revenue: Once you've answered these questions and have these insights at hand, you should start to get a sense of which areas of your funnel could use some extra TLC next quarter, so to speak. 🤧 There appears to be some around whether AARRR should be replaced with the Retention-led “RARRA”. Personally, I prefer the Pirate-Hacker alignment of energies in “AARRR”, so for the purposes of this post, we’ll be going with the original acronym. debate How to Set Company Objectives to Satisfy Every Stage of Your Funnel Your funnel priorities can be mapped against the stages of your product lifecycle, as follows: Before we list specific goals and OKRs most relevant to each funnel priority, here's a brief refresher on the stages of the Product Lifecycle. Your Quick Guide to the Stages of the Product Lifecycle 💡 Introduction 🌱 Growth 🧓🏻 Maturity 💀 Decline 1. 💡 Introduction Sometimes people build before they validate; sometimes people validate before they build. Either way: Your Product is in the Introduction Phase of its Lifecycle if: you haven't yet nailed the product-market fit you might not have launched yet you definitely aren't profitable Questions You Might Still Need to Answer in the Introduction Phase Include: Which problem/s do we solve, how, and for who — exactly? Where do our potentially biggest fans live (online)? What's the existing narrative in our space, and who is influential? How are we disrupting and improving on the status quo? "Infusing our output with critical thinking, new visions, and expansive transgressions opens up many more possibilities than it closes down. Scan for places where potency lies, get together, and start looking beyond the present." — Jess Henderson, ‘ Offline Matters: The Less Digital Guide to Creative Work’ 2. 🌱 Growth You'll Know You've Hit the Growth Phase When: you're seeing an unprecedented increase in sales you're talking a lot about how best to promote new product features to existing users your competitors know who you are "How are you positioning your product? If your current product is more advanced than competitors, you may be best positioned to earn a dominant market share—which means pushing more resources into current campaigns (at the expense of near-term profits)." — Derek Gleason for cxl.com Questions You're Probably Asking Yourself in the Growth Phase Include: Who do we need to hire right now? What are our departmental budgets and targets? Which potential partnerships are worth pursuing? How fast can the product team push this update? 3. 🧓🏻 Maturity Signs Your Product Has Reached Maturity May Include: you enjoy near-universal brand recognition you have thousands of competitors you're consistently profitable Questions You Should be Asking Yourself at Maturity Phase: What are the factors that may lead us into Decline? Are we effectively differentiating ourselves in a saturated market? Who and where are the new audiences we should be aiming to reach? 4. 💀 Decline "No matter how good your product is, it obeys the rules of the product life cycle." — Kateryna Mayka for eleken.co You'll Get that sick Decline Stage in Your Stomach Feeling When... users are not willing to pay for your product or service (aka it's no longer needed) your competitors are launching better features faster than you emerging tech starts making your product look obsolete there's a massive financial crash or change in legislation that negatively impacts your business Questions to ask when you're in Decline: How can we reduce spend and run on brand mileage? What's our rebrand, pivot, or exit strategy? What's no longer adding any value, and how can we milk what’s left? How to use the AARRR funnel to set OKRs for your product at every stage of its lifecycle Here are those Pirate Metrics one more time: 🪰 (how people find you) Acquisition 🕷️ (how many of those people actually try your product) Activation 🕸️ (how many of those people come back again, and again) Retention 🐜 (how many of those people tell their people about you) Referral 🦟 (how many of those users convert into paying customers) Revenue Now let’s get into how to set OKRs based on where your product’s at and which funnel metric you need to prioritize over the next few quarters. 🪰 1. Acquisition Prioritise Acquisition when your product is in the following phases: Introduction Growth Decline What's the Definition of Acquisition in the Product Lifecycle? Acquisition in growth or product marketing refers to efforts made to acquire new audience members, users, and/or eventually paying customers. Activities and tactics that fall under the Acquisition funnel priority include pretty much all the most expensive ones: SEO Paid Search and Social Advertising Content Marketing PR TV, Print and Billboard Advertising Going on Shark Tank, etc. How to set Product Acquisition OKRs Here are a few examples of how you might go about writing your OKRs if you wanted to focus on acquisition for the next six months: Q1 Acquisition Objective: Grow brand presence in the right markets. grow collective social media media communities to 100,000,000 key result 1: achieve 2,000 podcast downloads per episode key result 2: Q2 Acquisition Objective: Use new features/product lines to get press and attract users from new market segments. generate 10 meaningful press mentions around new/differentiating features key result 1: activate 1,000 new users on the pro/team plan key result 2: Q2 Acquisition Objective: Establish an engaged and authentic community. grow Discord community to identify 1,000 highly engaged brand ambassadors key result 1: optimize funnel to achieve 1,000 new subscriptions/month based on all site traffic key result 2: reshare and comment on ALL tagged posts on social media (15+ / week) key result 3: 2. 🕷️ Activation Prioritise Activation when your product is in the following phases: Introduction Growth What's the definition of Product Activation? Unlike the (sometimes) prone to vanity metrics related to acquisition, product activation indicates to engage with your product in a way that's beneficial to both themselves, and your business. how many of those interested people vaguely take an action actually "Activation happens when a registered user becomes a qualified lead. At this point, you need to evaluate if the specific circumstances that are necessary for that person are present and, if they are ready to become a customer." — for Theodore Moulos growthrocks.com Examples of activation campaigns and strategies will be unique to the product or service in question, but I really like : Dan McGaw's way of looking at it "The activation event has to be meaningful in terms of the value delivered to the customer. It’s strictly a one-time event. It signifies your business’ effectiveness in " getting customers to realize value from your product or service. How to set Product OKRs Activation As aforementioned, OKRs related to product activation will defer depending on your marketing strategy but for the sake of scalability — let's assume a product-led, freemium offering; designed to draw in a large pool of non-paying but active users before converting a percentage of these into paying customers, using automated (content-led) methods. ( ) sales-led, marketing-led, product-led..? Q1 Activation Objective: Get the right message(s) to the right people — in the right place — at the right time. attract 10,000 new active users key result 1: nurture 10% of new users over to pro/team plan key result 2: Q2 Activation Objective: Build an onboarding experience users love. attract 10,000 new active users key result 1: nurture 10% of new users over to pro/team plan key result 2: 3. 🕸️ Retention Prioritise Retention when your product is in the following phases: Growth Maturity What's the Definition of Retention? Retention might just be marketing's most lasting buzzword but, TBH, I fully agree. What better indicator of the success of your product than proof that people can't stop using it? If retention is lifecycle marketing's golden child, churn is her evil step-sister. You can measure your churn rate as follows: (Lost Customers ÷ Total Customers at the Start of Time Period) x 100. So, for example, if your app had 1,000 active users at the beginning of the month, and 450 of them have unsubscribed or become inactive, your churn rate for this month was 45% (and you might want to take another look at the assumptions you made around your product market fit). Your priority in Retention is to make the churn rate lower than your customer acquisition rate. Otherwise, growth can’t be achieved. The last few years, a big emphasis is put into the Retention channel by many growth marketers, and for a good reason. First, it’s a lot cheaper to retain an existing customer than acquiring a new one. At the beginning of the funnel, you were trying to build awareness through channels such as Facebook ads, Google ads, influencers, content marketing, etc. And, as you know, none of these channels comes for free. By Retention stage, you should have established communication channels in your own properties." — for Theodore Moulos growthrocks.com A few examples of user retention channels and tactics in AARRR or lifecycle marketing are: Newsletters Trigger-based email automation Push notifications In-app messengers and chatbots Gamification Rewards / loyalty programs Customer surveys Product personalization User feedback loops Sending glitter through the physical mail, etc. How to Set Product Retention OKRs Q1 Retention Objective: Retain and reward our most engaged users. overhaul email strategy to decrease unsubscribe rates by 5% key result 1: improve our monthly churn rate by 10% key result 2: Q2 Retention Objective: Build personalized feedback loops for our users. fix all the bugs marked "users are fleeing ‼️ " in the backlog key result 1: send monthly to promote new features key result 2: "have you tried this" emails What I like most about the phrasing of these objectives is that once they’re achieved, they can all be turned into impressive-sounding “have/do/be” statements (that you can back up with hard numbers in your next stakeholder newsletter), like: Phrasing OKRs is a subject that’s seen a lot of attention, but I think how you phrase your objectives is 100% up to you. As long as the phrasing of your Key Results check the boxes of a SMART goal, it’s all gravy IMHO. “We retain and reward our most engaged users, and we’ve built personalized feedback loops we’re using to make the product better for them.” 4. 🐜 Referral Prioritise Referral when your product is in the following phases: Growth What's the Definition of Product Referral? Think about how you came to know all the best products you use. More often than not, you tried it because a real human you know (either personally or on TikTok) told you it was good shit. Us humans are just wired like that, and that's why referrals are the best growth tactic in the game. "To really drive referrals you need to have a systematic process in place that incentivizes and generates them on a consistent basis." — Melanie Balke Marketing activities and tactics that fall under the Referral funnel priority include: One-click social sharing Incentivized referral campaigns (often in email newsletters) Google and app store reviews Online user reviews and testimonial prompts Net Promoter Score (NPS) Podcast reviews Youtube comments Product write-ups and reviews Buying celebrity video endorsements via Cameo and then promoting them on Tiktok, etc. How to Set Product Referral OKRs Q1 Referral Objective: Establish an internal referral culture. spend 20% of marketing budget on rewarding employees for online referrals, reviews, and testimonials key result 1: team to collectively publish 30+ interviews with real users key result 2: Q2 Referral Objective: Build out and automate our official referral program. spend 20% of marketing budget rewarding users for online referrals, reviews, and testimonials key result 1: ncrease our total referral traffic by 25% key result 2: i 5. 🦟  Revenue Prioritise Revenue when your product is in the following phases: Introduction Maturity Marketing activities and tactics that fall under the Referral funnel priority include: Pricing model testing and experimentation (for example “ ”) pay as you grow Automated upselling/cross-selling campaigns Payment automation Abandoned cart emails Content, site, or product monetization strategies What's it Going to Take for Your Startup to Turn Profitable? This the freemium-first world of SaaS, this can be one of the most controversial choices you make. You could limit access to features that were previously free in order to force the upsell... but you risk pissing off a lot of people. You could pump your freemium level product full of ads to educate users about the benefits of paying up... but, ditto. Personally, I really love the circular idea of ideating until you figure out a way of off your product, . helping your users make money somehow someway How to set Product Revenue OKRs Q1 Revenue Objective: Build a flawlessly automated onboarding flow for brands. optimize our funnel to process our first 1,000 automated payments key result 1: respond to first 1,000 messages from customers via our new chatbot key result 2: Q2 Revenue Objective: Implement incentivized cross-/up-selling campaigns. deploy 3 user-requested features to premium tier to encourage levelling up key result 1: signup 1,000 freemium users for a no credit-required free trial month key result 2: 💭 I’d love to hear your feedback on this approach to setting product OKRs. Product Managers, Marketing Directors, CEOs; Why not ? 😉 get your commentary published on HackerNoon See you around , Planet Internet Natasha ✌️💗 ✨ Article Resources OKRs for Startups by tability.io by Emily Bonnie for AARRR vs. RARRA: Which is Better? clevertap.com by Jess Henderson Offline Matters: The Less Digital Guide to Creative Work by Product Lifecycle Marketing: What Matters Most at Every Stage Derek Gleason for cxl.com by Decline Stage of the Product Life Cycle – How to Handle It Kateryna Mayka for eleken.co by for AARRR Framework: 10 Steps to Building a Growth Funnel Theodore Moulos growthrocks.com This “OKRs from a development team’s perspective” thread on HackerNews by Melanie Balke AARRR Framework- Metrics That Let Your StartUp Sound Like A Pirate Ship SaaS Marketing: 30 Examples of What Works by Aaron Brooks for ventureharbour.com

11 OKR Examples for Product Managers Chasing Pirate Metrics

Verifiable credentials, which provide a system for provable electronic facts and documentation through cryptography and public keys, can seem like an abstract concept. We’re so used to seeing our credentials printed out – the driver’s license, the passport, the insurance card – that sticking codified IDs on a thumb drive or online seems odd and unnecessary. And as anyone who has used a cryptocurrency wallet can attest, the early forms of such decentralized IDs are hardly user friendly. Just as cloud computing and big data seemed initially vague, then ubiquitous, so verifiable credentials promise to appear in our daily lives in the not-too-distant future. (My guess is they’ll pop up in your Apple Wallet one day, and then become normal). In fact, several industries are already digging in. Here are some of the most visible and promising use cases. Education As the economy continues to digitize, workers must adopt new skillsets -- and not necessarily as part of a four-year college degree. As coding bootcamps prove, students can attain employable skills within a matter of months. Yet there is no standardized way to validate candidates' skills, outside of a paper degree or certificate. 96% of employers use at least one kind of , according to a Global HR Research survey. At $20-$200 per candidate, the costs quickly add up. It is also an outdated process. The entire point of background checks is to attain trustable, verifiable information about a candidate, something that a verifiable credential could do for cents on the dollar. background screening Verifiable credentials could also host the gamut of employable skills, from cash register experience to cybersecurity coding. Such credentials currently exist only on the resume or LinkedIn profile, and are unverifiable unless an employer calls a reference that the candidate listed. Graduate or transfer schools face the same problem when requesting transcripts. Verifiable credentials would, for the first time, provide a foolproof way to tell if skills or classes taken are real. Just-in-time verifiable credentials take the concept a step further by enabling recipients to monitor credentials over time. A company that hires a college intern, for example, might require a 3.0 GPA over the course of a year-long internship. The school records office could automatically send over the student's GPA every semester for the year. Or a lab could automatically send drug-test results for an employee whose role requires monthly testing. Such verifiable credentials are in the very early stage, and privacy concerns must be addressed. But they are yet another promising use case for the education sphere. 2. Customs and Border Patrol The US has received worth of goods at its borders so far this year. Of that, over $1.3 billion was seized, whether due to counterfeiting, safety violations or other concerns. $2.42 trillion It takes the same amount of time to review all goods, whether safe or dangerous, counterfeit or authentic. US Customs and Border Protection (CBP) is better off applying manpower to shipments that are higher-risk, while letting in low-risk items with minimal effort. This is especially important for agriculture. It can take days to figure out if a shipment of perishable fruit, for example, contains a pathogen, and by then, entire loads could be lost. Verifiable credentials promise to solve such border-related problems by providing a trusted digital catalogue of information for each part of a shipped good. They can be used by supply chains in a stacked way, similar to Russian nesting dolls. Take a metal car door as an example. The first step might be a smelter in Poland. The person in charge of the smelting project obtains a verifiable credential when the load is completed for shipment to Great Britain, where the car doors are stamped. Once complete, the British manufacturer attains a verifiable credential that follows the one in Poland, and the doors are then sent to a BMW plant in Germany for assembly. Once assembled, the German plant adds third verifiable credentials, and then the load is shipped to the US, where the shipping containers get their own credential. CBP can then unstack all the virtual nesting dolls, and determine everything they need to know about parts, tariffs, safety, counterfeits and so on. 3. Transportation-as-a-Service Cars already come with a pile of credentials and certifications: insurance, registration, service history, VIN, title, emissions records and the driver's license. Parking tickets, speeding tickets, fast-lane transponders add another layer of identification. For now, middleman services such as repair shops, car reports and the DMV certify each vehicle's information. Verifiable credentials could put all of a car's information in one place, with the driver sharing selectively, depending on the type of request. Newer types of connected cars could even contain verifiable credentials within the vehicle itself. This becomes especially poignant given that Millennials, the largest generation in the US, and Gen-Z behind them are (specifically, they are buying cars later and driving them longer). Meanwhile, the car sharing market is 24% between 2020-2026. buying fewer cars expected to grow Verifiable credentials promise to play a starring role, not only in providing a record of who's at the wheel and when, but in terms of law and policy. For one, verifiable credentials prove the safety and roadworthiness of a car, by keeping its records accessible in one digital place. If a car is in a traffic violation, verifiable credentials prove who was there at the time. Vehicle ownership is also a big tax revenue item for states. If fewer people own cars, taxes disappear, and roads and infrastructure lose funding. Verifiable credentials, by tracking miles driven, greenhouse gas emissions, and so on, could create new revenue models. 4. Ad monetization Many websites rely on ad networks to monetize. That model is increasingly showing its limits. Revenue-oriented algorithms feed societal divisions by selecting for what the algo thinks will generate the most money. An increasing number of people find targeted data collection invasive, and employ ad blockers and other privacy tools as a result. The model is even expensive for advertisers. Half every ad dollar is taken during a transaction. Social media companies such as Facebook collect click, like, and other psychographic and demographic data to build a profile of likely spending habits. That data is then sold to companies wishing to target you. Despite advances in data collection and targeting technology, results are hit or miss. There is a tendency to see an item advertised that you already purchased, or items that you would never dream of buying. Third-party data is behind this – the educated guess that Facebook et. al. employ when selling data about your online interactions. First-party data, which you provide yourself, directly to advertisers, would fix this problem. Verifiable credentials, by anonymizing and proving your identity, would enable you to sell your data, for a price, directly to advertisers. You’d get a paycheck and advertisers would have first-party targeting data (they would sell you stuff you would actually buy). The middleman would be cut out, and both sides would profit. 5. Homebuying Real estate is rife with potential for verifiable credentials. Realtors, for one, try to target potential buyers and sellers on specific criteria. Selling data directly to them, via the process mentioned above, would enable better targeting, as well as cash in your pocket. Mortgage companies, meanwhile, conduct due diligence on employment and pay records. It is not an employer’s business to know whether an employee is applying for a home loan. Verifiable credentials could prevent employers from knowing. A pay stub could be transformed into a verifiable credential, enabling lenders to validate claims of employment without bothering the boss. Verifiable credentials could also be used during the inspection and appraisal processes, validating who was there and when. They could be used as digital titles. In such a money and trust-intensive transaction, there is an opportunity to transform the entire industry.

5 Promising Use Cases for Verifiable Credentials

3 Real-World Examples of Why Companies Need Better Email Authentication

This text began as a defense of the characters that inhabit us, our own fictions, and their expressions in virtuality. However, as usual, I succumbed to a nearly endless diatribe, raising arguments to dismantle possible ideas. In the end, the defense of performance turned into a rejection of essence, such as authenticity. In other texts, I mentioned the need to consider the amplifying potential of the Internet and the social context in which the development of technologies occurs when reflecting on digital habits. In this sense, virtuality amplifies the calls of our time. Amid the calls to become our best selves, to establish our personal brand, to explore all possibilities, and to express our opinions on almost everything, there is the call to express ourselves authentically and in a way that represents our own essence, showing ourselves as we truly are. After all, this would represent integrity. Obviously, this call is expressed in the use of technology. In Zuckerberg's words: “You have one identity…The days of you having a different image for your work friends or co-workers and for the other people you know are probably coming to an end pretty quickly…Having two identities for yourself is an example of a lack of integrity.” [1] Curiously, criticisms of social media make use of similar arguments, supported by the idea of the impossibility of multiple and concurrent ways of being. Like when they mention that there is no real in the virtual, that we are merely characters in constant performance. I believe that these comments and arguments have roots in two points: assuming that there is an authenticity outside the network and an accessible essence; and believing that knowing more, learning more, is always beneficial. In this text, I limit myself to exploring the first point. The notion of essence can be seen as a way of dealing with the lack of guarantees of existence, with the anxiety of the uncertain and the indeterminacy to which we are, in many ways, subjected. To think that there is an essence to be achieved, accessed, capable of alleviating our anxiety and giving meaning to our existence, can be comforting. However, it can also be a source of discomfort and serve the discourses of self-improvement and the instrumentalization of care. Not presupposing an essence requires us to accept and deal with ambivalence and contradiction, both in ourselves and in others. We must be capable of recognizing the nuances and complexity that come with being human. In order to do this, accepting that we will select what we choose to represent may be an option, and this is, to some extent, a performance. Authenticity in this context is interpreted as synonymous with self-expression free from performance, which would bring us closer to an essence. However, what is being referred to as performance may serve a function of containment of limitation. Let us imagine what a world would be like without performance, where we all always express exactly what we are feeling and thinking, which is part of what we are. At the very least, it would be chaotic. I, like many, prefer to call it unbearable. Thus, perhaps we are always performing, for even if we idealized being always transparent, that would not be possible. How would we convey, at the same time, two lines of thought that confront each other, composing a conflict or dilemma we experience at a given moment? How would we fully convey two emotions that coexist? Containment, the imposition of limits, allows us to act in an adaptable manner, to recognize ourselves and others, and to avoid being overwhelmed. Does this mean that it is possible to be whatever I want? That I can do whatever I want? No. The selection of representations also has limits; they can be social, ethical, economic, or biological impositions. Different representations imply different characters, but they do not mean different actors. What Representations Are We Willing to Interpret, and Why? What is relevant may be to consider how this character interacts with our own narrative, whether it is a source of exhaustion, or if we identify with it so much that we come to believe we are it and only it, forgetting that no narrative can sustain itself with just one character. Do I fear appearing different from the character I maintain on social media? Are there drawbacks to sustaining this character in light of the daily activities that life demands? Do I forgo other possibilities for myself because of it? If this character were to step out of the scene, how would it be? What is the impact of this character on the lives of others? How does it affect others? Does it come closer to or further away from what I desire to be or think I am? Perhaps the new question is: in service of what or which narratives are our supposedly virtual characters? "(...) time is a powerful force. It transforms our preferences. It reshapes our values. It alters our personalities. We seem to appreciate this fact, but only in retrospect. (...) It's as if, for most of us, the present is a magic time. (...) It's the moment at which we finally become ourselves. Human beings are works in progress that mistakenly think they're finished. The person you are right now is as transient, as fleeting and as temporary as all the people you've ever been. The one constant in our life is change."  - Daniel Gilbert [2] References: [1] Zuckerberg em David Kirkpatrick The Facebook Effect (2010). [2] Daniel Gilbert — The Psychology of Your Future Self. Photo by Barthelemy de Mazenod on Unsplash This text began as a defense of the characters that inhabit us, our own fictions, and their expressions in virtuality. However, as usual, I succumbed to a nearly endless diatribe, raising arguments to dismantle possible ideas. In the end, the defense of performance turned into a rejection of essence, such as authenticity. In other texts, I mentioned the need to consider the amplifying potential of the Internet and the social context in which the development of technologies occurs when reflecting on digital habits. In this sense, virtuality amplifies the calls of our time. Amid the calls to become our best selves, to establish our personal brand, to explore all possibilities, and to express our opinions on almost everything, there is the call to express ourselves authentically and in a way that represents our own essence, showing ourselves as we truly are. After all, this would represent integrity . express ourselves authentically and in a way that represents our own essence, showing ourselves as we truly are. After all, this would represent integrity Obviously, this call is expressed in the use of technology. In Zuckerberg's words: “You have one identity…The days of you having a different image for your work friends or co-workers and for the other people you know are probably coming to an end pretty quickly…Having two identities for yourself is an example of a lack of integrity.” [1] “You have one identity…The days of you having a different image for your work friends or co-workers and for the other people you know are probably coming to an end pretty quickly…Having two identities for yourself is an example of a lack of integrity.” [1] Curiously, criticisms of social media make use of similar arguments, supported by the idea of the impossibility of multiple and concurrent ways of being. Like when they mention that there is no real in the virtual, that we are merely characters in constant performance. I believe that these comments and arguments have roots in two points: assuming that there is an authenticity outside the network and an accessible essence; and believing that knowing more, learning more, is always beneficial. In this text, I limit myself to exploring the first point. The notion of essence can be seen as a way of dealing with the lack of guarantees of existence, with the anxiety of the uncertain and the indeterminacy to which we are, in many ways, subjected. To think that there is an essence to be achieved, accessed, capable of alleviating our anxiety and giving meaning to our existence, can be comforting. However, it can also be a source of discomfort and serve the discourses of self-improvement and the instrumentalization of care. Not presupposing an essence requires us to accept and deal with ambivalence and contradiction, both in ourselves and in others. We must be capable of recognizing the nuances and complexity that come with being human. In order to do this, accepting that we will select what we choose to represent may be an option, and this is, to some extent, a performance. Authenticity in this context is interpreted as synonymous with self-expression free from performance, which would bring us closer to an essence. However, what is being referred to as performance may serve a function of containment of limitation. Let us imagine what a world would be like without performance, where we all always express exactly what we are feeling and thinking, which is part of what we are. At the very least, it would be chaotic. I, like many, prefer to call it unbearable. Thus, perhaps we are always performing, for even if we idealized being always transparent, that would not be possible. How would we convey, at the same time, two lines of thought that confront each other, composing a conflict or dilemma we experience at a given moment? How would we fully convey two emotions that coexist? Containment, the imposition of limits, allows us to act in an adaptable manner, to recognize ourselves and others, and to avoid being overwhelmed. Does this mean that it is possible to be whatever I want? That I can do whatever I want? No. The selection of representations also has limits; they can be social, ethical, economic, or biological impositions. Different representations imply different characters, but they do not mean different actors. What Representations Are We Willing to Interpret, and Why? What is relevant may be to consider how this character interacts with our own narrative, whether it is a source of exhaustion, or if we identify with it so much that we come to believe we are it and only it, forgetting that no narrative can sustain itself with just one character. to consider how this character interacts with our own narrative, whether it is a source of exhaustion, or if we identify with it so much that we come to believe we are it and only it, forgetting that no narrative can sustain itself with just one character. Do I fear appearing different from the character I maintain on social media? Are there drawbacks to sustaining this character in light of the daily activities that life demands? Do I forgo other possibilities for myself because of it? If this character were to step out of the scene, how would it be? What is the impact of this character on the lives of others? How does it affect others? Does it come closer to or further away from what I desire to be or think I am? Perhaps the new question is: in service of what or which narratives are our supposedly virtual characters? Perhaps the new question is: in service of what or which narratives are our supposedly virtual characters? "(...) time is a powerful force. It transforms our preferences. It reshapes our values. It alters our personalities. We seem to appreciate this fact, but only in retrospect. (...) It's as if, for most of us, the present is a magic time. (...) It's the moment at which we finally become ourselves. Human beings are works in progress that mistakenly think they're finished. The person you are right now is as transient, as fleeting and as temporary as all the people you've ever been. The one constant in our life is change."  - Daniel Gilbert [2] "(...) time is a powerful force. It transforms our preferences. It reshapes our values. It alters our personalities. We seem to appreciate this fact, but only in retrospect. (...) It's as if, for most of us, the present is a magic time. (...) It's the moment at which we finally become ourselves. Human beings are works in progress that mistakenly think they're finished. The person you are right now is as transient, as fleeting and as temporary as all the people you've ever been. The one constant in our life is change."  - Daniel Gilbert [ 2 ] 2 References: [1] Zuckerberg em David Kirkpatrick The Facebook Effect (2010). Zuckerberg em David Kirkpatrick The Facebook Effect The Facebook Effect (2010). [2] Daniel Gilbert — The Psychology of Your Future Self. Daniel Gilbert — The Psychology of Your Future Self. Photo by Barthelemy de Mazenod on Unsplash Photo by Barthelemy de Mazenod on Unsplash Barthelemy de Mazenod Unsplash

Why Not Be Authentic on Social Media?

لماذا لا نكون أصليين على وسائل التواصل الاجتماعي؟

¿Por qué no ser auténtico en las redes sociales?

Zašto ne biti autentičan na društvenim mrežama?

Ինչու՞ իրական չլինել սոցիալական լրատվամիջոցներում:

ソーシャル メディアで本物らしくないのはなぜですか?

ហេតុអ្វីមិនពិតប្រាកដនៅលើប្រព័ន្ធផ្សព្វផ្សាយសង្គម?

Эмне үчүн социалдык медиада чыныгы болбошу керек?

Mengapa Tidak Menjadi Tulen di Media Sosial?

Ubona gute ubaye umunyakuri ku mbuga nkoranyambaga?

Ha Yini U Nga Ri Wa Ntiyiso Eka Social Media?

Nega ijtimoiy tarmoqlarda haqiqiy bo'lmaslik kerak?

为什么不在社交媒体上表现真实？

The startup ecosystem is often portrayed as a vibrant landscape of innovation and opportunity, yet beneath the surface lies a complex web of misleading tactics that can undermine both startups and venture capitalists (VCs). As the industry evolves, it’s crucial to confront the theatrical and populistic attitudes that dominate pitch presentations and investment decisions. This article aims to shed light on these dynamics, fostering a more authentic relationship between startups and VCs. 🎭Theatrical Presentations: Style Over Substance Pitch competitions have become synonymous with startup funding, but they often resemble theatrical performances more than genuine business evaluations. Founders are pressured to deliver captivating narratives, focusing on storytelling rather than the viability of their business models. This emphasis on performance can lead to: Crowd InfluenceJust as populism sways public opinion, an audience's enthusiasm can unduly influence VCs to invest based on perceived popularity rather than critical assessment. This bandwagon effect can result in funding decisions that prioritize hype over substance. Judging CriteriaMany competitions reward presentation skills over rigorous financial analysis. This skewed focus can mislead investors into backing startups needing sustainable business practices or a clear path to profitability. 💰The Financial Focus of VCs While VCs play a crucial role in funding innovation, their approach often prioritizes financial returns over the purpose of startups. This can manifest in several ways: High Return ExpectationsVCs typically seek substantial returns, overshadowing a startup's original mission. The pressure to scale rapidly may lead to unsustainable growth strategies that compromise long-term viability. Power Law DynamicsThe venture capital model operates under a power law, where a few successful investments generate the most returns. This encourages VCs to spread their bets across many startups, leading to a mindset where individual missions are secondary to overall portfolio performance. 🧨The Risk of Overvaluation and Misaligned Interests The excitement generated during pitch events can lead to inflated valuations for startups that lack solid foundations. VCs may be swayed by the energy in the room rather than conducting thorough due diligence, resulting in: OvervaluationStartups may receive funding based on charisma rather than sound business practices, perpetuating investment cycles in companies that fail to deliver on their promises. Dilution of VisionAs VCs influence startups, there is a risk that founders will alter their original missions to align with investor expectations. This dilution can alienate key stakeholders and disrupt the startup’s core purpose. 📣A Call for Authenticity and Collaboration To disrupt the current landscape, both startups and VCs must embrace authenticity and collaboration: Emphasize SubstanceStartups should prioritize clear communication about their business models and market strategies over theatrical presentations. Investors must look beyond charisma and focus on the fundamentals driving long-term success. Align InterestsFounders and VCs should work together to ensure that investment strategies align with the startup’s mission. Open dialogue about expectations can help bridge the gap between financial goals and entrepreneurial vision. Foster Meaningful ConnectionsInstead of merely networking for funding opportunities, both parties should engage in deeper conversations about business strategy and growth potential. Building relationships based on trust and shared values can lead to more informed investment decisions. Conclusion The startup investment landscape is ripe for disruption. By confronting misleading tactics rooted in theatricality and populism, we can foster a more authentic relationship between startups and venture capitalists. Emphasizing substance over style, aligning interests, and encouraging meaningful dialogue will pave the way for sustainable growth and innovation in the industry. It’s time for both sides to move beyond performance-driven narratives and focus on what truly matters: building successful businesses grounded in purpose and integrity. The startup ecosystem is often portrayed as a vibrant landscape of innovation and opportunity, yet beneath the surface lies a complex web of misleading tactics that can undermine both startups and venture capitalists (VCs). As the industry evolves, it’s crucial to confront the theatrical and populistic attitudes that dominate pitch presentations and investment decisions. This article aims to shed light on these dynamics, fostering a more authentic relationship between startups and VCs. 🎭Theatrical Presentations: Style Over Substance Pitch competitions have become synonymous with startup funding, but they often resemble theatrical performances more than genuine business evaluations. Founders are pressured to deliver captivating narratives, focusing on storytelling rather than the viability of their business models. This emphasis on performance can lead to: Crowd InfluenceJust as populism sways public opinion, an audience's enthusiasm can unduly influence VCs to invest based on perceived popularity rather than critical assessment. This bandwagon effect can result in funding decisions that prioritize hype over substance. Crowd Influence Just as populism sways public opinion, an audience's enthusiasm can unduly influence VCs to invest based on perceived popularity rather than critical assessment. This bandwagon effect can result in funding decisions that prioritize hype over substance. Judging CriteriaMany competitions reward presentation skills over rigorous financial analysis. This skewed focus can mislead investors into backing startups needing sustainable business practices or a clear path to profitability. Judging Criteria Many competitions reward presentation skills over rigorous financial analysis. This skewed focus can mislead investors into backing startups needing sustainable business practices or a clear path to profitability. 💰The Financial Focus of VCs While VCs play a crucial role in funding innovation, their approach often prioritizes financial returns over the purpose of startups. This can manifest in several ways: High Return ExpectationsVCs typically seek substantial returns, overshadowing a startup's original mission. The pressure to scale rapidly may lead to unsustainable growth strategies that compromise long-term viability. High Return Expectations VCs typically seek substantial returns, overshadowing a startup's original mission. The pressure to scale rapidly may lead to unsustainable growth strategies that compromise long-term viability. Power Law DynamicsThe venture capital model operates under a power law, where a few successful investments generate the most returns. This encourages VCs to spread their bets across many startups, leading to a mindset where individual missions are secondary to overall portfolio performance. Power Law Dynamics The venture capital model operates under a power law, where a few successful investments generate the most returns. This encourages VCs to spread their bets across many startups, leading to a mindset where individual missions are secondary to overall portfolio performance. 🧨The Risk of Overvaluation and Misaligned Interests The excitement generated during pitch events can lead to inflated valuations for startups that lack solid foundations. VCs may be swayed by the energy in the room rather than conducting thorough due diligence, resulting in: OvervaluationStartups may receive funding based on charisma rather than sound business practices, perpetuating investment cycles in companies that fail to deliver on their promises. Overvaluation Startups may receive funding based on charisma rather than sound business practices, perpetuating investment cycles in companies that fail to deliver on their promises. Dilution of VisionAs VCs influence startups, there is a risk that founders will alter their original missions to align with investor expectations. This dilution can alienate key stakeholders and disrupt the startup’s core purpose. Dilution of Vision As VCs influence startups, there is a risk that founders will alter their original missions to align with investor expectations. This dilution can alienate key stakeholders and disrupt the startup’s core purpose. 📣A Call for Authenticity and Collaboration To disrupt the current landscape, both startups and VCs must embrace authenticity and collaboration: Emphasize SubstanceStartups should prioritize clear communication about their business models and market strategies over theatrical presentations. Investors must look beyond charisma and focus on the fundamentals driving long-term success. Emphasize Substance Startups should prioritize clear communication about their business models and market strategies over theatrical presentations. Investors must look beyond charisma and focus on the fundamentals driving long-term success. Align InterestsFounders and VCs should work together to ensure that investment strategies align with the startup’s mission. Open dialogue about expectations can help bridge the gap between financial goals and entrepreneurial vision. Align Interests Founders and VCs should work together to ensure that investment strategies align with the startup’s mission. Open dialogue about expectations can help bridge the gap between financial goals and entrepreneurial vision. Foster Meaningful ConnectionsInstead of merely networking for funding opportunities, both parties should engage in deeper conversations about business strategy and growth potential. Building relationships based on trust and shared values can lead to more informed investment decisions. Foster Meaningful Connections Instead of merely networking for funding opportunities, both parties should engage in deeper conversations about business strategy and growth potential. Building relationships based on trust and shared values can lead to more informed investment decisions. Conclusion The startup investment landscape is ripe for disruption. By confronting misleading tactics rooted in theatricality and populism, we can foster a more authentic relationship between startups and venture capitalists. Emphasizing substance over style, aligning interests, and encouraging meaningful dialogue will pave the way for sustainable growth and innovation in the industry. It’s time for both sides to move beyond performance-driven narratives and focus on what truly matters: building successful businesses grounded in purpose and integrity.

Confronting Misleading Tactics in Startup Investments: Calling for Authenticity

How to Implement Multi-Device Authentication System with FastAPI, Redis, and JWT

በFastAPI፣ Redis እና JWT የብዝሃ-መሣሪያ ማረጋገጫ ስርዓትን እንዴት መተግበር እንደሚቻል

Sådan implementeres Multi-Device Authentication System med FastAPI, Redis og JWT

Cómo implementar un sistema de autenticación multidispositivo con FastAPI, Redis y JWT

FastAPI, Redis और JWT के साथ मल्टी-डिवाइस प्रमाणीकरण प्रणाली को कैसे लागू करें

Ki jan yo aplike sistèm otantifikasyon milti-aparèy ak FastAPI, Redis, ak JWT

Ինչպես իրականացնել բազմաբնույթ սարքի նույնականացման համակարգը FastAPI-ի, Redis-ի և JWT-ի միջոցով

כיצד ליישם מערכת אימות מרובת מכשירים עם FastAPI, Redis ו-JWT

FastAPI、Redis、JWT を使用したマルチデバイス認証システムの実装方法

FastAPI, Redis және JWT көмегімен көп құрылғының аутентификация жүйесін қалай енгізу керек

Como implementar um sistema de autenticação multidispositivo com FastAPI, Redis e JWT

Cum să implementați sistemul de autentificare multi-dispozitiv cu FastAPI, Redis și JWT

Ndlela yo Tirhisa Sisiteme ya Vuhlayiseki bya Switirhisiwa swo Tala hi FastAPI, Redis, na JWT

How to Secure User Authentication in React With Clerk

Today, I want to share a simple tutorial on how to set up authentication in your Next.js project using Firebase. This guide will walk you through the process step-by-step, ensuring you can quickly implement a secure authentication system. https://youtu.be/qb2Ug9Yoatg?si=UqTUEOsFibmtDf1m&embedable=true Step 1: Set Up Firebase Account Create a Firebase Project Start by visiting the https://console.firebase.google.com/. You’ll need to create a Google account if you don’t already have one.
Once logged in, click “Add Project” to create a new Firebase project.
Follow the on-screen instructions to complete the project setup. This will serve as the backend for your authentication system. Enable Authentication In the Firebase Console, navigate to the left sidebar, click on “Build,” and then select “Authentication.”
Click on “Get Started” to initialize the authentication module.
You’ll see a list of sign-in methods. For this tutorial, we’ll enable Google and Email/Password authentication. Toggle the switch to enable each method.
For Google sign-in, you’ll need to provide a support email, typically your Firebase Google email.
Once you’ve configured your sign-in methods, click “Save” to apply the changes. Set Up Your Application Head over to “Project Settings” in the Firebase Console.
Scroll to the “Your Apps” section and click “Web App.”
Name your web app. If you plan to use Firebase Hosting, check the corresponding box.
Select your project and click “Register App.” This will generate SDK settings that you’ll need for your Next.js project.
Make sure to save these SDK settings securely, as they contain sensitive information. Step 2: Set Up Your Next.js Project Create a Next.js Application if you don’t have one yet (Optional) Open your terminal and create a new Next.js application by running the appropriate command (e.g., npx create-next-app).
Navigate into your project directory and install the Firebase package using the command: npm install firebase. This will allow you to integrate Firebase services into your app. Configure Firebase Open your preferred IDE, such as Visual Studio Code.
Create a new file named firebase.js in your project. This file will hold your Firebase configuration.
Copy the configuration data from the Firebase Console and paste it into firebase.js. This data includes your API key, project ID, and other essential settings.
For security reasons, consider using environment variables to store these configurations instead of hardcoding them. Source code: https://github.com/proflead/auth-next-js-app/blob/fa15aa8d6544937aa480a4308a8676a3310ed0b2/src/app/firebase.js Create Authentication Context Set up an AuthContext to manage the authentication state across your application.


This context will store information about the current user and provide functions for signing in and out.


Using context, you can avoid manually passing authentication props through every component. Source code: https://github.com/proflead/auth-next-js-app/blob/fa15aa8d6544937aa480a4308a8676a3310ed0b2/src/app/context/AuthContext.js Wrap Your Application In your layout.js file, wrap your entire Next.js application with the AuthProvider component.
This step ensures that the authentication context is available throughout your app, making it easy for any component to access the authentication state and functions.
Don’t forget to import the necessary components at the top of your script. Source code: https://github.com/proflead/auth-next-js-app/blob/fa15aa8d6544937aa480a4308a8676a3310ed0b2/src/app/layout.js Step 3: Create a Login Component Build the Login Component Create a login component that uses the useAuth hook to access the sign-in function from the authentication context.
This component will allow users to sign in with Google, providing a seamless authentication experience.
Ensure the component is user-friendly and clearly indicates the sign-in options available. Source code: https://github.com/proflead/auth-next-js-app/blob/fa15aa8d6544937aa480a4308a8676a3310ed0b2/src/app/Login.js Protect Your Pages Open page.js and import your login component and context.
Modify the code to protect your content, ensuring that only signed-in users can access certain pages or features. Source code: https://github.com/proflead/auth-next-js-app/blob/fa15aa8d6544937aa480a4308a8676a3310ed0b2/src/app/page.js If you want to see the code of the entire project, please visit https://github.com/proflead/auth-next-js-app Conclusion That’s it! You’ve successfully set up authentication in your Next.js application using Firebase. If you like this tutorial, please click like and share. You can follow me on YouTube, join my Telegram, or support me on Patreon. Thanks! :) Cheers! Today, I want to share a simple tutorial on how to set up authentication in your Next.js project using Firebase. This guide will walk you through the process step-by-step, ensuring you can quickly implement a secure authentication system. https://youtu.be/qb2Ug9Yoatg?si=UqTUEOsFibmtDf1m&embedable=true https://youtu.be/qb2Ug9Yoatg?si=UqTUEOsFibmtDf1m&embedable=true Step 1: Set Up Firebase Account Create a Firebase Project Create a Firebase Project Start by visiting the https://console.firebase.google.com/. You’ll need to create a Google account if you don’t already have one. Once logged in, click “Add Project” to create a new Firebase project. Follow the on-screen instructions to complete the project setup. This will serve as the backend for your authentication system. Start by visiting the https://console.firebase.google.com/. You’ll need to create a Google account if you don’t already have one. https://console.firebase.google.com/. https://console.firebase.google.com/. Once logged in, click “Add Project” to create a new Firebase project. Follow the on-screen instructions to complete the project setup. This will serve as the backend for your authentication system. Enable Authentication Enable Authentication In the Firebase Console, navigate to the left sidebar, click on “Build,” and then select “Authentication.” Click on “Get Started” to initialize the authentication module. You’ll see a list of sign-in methods. For this tutorial, we’ll enable Google and Email/Password authentication. Toggle the switch to enable each method. For Google sign-in, you’ll need to provide a support email, typically your Firebase Google email. Once you’ve configured your sign-in methods, click “Save” to apply the changes. In the Firebase Console, navigate to the left sidebar, click on “Build,” and then select “Authentication.” Click on “Get Started” to initialize the authentication module. You’ll see a list of sign-in methods. For this tutorial, we’ll enable Google and Email/Password authentication. Toggle the switch to enable each method. For Google sign-in, you’ll need to provide a support email, typically your Firebase Google email. Once you’ve configured your sign-in methods, click “Save” to apply the changes. Set Up Your Application Set Up Your Application Head over to “Project Settings” in the Firebase Console. Scroll to the “Your Apps” section and click “Web App.” Name your web app. If you plan to use Firebase Hosting, check the corresponding box. Select your project and click “Register App.” This will generate SDK settings that you’ll need for your Next.js project. Make sure to save these SDK settings securely, as they contain sensitive information. Head over to “Project Settings” in the Firebase Console. Scroll to the “Your Apps” section and click “Web App.” Name your web app. If you plan to use Firebase Hosting, check the corresponding box. Select your project and click “Register App.” This will generate SDK settings that you’ll need for your Next.js project. Make sure to save these SDK settings securely, as they contain sensitive information. Step 2: Set Up Your Next.js Project Create a Next.js Application if you don’t have one yet (Optional) Create a Next.js Application if you don’t have one yet Open your terminal and create a new Next.js application by running the appropriate command (e.g., npx create-next-app). Navigate into your project directory and install the Firebase package using the command: npm install firebase. This will allow you to integrate Firebase services into your app. Open your terminal and create a new Next.js application by running the appropriate command (e.g., npx create-next-app ). npx create-next-app Navigate into your project directory and install the Firebase package using the command: npm install firebase . This will allow you to integrate Firebase services into your app. npm install firebase Configure Firebase Configure Firebase Open your preferred IDE, such as Visual Studio Code. Create a new file named firebase.js in your project. This file will hold your Firebase configuration. Copy the configuration data from the Firebase Console and paste it into firebase.js. This data includes your API key, project ID, and other essential settings. For security reasons, consider using environment variables to store these configurations instead of hardcoding them. Open your preferred IDE, such as Visual Studio Code. Create a new file named firebase.js in your project. This file will hold your Firebase configuration. firebase.js Copy the configuration data from the Firebase Console and paste it into firebase.js . This data includes your API key, project ID, and other essential settings. firebase.js For security reasons, consider using environment variables to store these configurations instead of hardcoding them. Source code: https://github.com/proflead/auth-next-js-app/blob/fa15aa8d6544937aa480a4308a8676a3310ed0b2/src/app/firebase.js Source code: https://github.com/proflead/auth-next-js-app/blob/fa15aa8d6544937aa480a4308a8676a3310ed0b2/src/app/firebase.js https://github.com/proflead/auth-next-js-app/blob/fa15aa8d6544937aa480a4308a8676a3310ed0b2/src/app/firebase.js Create Authentication Context Create Authentication Context Set up an AuthContext to manage the authentication state across your application. This context will store information about the current user and provide functions for signing in and out. Using context, you can avoid manually passing authentication props through every component. Set up an AuthContext to manage the authentication state across your application. Set up an AuthContext to manage the authentication state across your application. This context will store information about the current user and provide functions for signing in and out. This context will store information about the current user and provide functions for signing in and out. Using context, you can avoid manually passing authentication props through every component. Using context, you can avoid manually passing authentication props through every component. Source code: https://github.com/proflead/auth-next-js-app/blob/fa15aa8d6544937aa480a4308a8676a3310ed0b2/src/app/context/AuthContext.js Source code: https://github.com/proflead/auth-next-js-app/blob/fa15aa8d6544937aa480a4308a8676a3310ed0b2/src/app/context/AuthContext.js https://github.com/proflead/auth-next-js-app/blob/fa15aa8d6544937aa480a4308a8676a3310ed0b2/src/app/context/AuthContext.js Wrap Your Application Wrap Your Application In your layout.js file, wrap your entire Next.js application with the AuthProvider component. This step ensures that the authentication context is available throughout your app, making it easy for any component to access the authentication state and functions. Don’t forget to import the necessary components at the top of your script. In your layout.js file, wrap your entire Next.js application with the AuthProvider component. layout.js AuthProvider This step ensures that the authentication context is available throughout your app, making it easy for any component to access the authentication state and functions. Don’t forget to import the necessary components at the top of your script. Source code: https://github.com/proflead/auth-next-js-app/blob/fa15aa8d6544937aa480a4308a8676a3310ed0b2/src/app/layout.js Source code: https://github.com/proflead/auth-next-js-app/blob/fa15aa8d6544937aa480a4308a8676a3310ed0b2/src/app/layout.js https://github.com/proflead/auth-next-js-app/blob/fa15aa8d6544937aa480a4308a8676a3310ed0b2/src/app/layout.js Step 3: Create a Login Component Build the Login Component Build the Login Component Create a login component that uses the useAuth hook to access the sign-in function from the authentication context. This component will allow users to sign in with Google, providing a seamless authentication experience. Ensure the component is user-friendly and clearly indicates the sign-in options available. Create a login component that uses the useAuth hook to access the sign-in function from the authentication context. useAuth This component will allow users to sign in with Google, providing a seamless authentication experience. Ensure the component is user-friendly and clearly indicates the sign-in options available. Source code: https://github.com/proflead/auth-next-js-app/blob/fa15aa8d6544937aa480a4308a8676a3310ed0b2/src/app/Login.js Source code: https://github.com/proflead/auth-next-js-app/blob/fa15aa8d6544937aa480a4308a8676a3310ed0b2/src/app/Login.js https://github.com/proflead/auth-next-js-app/blob/fa15aa8d6544937aa480a4308a8676a3310ed0b2/src/app/Login.js Protect Your Pages Protect Your Pages Open page.js and import your login component and context. Modify the code to protect your content, ensuring that only signed-in users can access certain pages or features. Open page.js and import your login component and context. page.js Modify the code to protect your content, ensuring that only signed-in users can access certain pages or features. Source code: https://github.com/proflead/auth-next-js-app/blob/fa15aa8d6544937aa480a4308a8676a3310ed0b2/src/app/page.js Source code: https://github.com/proflead/auth-next-js-app/blob/fa15aa8d6544937aa480a4308a8676a3310ed0b2/src/app/page.js https://github.com/proflead/auth-next-js-app/blob/fa15aa8d6544937aa480a4308a8676a3310ed0b2/src/app/page.js If you want to see the code of the entire project, please visit https://github.com/proflead/auth-next-js-app https://github.com/proflead/auth-next-js-app https://github.com/proflead/auth-next-js-app Conclusion That’s it! You’ve successfully set up authentication in your Next.js application using Firebase. If you like this tutorial, please click like and share. You can follow me on YouTube , join my Telegram , or support me on Patreon . Thanks! :) YouTube YouTube Telegram Telegram Patreon Patreon Cheers!

Next.js Authentication Made Easy with Firebase

Crypto PR agencies Are Shilling Tokens - How Authentic Projects Could Use PR Instead

ক্রিপ্টো পিআর এজেন্সিগুলি শিলিং টোকেন দিচ্ছে - এর পরিবর্তে কীভাবে প্রামাণিক প্রকল্পগুলি পিআর ব্যবহার করতে পারে

Krypto-PR-Agenturen werben mit Token – Wie authentische Projekte stattdessen PR nutzen könnten

Las agencias de relaciones públicas de criptomonedas están promocionando tokens: cómo los proyectos auténticos podrían usar las relaciones públicas en su lugar

Les agences de relations publiques cryptographiques sont des jetons de shilling – Comment les projets authentiques pourraient utiliser les relations publiques à la place

क्रिप्टो पीआर एजेंसियां टोकन बेच रही हैं - कैसे प्रामाणिक परियोजनाएं पीआर का उपयोग कर सकती हैं

暗号通貨PR代理店はトークンを宣伝している - 本物のプロジェクトは代わりにPRを活用できる

암호화폐 홍보 기관은 토큰을 팔고 있습니다. 진정한 프로젝트가 대신 홍보를 활용할 수 있는 방법

Agências de RP de criptomoedas estão vendendo tokens - Como projetos autênticos podem usar RP em vez disso

Криптовалютные PR-агентства торгуют токенами — как настоящие проекты могли бы использовать PR вместо этого

Kripto PR ajansları Token'ları Satıyor - Gerçek Projeler PR'ı Nasıl Kullanabilir?

Các công ty quan hệ công chúng tiền điện tử đang kiếm lợi từ các mã thông báo - Các dự án xác thực có thể sử dụng quan hệ công chúng như thế nào

加密公关机构正在推销代币——真实项目如何利用公关手段

COPA v. Wright, Court Filing, retrieved on January 29, 2024, is part of HackerNoon’s Legal PDF Series. You can jump to any part of this filing here. This part is 26 of 42. 24. Timecoin ODT Whitepaper (Reliance Document) {ID_000254} 446. The document purports to be a precursor draft of the Bitcoin White Paper and is presented as if written by Dr Wright. It is dated in the period 6 May 2008 to 12 December 2008 in its metadata, and Dr Wright states its approximate date to be 6 May 2008 in his Chain of Custody information. (a) COPA’s Reasons for Alleging Forgery 447. The document has been backdated. Rather than being a precursor document to the Bitcoin White Paper as it purports to be, this document has been created from the Bitcoin White Paper subsequently and edited in such a way that it appears as if it was precursor work. [PM2 60-64]]. 448. {ID_000254} has apparently been converted from the Bitcoin White Paper (which is a PDF) into a more easily editable format and has then undergone further conversions via intermediate documents [PM2 [60-64]]. Font configurations and the absence of diagrams are consistent with this conclusion [PM2 [17-28]]. No such intermediate document has been disclosed. 449. Diagrams have been omitted from this document as a result of the conversion process from PDF. The inclusion of the object replacement character ￼ within the document [a point where a diagram would be expected to appear is consistent with {ID_000254} being created by a process of conversion of a different document. [PM2 [28]]. 450. Where diagrams are absent, the document nevertheless preserves margin indentations from the Bitcoin White Paper PDF, but which do not match the content of the document. [PM2 [29-37]]. 451. The document irregularly contains words throughout in which hyphens ought to appear but are missing. This is not consistent with ordinary dictation or typing error but is as an artefact of conversion from PDF and backdating. [PM2 [38-44]]. 452. A conversion of the Bitcoin White Paper PDF to editable form would result in corruption of formulae. In each case where those formulae would have appeared corrupted, they have been deleted from {ID_000254}, leaving behind white space. [PM2 [45-48]]. 453. The document contains irregular line breaks consistent with conversion from the Bitcoin White Paper PDF into editable form and backdating. [PM2 [49-51]]. 454. The document contains text that matches the corrected text of the Bitcoin White Paper (2009 version) [PM2 [12]]. It does not match the October 2008 or November 2008 versions of the Bitcoin White Paper, even though this document purports to be earlier than both of them. 455. The document has been disclosed with irregular metadata listed in relation to its Created and Last Accessed external metadata properties. [PM2 [6-11]]. (b) COPA’s Reasons for Inferring Dr Wright’s Knowledge / Responsibility 456. The effect of the tampering is to make the document appear to be supportive of Dr Wright’s claim to be Satoshi Nakamoto (presenting as a predecessor draft of the Bitcoin White Paper and supposedly written by him in early 2008), contrary to fact. Further, the document uses the same software (OpenOffice Writer) as used by Satoshi Nakamoto. 457. Dr Wright has positively asserted in these proceedings that this is a document on which he primarily relies as supporting his claim to be Satoshi Nakamoto. 458. The document bears Dr Wright’s name and contact details. 459. The contact details included refer to Charles Sturt University. In his evidence in these proceedings, Dr Wright has claimed to have drafted and shared versions of the Bitcoin White Paper while studying at Charles Sturt University, and to have discussed the concepts with teaching staff at Charles Sturt University. [Wright1 [87], Wright4 [52]]. 460. In his evidence in these proceedings, Dr Wright positively relies upon the presence of the word “Timecoin” in documents he has disclosed as being precursor work to the Bitcoin White Paper and thus forming part of the story behind his claim to be Satoshi Nakamoto. Moreover, on the basis of his narrative, this is a detail which would have been known to him and to few, if any, others. [Wright1 [26], Wright4 [6.c.x.]]. 461. The document contains metadata that purports to pre-date the Bitcoin White Paper, indicating efforts at backdating to support Dr Wright’s claim. 462. Dr Wright claims, in his chain of custody information, that only he drafted this document. 463. Dr Wright has stated in these proceedings that this was a draft of a document under the name TimeCoin which later became bitcoin. [Exhibit CSW-5] 464. Dr Wright has not disclosed the apparent intermediate document from which this document was created. [PM2 [63]]. (c) Dr Wright’s Explanations and COPA’s Rebuttal 465. Dr Wright sought to explain away a number of the anomalous findings by saying that both this document and the Bitcoin White Paper were originally created in LATEX and that the commands in the original code accounted for such features as (a) the notes being in a font which was the same as would later be used for tables in the White Paper; (b) the OBJ character; (c) indentation in empty lines corresponding to the size of flowcharts later featuring in the Bitcoin White Paper; and (d) irregularities in hyphenation. See {CSW/2/26} to {CSW/2/28}; {Day3/139:21} to {Day3/152:8}. 466. Dr Wright sought to explain away the content of the document matching the March 2009 version of the Bitcoin White Paper rather than the earlier released versions by claiming that he does not “write things linearly”. He claimed to have used text in this early document, edited it out again in the August and October 2008 versions of the White Paper and then added it back in again for the March 2009 version. See {CSW/2/28} to {CSW/2/29}; {Day3/153:9} to {Day3/154:10}. 467. Dr Wright sought to explain away the irregular metadata by saying that his use of “Xcopy and related tools” somehow accounted for it: {CSW/2/28}. 468. COPA submitted that this explanation should be rejected as dishonest for the following reasons: 468.1. The Bitcoin White Paper was not originally created in LATEX, as convincingly established by the expert evidence of Mr Rosendahl (which was agreed by Dr Wright’s expert, Mr Lynch, in the joint statement). There is equally no basis for saying that this document was originally created in LATEX. Furthermore, no LAT EX.tex file has been provided to support Dr Wright’s account in relation to the creation of this document. 468.2. The use of LATEX to create the document would not account for the presence of the OBJ (object replacement) character, which on the expert evidence is purely and simply an artefact of conversion from PDF: see PM2 [26-28] {H/17/8}. 468.3. Neither would the use of LATEX to create the document account for Dr Wright having predicted in a precursor document precisely the size required for diagrams and having applied coding to mark out indentations for the diagrams in what would be empty space in the document. 468.4. Neither would the use of LATEX to create the document account for there being irregular hyphenation in precisely the points where line breaks appear in the text of the Bitcoin White Paper. Dr Wright could only weakly account for this as him doing “unusual things” and deliberately including irregular hyphenation {Day3/10:11}. This explanation was nonsensical. Further, it assumed that his deliberate inclusion of irregular hyphenation just happened by coincidence to fall in the places where line breaks existed in the Bitcoin White Paper. 468.5. Dr Wright’s explanation for the irregular metadata was at odds with the independent expert evidence. It also assumed that this irregularity happened by coincidence to co-exist with the other irregularities, when in fact all suggest backdating. 468.6. Dr Wright’s explanation for the content of the document including changes which were made to the Bitcoin White Paper between its 2008 and 2009 versions is inherently unlikely. It also assumes that this irregularity happened by coincidence to co-exist with all the other irregularities, when in fact all suggest backdating. (d) Conclusion 469. The explanations gathered in Appendix 1 to Dr Wright’s Closing confirm his reliance on both this document and the Bitcoin White Paper being based on earlier LATEX files and his allegation that the diagrams were created with LATEX. I find those explanations to be false, in view of my more general finding that the Bitcoin White Paper was not produced in LATEX. Other explanations (the indentations, the supposed ‘steganographic watermarking’ and formatting irregularities) are just a desperate attempt to explain away Dr Wright’s failure to be able to reproduce the Bitcoin White Paper in LATEX. The ‘non-linear’ working explanation (see [468.6] above) is ridiculous, in the light of all the other evidence which clearly indicates that this document was forged by Dr Wright. I so conclude. Continue Reading Here. About HackerNoon Legal PDF Series: We bring you the most important technical and insightful public domain court case filings.

This court case retrieved on January 29, 2024, judiciary.uk is part of the public domain. The court-created documents are works of the federal government, and under copyright law, are automatically placed in the public domain and may be shared without legal restriction. COPA v. Wright, Court Filing, retrieved on January 29, 2024, is part of HackerNoon’s Legal PDF Series. You can jump to any part of this filing here. This part is 26 of 42. COPA v. Wright, Court Filing, retrieved on January 29, 2024, is part of HackerNoon’s Legal PDF Series . You can jump to any part of this filing here . This part is 26 of 42. HackerNoon’s Legal PDF Series HackerNoon’s Legal PDF Series here here 24. Timecoin ODT Whitepaper (Reliance Document) {ID_000254} 446. The document purports to be a precursor draft of the Bitcoin White Paper and is presented as if written by Dr Wright. It is dated in the period 6 May 2008 to 12 December 2008 in its metadata, and Dr Wright states its approximate date to be 6 May 2008 in his Chain of Custody information. (a) COPA’s Reasons for Alleging Forgery (a) COPA’s Reasons for Alleging Forgery 447. The document has been backdated. Rather than being a precursor document to the Bitcoin White Paper as it purports to be, this document has been created from the Bitcoin White Paper subsequently and edited in such a way that it appears as if it was precursor work. [PM2 60-64]]. 448. {ID_000254} has apparently been converted from the Bitcoin White Paper (which is a PDF) into a more easily editable format and has then undergone further conversions via intermediate documents [PM2 [60-64]]. Font configurations and the absence of diagrams are consistent with this conclusion [PM2 [17-28]]. No such intermediate document has been disclosed. 449. Diagrams have been omitted from this document as a result of the conversion process from PDF. The inclusion of the object replacement character ￼ within the document [a point where a diagram would be expected to appear is consistent with {ID_000254} being created by a process of conversion of a different document. [PM2 [28]]. 450. Where diagrams are absent, the document nevertheless preserves margin indentations from the Bitcoin White Paper PDF, but which do not match the content of the document. [PM2 [29-37]]. 451. The document irregularly contains words throughout in which hyphens ought to appear but are missing. This is not consistent with ordinary dictation or typing error but is as an artefact of conversion from PDF and backdating. [PM2 [38-44]]. 452. A conversion of the Bitcoin White Paper PDF to editable form would result in corruption of formulae. In each case where those formulae would have appeared corrupted, they have been deleted from {ID_000254}, leaving behind white space. [PM2 [45-48]]. 453. The document contains irregular line breaks consistent with conversion from the Bitcoin White Paper PDF into editable form and backdating. [PM2 [49-51]]. 454. The document contains text that matches the corrected text of the Bitcoin White Paper (2009 version) [PM2 [12]]. It does not match the October 2008 or November 2008 versions of the Bitcoin White Paper, even though this document purports to be earlier than both of them. 455. The document has been disclosed with irregular metadata listed in relation to its Created and Last Accessed external metadata properties. [PM2 [6-11]]. (b) COPA’s Reasons for Inferring Dr Wright’s Knowledge / Responsibility (b) COPA’s Reasons for Inferring Dr Wright’s Knowledge / Responsibility 456. The effect of the tampering is to make the document appear to be supportive of Dr Wright’s claim to be Satoshi Nakamoto (presenting as a predecessor draft of the Bitcoin White Paper and supposedly written by him in early 2008), contrary to fact. Further, the document uses the same software (OpenOffice Writer) as used by Satoshi Nakamoto. 457. Dr Wright has positively asserted in these proceedings that this is a document on which he primarily relies as supporting his claim to be Satoshi Nakamoto. 458. The document bears Dr Wright’s name and contact details. 459. The contact details included refer to Charles Sturt University. In his evidence in these proceedings, Dr Wright has claimed to have drafted and shared versions of the Bitcoin White Paper while studying at Charles Sturt University, and to have discussed the concepts with teaching staff at Charles Sturt University. [Wright1 [87], Wright4 [52]]. 460. In his evidence in these proceedings, Dr Wright positively relies upon the presence of the word “Timecoin” in documents he has disclosed as being precursor work to the Bitcoin White Paper and thus forming part of the story behind his claim to be Satoshi Nakamoto. Moreover, on the basis of his narrative, this is a detail which would have been known to him and to few, if any, others. [Wright1 [26], Wright4 [6.c.x.]]. 461. The document contains metadata that purports to pre-date the Bitcoin White Paper, indicating efforts at backdating to support Dr Wright’s claim. 462. Dr Wright claims, in his chain of custody information, that only he drafted this document. 463. Dr Wright has stated in these proceedings that this was a draft of a document under the name TimeCoin which later became bitcoin. [Exhibit CSW-5] 464. Dr Wright has not disclosed the apparent intermediate document from which this document was created. [PM2 [63]]. (c) Dr Wright’s Explanations and COPA’s Rebuttal (c) Dr Wright’s Explanations and COPA’s Rebuttal 465. Dr Wright sought to explain away a number of the anomalous findings by saying that both this document and the Bitcoin White Paper were originally created in LATEX and that the commands in the original code accounted for such features as (a) the notes being in a font which was the same as would later be used for tables in the White Paper; (b) the OBJ character; (c) indentation in empty lines corresponding to the size of flowcharts later featuring in the Bitcoin White Paper; and (d) irregularities in hyphenation. See {CSW/2/26} to {CSW/2/28}; {Day3/139:21} to {Day3/152:8}. 466. Dr Wright sought to explain away the content of the document matching the March 2009 version of the Bitcoin White Paper rather than the earlier released versions by claiming that he does not “write things linearly”. He claimed to have used text in this early document, edited it out again in the August and October 2008 versions of the White Paper and then added it back in again for the March 2009 version. See {CSW/2/28} to {CSW/2/29}; {Day3/153:9} to {Day3/154:10}. 467. Dr Wright sought to explain away the irregular metadata by saying that his use of “Xcopy and related tools” somehow accounted for it: {CSW/2/28}. 468. COPA submitted that this explanation should be rejected as dishonest for the following reasons: 468.1. The Bitcoin White Paper was not originally created in LATEX, as convincingly established by the expert evidence of Mr Rosendahl (which was agreed by Dr Wright’s expert, Mr Lynch, in the joint statement). There is equally no basis for saying that this document was originally created in LATEX. Furthermore, no LAT EX.tex file has been provided to support Dr Wright’s account in relation to the creation of this document. 468.2. The use of LATEX to create the document would not account for the presence of the OBJ (object replacement) character, which on the expert evidence is purely and simply an artefact of conversion from PDF: see PM2 [26-28] {H/17/8}. 468.3. Neither would the use of LATEX to create the document account for Dr Wright having predicted in a precursor document precisely the size required for diagrams and having applied coding to mark out indentations for the diagrams in what would be empty space in the document. 468.4. Neither would the use of LATEX to create the document account for there being irregular hyphenation in precisely the points where line breaks appear in the text of the Bitcoin White Paper. Dr Wright could only weakly account for this as him doing “unusual things” and deliberately including irregular hyphenation {Day3/10:11}. This explanation was nonsensical. Further, it assumed that his deliberate inclusion of irregular hyphenation just happened by coincidence to fall in the places where line breaks existed in the Bitcoin White Paper. 468.5. Dr Wright’s explanation for the irregular metadata was at odds with the independent expert evidence. It also assumed that this irregularity happened by coincidence to co-exist with the other irregularities, when in fact all suggest backdating. 468.6. Dr Wright’s explanation for the content of the document including changes which were made to the Bitcoin White Paper between its 2008 and 2009 versions is inherently unlikely. It also assumes that this irregularity happened by coincidence to co-exist with all the other irregularities, when in fact all suggest backdating. (d) Conclusion (d) Conclusion 469. The explanations gathered in Appendix 1 to Dr Wright’s Closing confirm his reliance on both this document and the Bitcoin White Paper being based on earlier LATEX files and his allegation that the diagrams were created with LATEX. I find those explanations to be false, in view of my more general finding that the Bitcoin White Paper was not produced in LATEX. Other explanations (the indentations, the supposed ‘steganographic watermarking’ and formatting irregularities) are just a desperate attempt to explain away Dr Wright’s failure to be able to reproduce the Bitcoin White Paper in LATEX. The ‘non-linear’ working explanation (see [468.6] above) is ridiculous, in the light of all the other evidence which clearly indicates that this document was forged by Dr Wright. I so conclude. Continue Reading Here. Continue Reading Here . Here About HackerNoon Legal PDF Series: We bring you the most important technical and insightful public domain court case filings. This court case retrieved on January 29, 2024, judiciary.uk is part of the public domain. The court-created documents are works of the federal government, and under copyright law, are automatically placed in the public domain and may be shared without legal restriction. About HackerNoon Legal PDF Series: We bring you the most important technical and insightful public domain court case filings. This court case retrieved on January 29, 2024, judiciary.uk is part of the public domain. The court-created documents are works of the federal government, and under copyright law, are automatically placed in the public domain and may be shared without legal restriction. judiciary.uk judiciary.uk

COPA Challenges Authenticity of Wright's Timecoin ODT Document

Stories, News & Mentions about AUTHENTICUS

Authenticus’s Stories on HackerNoon