Get the most recent info and news about DevBrews on HackerNoon, where 10k+ technologists publish stories for 4M+ monthly readers.

DevBrews

devbrews

Hey Hackers, DevBrews has been nominated in HackerNoon's annual awards in Sofia, Bulgaria. Startup of the Year Please vote for us here: https://hackernoon.com/startups/europe/europe-sofia-bulgaria Read more about us below to understand why we deserve your vote. Are you also participating in SOTY 2023? If so, . click here to fill out this interview Meet DevBrews We develop fully-featured marketplaces for startups and businesses to empower their growth. We provide highly customizable, modular, and scalable two-sided marketplace development for any use case and industry. You have identified a niche with high demand for the exchange of products, services, or information. We’ll help you with the marketplace software to make the exchange happen. My Role My passion for communities and network effects combined with my product understanding and experience with building software platforms helped me to specialize and concentrate our efforts on building online marketplace platforms for any type of business. This is how Devbrews was born! At our company, we have extensive experience in custom software development for online marketplace platforms. We understand that every business is unique, and that's why we offer highly customizable, modular, and scalable solutions that are tailored to meet your specific needs. How We're Disrupting/Improving the Marketplace Development Industry We believe custom marketplace development should be simple, cost-effective, and fast. Marketplace creators struggle with the infinite trade-offs between price, performance, personalization, and time to market. This is why we created a solution to help marketplace creators and owners effectively create platforms that meet all their needs together. Standing Out from The Crowd Unlike the no-code solutions, we will customize your platform to cover specific business requirements or add flavor that will make it stand out of the crowd. We have developed a bullet-proof UX approach and 99,99% uptime guarantee through a verified cloud provider, fully automated deployment, and DR strategies out of the box. The marketplace is fast, scalable with excellent user experience. Our Predictions/Thoughts on the Marketplace Development Industry in 2023 The marketplace industry is not new. It’s a growing industry that will even grow more in 2023 and the next 5-10 years. We all have seen great success stories like , , or which have inspired numerous marketplace creators in a variety of business niches. Airbnb Uber Upwork No-code and one-size fit all solutions like Sharetribe and Bubble helped to democratize this industry helping small companies and entrepreneurs quickly build their marketplaces and test their ideas. However, those technologies have their limitations and prevent marketplaces to stand out from the crowd. Within the growing industry companies will need more and more custom solutions to make products that users love and empower the network effects which are crucial to the success of every marketplace. What word defines the state of marketplace development industry in 2023? The online marketplace industry is in fast growth. Having more and more marketplace platforms urges the need for differentiation and scalability. Why we decided to participate in HackerNoon's Startup of the Year awards We are a small startup providing boutique products and solutions. We are constantly looking for ways to make sustainable products and happy customers. We strongly believe in the network effects and the Hackernoon community is a brilliant way to see the power of this. Final Thoughts We are driven by an obsession to make marketplace development easy and affordable. Moreover, DevBrews is a philosophy and passion, it’s a lean approach to building online marketplaces the right way. DevBrews is nominated as Startup of the Year in Sofia, Bulgaria. Vote for us today!

Growing Businesses with Robust Marketplaces - Interview with Startups of the Year Nominee, DevBrews

Negocios en crecimiento con mercados robustos: entrevista con el nominado a Startups del año, DevBrews

Entreprises en croissance avec des marchés robustes - Entretien avec le nominé des startups de l'année, DevBrews

मजबूत बाज़ारों के साथ बढ़ते व्यवसाय - वर्ष के नामांकित व्यक्ति, DevBrews के स्टार्टअप के साथ साक्षात्कार

堅牢なマーケットプレイスでビジネスを成長させる - スタートアップ オブ ザ イヤーにノミネートされた DevBrews へのインタビュー

Negócios em crescimento com mercados robustos - Entrevista com o candidato a startups do ano, DevBrews

Doanh nghiệp đang phát triển với thị trường mạnh mẽ - Phỏng vấn Ứng cử viên khởi nghiệp của năm, DevBrews

通过强大的市场不断成长的企业 - 采访年度初创公司提名者 DevBrews

Do you identify yourself as a developer advocate? Are you confident that your skills are being fully utilized in your current role? OR, Do you ever feel like your work requires more skills than what you currently possess? relations (DevRel, in short), both as a field and for those working within it, is currently facing a significant identity crisis. There is little to no standardization across various aspects of the role, from the type of work being done, to the required competencies, and even to the ideal career ladder. Developer This blog presents a somber view of the identity crisis currently plaguing DevRel. I conclude the blog with one action item YOU can take before irreparable damage is done to the very essence of our field’s identity. Forming the identity December 9, 1968. Douglas Engelbart took to the stage to perform what would become known as the . Little did the audience know that they were about to witness a demonstration that would forever change the course of computing history. “Mother of All Demos” Engelbart’s presentation was not just a showcase of his technological innovations, but it was also an invitation for developers to collaborate with him in advancing the field of human-computer interaction. Many credit Engelbart for first planting the seed of technology evangelism. However, is more widely known to pioneer the role of technology evangelist as the first successful one, promoting the Macintosh in the 1980s through his passionate speeches, demonstrations, and events. Guy Kawasaki Apple Around 2012-13, companies like EngineYard, Twilio, SendGrid, and New Relic took DevRel to the mainstream by investing heavily in their DevRel programs and reaching their developers from a community-first approach. Rather than traditional marketing materials, these companies had engineers presenting technical talks at meetups and conferences. Battling for an identity Long before I had the title of developer advocate, I was delivering talks, hosting meetups, and writing technical blogs on my own time. I was doing this out of joy and could never imagine that I could do this full-time (and get paid to do so). As a full-time doing the “DevRel thing” on the side, I didn’t have an identity crisis. I was just another software engineer who was active in writing and public speaking. When I started to do DevRel full-time, I asked myself “How valuable and visible is my work?”. Check out what Rachel has to say about the value of tech writing: software engineer https://twitter.com/rachelnabors/status/1647779097702199296?s=20&embedable=true https://twitter.com/rachelnabors/status/1647779097702199296?s=20&embedable=true This can be very much relatable to the perceived value of DevRel. https://twitter.com/rachelnabors/status/1647780297780641802?s=20&embedable=true It’s a for anyone in DevRel. Please bookmark! golden thread When I started my first official DevRel role at IBM, the answer to “What do you do at IBM?” never ended in one line as developer advocacy was new to most folks. I was tired of explaining my role every time so I . If you think that something clever like “I help developers to succeed” or “I educate developers on $someTechnology” would work, please try it out on someone who never heard of developer relations and then ask them back if they understood what you do from that clever one-liner. wrote a blog to explain How did we arrive at this point? Surprisingly enough… it’s because DevRel became highly successful! Seeing the massive success of DevRel programs at companies like Twilio and HashiCorp, other companies wanted to replicate. However, simply copying their models does not guarantee success. In fact, many tech companies that attempted to do so ended up failing in their DevRel programs. Without insider knowledge, here’s my calculated guess on the “why”: DevRel programs require a genuine commitment to developers and their needs. This means investing in resources like documentation, support channels, and events, as well as taking the time to engage with the developer community. Many companies see DevRel as an afterthought or a checkbox item, rather than a core part of their business strategy. Lack of genuine commitment: : Developers have a unique mindset and approach to problem-solving. They value tools that are easy to use, well-documented, and flexible. Companies that fail to understand this mindset may develop tools and resources that are too complex or too restrictive, which can turn developers off. Even the best DevRel team won’t be able to shine a poor product. Poor understanding of the developer mindset Developers are a discerning audience, and they can quickly sniff out inauthenticity. Companies that lack trust with the developer community, perhaps because of a history of closed-source practices or a lack of transparency, may struggle to build meaningful relationships with developers. Imagine that you (a developer advocate) went above and beyond on a developer event. You delivered a talk, spent hours on booth duties, and talked to a bunch of developers about the behind your product. You write a 9 page trip report with all the details and the CEO comes to you right after the event asking for an ROI. It’s extremely easy to lose the trust of the community as well as the trust of your own DevRel team. Lack of trust: technology Building a strong DevRel program requires a significant investment of time, money, and people. Companies that try to cut corners or skimp on resources may find that their DevRel efforts fall short. Sure, you can hire 3 junior folks to form a DevRel team but without senior people in the team to groom them, they’ll burn out fast with trying to do 10 things at a time and battling for an identity. Insufficient resources: Even with the best intentions and resources, DevRel programs can fail if they are poorly executed. This might include a lack of follow-through on promises, inconsistent messaging, or an inability to respond to developer feedback in a timely manner. Poor execution: Engineering? Marketing? Product? Office of CTO? Oh no! Not “where should DevRel sit” question again 🤬 An engineer typically works under the Engineering org, while an SDR works in Sales, and a marketing analyst works in Marketing. But where does a developer advocate fit in? Many of them are engineers by trade, work closely with the product team, (oftentimes) report to the marketing department, and can be great allies for sales reps without directly selling the product. Karin recently asked this same question which received . In these responses, people had eight different opinions on where DevRel should sit - from some flavors of “it depends” to “DevRel as a separate org” to “sales”. Out of all 31 responses, I share the same view as : 31 responses on Twitter Jim Bennett It’s such a cross functional org that there is no real right answer. Done well it’s such a strong collaboration across all the orgs that it should have access to marketing budget as well as product teams. Just not sales - it should never be tied to revenue. Had I responded to that thread, here would be my corollary to Jim’s response: Developer relations (DevRel), when done right, acts as a metaphorical glue among cross-functional teams, similar to the . DevRel, like the gold in Kintsugi, repairs fractured relationships or creates non-existing relationships between an organization and its target developer audience. It creates an environment based on authenticity and trust, without a direct purpose of “selling no matter what”. Japanese art of Kintsugi But is DevRel really a golden solution for everyone? Does every organization have the capacity to use the power of DevRel? The real cost of identity crisis Here’s a CEO asking if developer advocacy is a good idea or not. Here’s a programmer with ~40K Twitter followers who does not trust developer advocates because this person feels that developer advocates are just pitching people for their employers instead of people really helping developers. Here’s a company pitting DevRel teams against each other without even taking their consent. They have since taken down the post due to backlash. At the core of this confusion, there are two questions: What is DevRel? Why are we paying them? If we (the DevRel community) cannot have a unified answer to the first question, more and more people will question the effectiveness of DevRel. I don’t know about you but I’ve seen more than enough “And the entire DevRel team was let go” posts in the last few months. In a weak economy, you need a strong justification for the second question to save your job. Have we forgotten how to be engineers? I live in Canada so I’m aware that the term “engineer” has a special meaning in some places that is regulated by local engineering associations. However, my use of the term “engineer” refers to anyone who has professionally built software and hence, (software) engineer. This includes a wide variety of roles such as developers, SysAdmins, DBAs, Solution Architects, etc. It has nothing to do with your path to becoming a software engineer. Whether you’re a ComSci Ph.D. or a bootcamp grad, you possess a certain skillset that is common to expect from a majority of other software engineers. You know how to use version control, read a piece of code, write and debug code, and so on. In the last 10 years, the identity of DevRel has become more convoluted. When I started at IBM in 2014, there were very few developer advocates in the industry (compared to now). A developer advocate would be someone with decades (not years) of engineering experience who chose not to go the management or principal engineer route. They wanted to teach and share their experience. One of the common complaints DevRel folks have is that we don’t get a seat at the table in terms of product development and roadmap. Your peers at product or engineering will likely respect product feedback coming from an engineer than from someone who has very little to do with coding in their day-to-day job. Does it mean a developer advocate needs to regularly write code that runs in production? No! and are two extremes. At the bare minimum, you should be comfortable writing code samples and you should do that regularly as part of your job. “I know how to code and I’ll do it when needed (interpreted as )” is a dangerous mindset for a developer advocate. Zero coding writing production code daily never You aren’t gatekeeping… are you? When I express my view on developer advocates needing to be highly technical, I usually get three types of questions/comments: What about developer advocates who are more community-focused? : A developer advocate is the default role that comes to mind when people think about DevRel. If you’re a series-A startup and can only afford to have one person on your DevRel team, it’s likely that you’ll hire a developer advocate. This is why DevRel and developer advocate are often used interchangeably, even though one is a subset of the other. My response Out of the 3Cs (code, content, community), what % of code and technical content are you producing as a developer advocate? If the answer is “zero” or “very little”, you’re confusing developer advocates with community managers. A community manager is a super important role. At smaller companies, a developer advocate might be doing community management on top of their advocacy work. But and come first for a developer advocate, with work as a nice-to-have. code technical content community Are you trying to gatekeep? Not really; I’m simply sharing my opinions on DevRel ( ). A question back at you: can you maintain quality of anything without setting some level of standards? From a software engineer to a sales rep, there is clear and job description and expectations for every single role in tech industry; except DevRel! Most of what I’m saying have been said many times in the past by well-respected DevRel leaders. My response: on my personal blog unified But.. I have empathy for developers. Isn’t that enough? My response: Having empathy is important but empathy will not help you become a strong develper advocate. How does one cultivate empathy in the first place? Tim Berglund, a respected figure in DevRel and one of the best developer advocates out there, points out that genuine empathy for developers is challenging to achieve if you have never been a developer yourself. It’s almost impossible to truly understand their experiences and struggles without a background in engineering or coding. alone Tim goes on to explain that developers worldwide, regardless of spoken language, share a common dialect and inside jokes that only fellow developers can comprehend. This shared language and understanding of the developer’s world can only be acquired through years spent behind a keyboard, earning a livelihood by writing code. It is by going through similar challenges and experiences that one can truly develop the empathy necessary to connect with other developers. DevRel is NOT influencer marketing Once I had a recruiter reach out who was looking for a DevRel superstar with a certain Twitter follower count as part of the required skills on the job description. I was about to write this section and then heard Tim Berglund craft the same message perfectly. Listen to what Tim has to say about the influencer path vs. the traditional DevRel path ⤵️ https://www.youtube.com/live/9OmURvI9gwo?feature=share&t=1921&embedable=true You’re a developer advocate… what’s next? Around 2013-14, some of my IBM colleagues retired as developer advocates. This is after they became a developer advocate after working as a senior engineer for 20+ years. I wrote before that . In present days, some companies are hiring junior folks as a developer advocate (totally not to save on 💰) and then they are not providing them a DevRel career path to grow. developer advocacy is not an entry-level role If you’re a solo developer advocate, what does a promotion look like for you? If you’re manager of a DevRel team, do you have a defined career ladder at your company? At what point in your DevRel career do you reach a plateau, where staying in a DevRel role no longer offers further growth opportunities? Scanning the internet, I found with publicly posted DevRel career paths. Besides these four companies, I know a few more with defined career ladders for DevRel individual contributor (IC) but none for DevRel managers. From DevRel-ladders site: four companies Often one of the hardest challenges in Developer Relations is . Clarity around goals, metrics, place within the organization, but most importantly clarity about your career path. clarity When your DevRel team doesn’t have clarity, they’ll face an identity crisis and that’s the shortest path to burnout. But… there is hope If you’ve managed to read this far, thank you for your patience! There are three key things YOU can focus on in order to revive the lost identity of developer relations. If you’re a DevRel IC, focus on: Technical expertise Authenticity Optics You, as a developer advocate, need to showcase the technical expertise which is the foundation of helping your developers succeed. You have to do that in an authentic way and not treat every community member as a new lead in the marketing funnel. Besides doing the work, you have to be intentional in conveying the value of your work within your company. This is where the optics comes in. If you manage a DevRel team, focus on: Exec buy-in DevRel metrics Avoiding burn-outs Your exec team must understand the value of developer relations they hire the first developer advocate and they should be transparent in their support for DevRel. If you are in a difficult spot where you have to convince the leadership on DevRel ROI, understand what metrics are important for the exec team and find a direct/semi-direct relation with DevRel metrics. before Most people working in DevRel are eager to help and often find it challenging to say “no”. When this eagerness is coupled with a lack of clarity and clear expectations, it becomes the primary cause of DevRel burnout. It is crucial to prioritize the well-being of your team and foster a sense of psychological safety within the organization. My hope from this blog is to inspire you, the reader, to revive the lost identity of developer relations and help developers succeed. Remember, DevRel is the only team at your company that can speak the engineer’s language, provide regular feedback to the product team, function as a marketing team, and grow the community as the face of your company. Also published here.

Identity Crisis: A Story of DevRel's Journey

Ali Pacha by Alexandre Dumas, is part of the HackerNoon Books Series. You can jump to any chapter in this book here . Chapter VI CHAPTER VI Ali had long cherished a violent passion for Zobeide, the wife of his son Veli Pacha: Having vainly attempted to gratify it after his son’s departure, and being indignantly repulsed, he had recourse to drugs, and the unhappy Zobeide remained in ignorance of her misfortune until she found she was pregnant. Then, half-avowals from her women, compelled to obey the pacha from fear of death, mixed with confused memories of her own, revealed the whole terrible truth. Not knowing in her despair which way to turn, she wrote to Ali, entreating him to visit the harem. As head of the family, he had a right to enter, being supposed responsible for the conduct of his sons’ families, no-law-giver having hitherto contemplated the possibility of so disgraceful a crime. When he appeared, Zobeide flung herself at his feet, speechless with grief. Ali acknowledged his guilt, pleaded the violence of his passion, wept with his victim, and entreating her to control herself and keep silence, promised that all should be made right. Neither the prayers nor tears of Zobeide could induce him to give up the intention of effacing the traces of his first crime by a second even more horrible. But the story was already whispered abroad, and Pacho Bey learnt all its details from the spies he kept in Janina. Delighted at the prospect of avenging himself on the father, he hastened with his news to the son. Veli Pacha, furious, vowed vengeance, and demanded Pacho Bey’s help, which was readily promised. But Ali had been warned, and was not a man to be taken unawares. Pacho Bey, whom Veli had just promoted to the office of sword-bearer, was attacked in broad daylight by six emissaries sent from Janina. He obtained timely help, however, and five of the assassins, taken red-handed, were at once hung without ceremony in the market-place. The sixth was the messenger whose arrival with the news had caused such dismay at Ali’s banquet. As Ali reflected how the storm he had raised could best be laid, he was informed that the ruler of the marriage feast sent by Moustai, Pacha of Scodra, to receive the young bride who should reign in his harem, had just arrived in the plain of Janina. He was Yussuf Bey of the Delres, an old enemy of Ali’s, and had encamped with his escort of eight hundred warriors at the foot of Tomoros of Dodona. Dreading some treachery, he absolutely refused all entreaties to enter the town, and Ali seeing that it was useless to insist, and that his adversary for the present was safe, at once sent his grand-daughter, the Princess of Aulis, out to him. This matter disposed of, Ali was able to attend to his hideous family tragedy. He began by effecting the disappearance of the women whom he had been compelled to make his accomplices; they were simply sewn up in sacks by gipsies and thrown into the lake. This done, he himself led the executioners into a subterranean part of the castle, where they were beheaded by black mutes as a reward for their obedience. He then sent a doctor to Zobeide; who succeeded in causing a miscarriage, and who, his work done, was seized and strangled by the black mutes who had just beheaded the gipsies. Having thus got rid of all who could bear witness to his crime, he wrote to Veli that he might now send for his wife and two of his children, hitherto detained as hostages, and that the innocence of Zobeide would confound a calumniator who had dared to assail him with such injurious suspicions. When this letter arrived, Pacho Bey, distrusting equally the treachery of the father and the weakness of the son, and content with having sown the seeds of dissension in his enemy’s family, had sufficient wisdom to seek safety in flight. Ali, furious, vowed, on hearing this, that his vengeance should overtake him even at the ends of the earth. Meanwhile he fell back on Yussuf Bey of the Debres, whose escape when lately at Janina still rankled in his mind. As Yussuf was dangerous both from character and influence, Ali feared to attack him openly, and sought to assassinate him. This was not precisely easy; for, exposed to a thousand dangers of this kind, the nobles of that day were on their guard. Steel and poison were used up, and another way had to be sought. Ali found it. One of the many adventurers with whom Janina was filled penetrated to the pacha’s presence, and offered to sell the secret of a powder whereof three grains would suffice to kill a man with a terrible explosion—explosive powder, in short. Ali heard with delight, but replied that he must see it in action before purchasing. In the dungeons of the castle by the lake, a poor monk of the order of St. Basil was slowly dying, for having boldly refused a sacrilegious simony proposed to him by Ali. He was a fit subject for the experiment, and was successfully blown to pieces, to the great satisfaction of Ali, who concluded his bargain, and hastened to make use of it. He prepared a false firman, which, according to custom, was enclosed and sealed in a cylindrical case, and sent to Yussuf Bey by a Greek, wholly ignorant of the real object of his mission. Opening it without suspicion, Yussuf had his arm blown off, and died in consequence, but found time to despatch a message to Moustai Pacha of Scodra, informing him of the catastrophe, and warning him to keep good guard. Yussuf’s letter was received by Moustai just as a similar infernal machine was placed in his hands under cover to his young wife. The packet was seized, and a careful examination disclosed its nature. The mother of Moustai, a jealous and cruel woman, accused her daughter-in-law of complicity, and the unfortunate Ayesha, though shortly to become a mother, expired in agony from the effects of poison, only guilty of being the innocent instrument of her grandfather’s treachery. Fortune having frustrated Ali’s schemes concerning Moustai Pacha, offered him as consolation a chance of invading the territory of Parga, the only place in Epirus which had hitherto escaped his rule, and which he greedily coveted. Agia, a small Christian town on the coast, had rebelled against him and allied itself to Parga. It provided an excuse for hostilities, and Ali’s troops, under his son Mouktar, first seized Agia, where they only found a few old men to massacre, and then marched on Parga, where the rebels had taken refuge. After a few skirmishes, Mouktar entered the town, and though the Parganiotes fought bravely, they must inevitably have surrendered had they been left to themselves. But they had sought protection from the French, who had garrisoned the citadel, and the French grenadiers descending rapidly from the height, charged the Turks with so much fury that they fled in all directions, leaving on the field four “bimbashis,” or captains of a thousand, and a considerable number of killed and wounded. The pacha’s fleet succeeded no better than his army. Issuing from the Gulf of Ambracia, it was intended to attack Parga from the sea, joining in the massacre, and cutting off all hope of escape from that side, Ali meaning to spare neither the garrison nor any male inhabitants over twelve years of age. But a few shots fired from a small fort dispersed the ships, and a barque manned by sailors from Paxos pursued them, a shot from which killed Ali’s admiral on his quarter-deck. He was a Greek of Galaxidi, Athanasius Macrys by name. Filled with anxiety, Ali awaited news at Prevesa, where a courier, sent off at the beginning of the action, had brought him oranges gathered in the orchards of Parga. Ali gave him a purse of gold, and publicly proclaimed his success. His joy was redoubled when a second messenger presented two heads of French soldiers, and announced that his troops were in possession of the lower part of Parga. Without further delay he ordered his attendants to mount, entered his carriage, and started triumphantly on the Roman road to Nicopolis. He sent messengers to his generals, ordering them to spare the women and children of Parga, intended for his harem, and above all to take strict charge of the plunder. He was approaching the arena of Nicopolis when a third Tartar messenger informed him of the defeat of his army. Ali changed countenance, and could scarcely articulate the order to return to Prevesa. Once in his palace, he gave way to such fury that all around him trembled, demanding frequently if it could be true that his troops were beaten. “May your misfortune be upon us!” his attendants answered, prostrating themselves. All at once, looking out on the calm blue sea which lay before his windows, he perceived his fleet doubling Cape Pancrator and re-entering the Ambracian Gulf under full sail; it anchored close by the palace, and on hailing the leading ship a speaking trumpet announced to Ali the death of his admiral, Athanasius Macrys. “But Parga, Parga!” cried Ali. “May Allah grant the pacha long life! The Parganiotes have escaped the sword of His Highness.” “It is the will of Allah!” murmured the pacha; whose head sank upon his breast in dejection. Arms having failed, Ali, as usual, took refuge in plots and treachery, but this time, instead of corrupting his enemies with gold, he sought to weaken them by division. About HackerNoon Book Series: We bring you the most important technical, scientific, and insightful public domain books. This book is part of the public domain. Alexandre Dumas (2006). Ali Pacha. Urbana, Illinois: Project Gutenberg. Retrieved https://www.gutenberg.org/cache/epub/2753/pg2753-images.html This eBook is for the use of anyone anywhere at no cost and with almost no restrictions whatsoever. You may copy it, give it away or re-use it under the terms of the Project Gutenberg License included with this eBook or online at www.gutenberg.org , located at https://www.gutenberg.org/policy/license.html .

Ali had long cherished a violent passion for Zobeide

We are the team and would like to participate in the . Well. Let's get started. Hello everyone! Free TON Ecosystem #Decentralized-Internet Writing Contest Plan Prehistory Concept End DeNet Prehistory We got the idea of ​​a decentralized Internet somehow suddenly, and we didn't even know about the existence of such a competition. But since it so happened that the competition exists, why not take part, right? :) DeNet Concept So, our concept in a nutshell can be described as . Unfortunately, the real network has , for example, such as 16 KB per message, and we to fully deploy the static code in the blockchain but we can easily get around it by breaking messages into several blocks of size at . placing static inside a smart contract main.ton.dev very critical limitations will not be able 15.99 KB In the end, we can create or with intended for hosting sites, for example , and you can for a certain amount of TON Crystal. So, conditionally, we have a network specially configured to work with , their coins have a rate (value). denet.ton.dev freenet.ton.dev our own currency 🌎 DeCoins get them by exchanging them for DeFi DeNet Now it is necessary to solve the question of how to store these very statics. There are two options: The first is to . It seems to us that this approach will not always be advantageous. store the HTML code in variables at a smart contract 2. The second is . In the foreseeable future, in our opinion, it is not worth waiting for now, but when it appears, we will be able to deploy the statics properly. TON Storage Let's Go Back to DeNet: We Want to Introduce DHTTP - Decentralized HTTP Methods such as, for example, , , , and others will be written in the code of the contract (interface), which allows us to interact with the internal database (in any form, but still a database). GET POST PUT DELETE We will also store an array where (we'll come back later) will get the available routes. But what kind of site can it be if you can't interact with it. routes DeBrowser We introduce an array that . The programmer who writes the code for the DeNet site . We will give an example with our project - . owners can change routing, site configuration, and other metadata can change and add their own functions for their own needs Free TON Ecosystem The has the right to add his project to the general list by entering the required data. But what happens when he clicks the add button? guest The request is sent to the smart contract, to the same method, from where it gets to another method specified in the array. GET routes Then it goes through authorization (guest or owner), and is passed to other middleware, for example - creating a project (adding information to the mapping), and ultimately the contract sends a response to DeBrowser. Now, as promised, back to DeBrowser. This is . Unfortunately, to receive a response from a site hosted in DeNet. a special contract that the client deploys this is a mandatory procedure This contract has its own set of methods, which can, for example, display an error message, success message to the user, or execute arbitrary JavaScript code (to replace the code in real mode). But in fact, . DeBrowser is just the same Internet browser, but configured to interact with the blockchain Let's not be scattered, and clearly define the methods for each of the contracts. DeNet Endpoint get(string uri)
post(string uri, string[] array)
head(string uri, string[] array)
put(string uri, string[] array)
delete(string uri, string[] array)
exists(string uri)
selfDestruct()
getDHTTPVersion() // 1.0, for example

// Other methods writen by developer DeBrowser successCallback(address page, string message)
errorCallback(address page, string message)
infoCallback(address page, string message)
updateCallback(address page, string message)
dhttpcodeCallback(address page, uint code) // 404, for example
existsCallback(bool status) DeNS (+ search system) getAddress(string domain) //ton.eco, for example, to 0:....
setAddress(address page, string domain)
setMeta(address page, string meta) // 0.... and Free TON Ecosystem
searchAddress(string data) // Free TON Ecosystem -> from meta 
removeMeta(address page) // Remove from search system
getAll()
setDesc(address page, string desc) // Set description for site
removeAddress(address page)
inactivePage(address page) // set incative status
setDHTTPVersion(address page, string version)

// Other methods writen by DeNS, for example:
incrementViews(address page) The shown code is just an example of how we imagine this. Consider this. As you may have noticed, we have also described for DeNet. It is imperative that these methods in the DeNet system, . DeNS be in every contract otherwise DeBrowser will not be able to work Now we come to . After all, each DeNet-endpoint must be safe for viewing by the end user. Therefore, we must make a , which will check the security contract (the existence of any methods) and return the result. safety DeValidator DeValidator ableToWork(address page, uint type)

// Other methods, for example:
checkOnBlacklist(address page) can be public. must also have support for all versions, having previously obtained it by calling the DeNet Endpoint method ( ), or by obtaining it from . DeValidator DeBrowser DHTTP getDHTTPVersion() DeNS By the way, a , that is, hosting a site. After that, users will be able to access your site. But the big disadvantage is that the user will have to pay to deploy . At the same time, . huge advantage of DeNet is a one-time payment for deploying a contract DeBrowser DeBrowser you do not have to think about authorization by login and password, you will be already authorized by signing messages with DeBrowser keys Final Thoughts We hope you liked our article! If you like this concept, we will definitely continue to develop it. We sincerely want to develop DeNet, but we need funds and experienced staff. This concludes the first part of the DeNet concept, but rest assured, . we'll be back See you soon! You can write to us on for more information or help. Telegram

Stories, News & Mentions about DEVBREWS

Devbrews’s Stories on HackerNoon