#foss = free open source software now and forever

[amalgamasreal]

FOSS IS LOVE

FOSS IS LIFE

[terriinet]

Diptrace import eagle library

Diptrace import eagle library update#

Diptrace import eagle library manual#

Diptrace import eagle library software#

Diptrace import eagle library password#

Diptrace import eagle library software#

Yes, true Free/Open Source Software (FOSS) EDA tools generally are not the same as their commercial counterparts. There are very capable open-source programs though (Linux, Firefox, Open Office), but usually they also earn money, but from other sources. The pluses is it is free, open source and cross-platform, minuses - usually it has more bugs, is less capable and no support if compare to the software which is made and supported by full-time employees who earn money from their work. There are both pluses and minuses on free open-source software. Good luck with your project! Thanks and have a nice day! Yes, they look good now but either or both could disappear in an instant. There is a very real risk of getting stranded or orphaned with either Eagle or DipTrace. Seriously, from a strategic view point using F/OSS EDA tools makes a lot of sense. The UI has improved dramatically over the last couple of years and KiCAD rivals its commercial peers in usability and quality. You certainly cannot beat the price (free) and it is very capable. There are tutorials available and it works well. The learning curve on gEDA can be steep but you can start using KiCAD with small projects relatively easily. Much hobbyist project effort has been lost due to using commercial tools! There have been *many* commercial EDA tools which have disappeared over the years leaving hordes of stranded orphans with no support at all. Also since they are free/open source you can publish the schematics and PCB layout without fear of them being lost because of some unsupportable commercial format when the company disappears. Both are excellent packages and you can use them unlimited to create whatever hobbyist project you want. The solution is to use either gEDA or KiCAD which are both Free/Open Source software. Those designs are not possible with the entry editions of either Eagle or DipTrace. I have several Euroboard (160x100 mm) designs that exceed 1000 holes. Commercial EDA software uses proprietary and *non-portable* formats so once you start you are stuck with them forever unless you are willing to recreate your designs in another EDA tool. It will not take much of a project to exceed the limitations of either programs beginner editions and by then it will be too late. Both are commercial programs and are severely limited. Hi! IMO, neither Eagle nor DipTrace are appropriate software for hobbyist EDA.

Diptrace import eagle library password#

to moderator: Captha doesn't work on password reminder (always says it is incorrect), so I have registered new account. Also this version will have new pattern libraries (+ all patterns have standartized names, which are similar to patterns inside component libraries).

Diptrace import eagle library manual#

In the next release (2.2) we add net classes with multiple rules set, strict via styles to easily handle blind/buried vias, 3D preview and significantly improve manual routing + many minor improvements. Also all libraries/designs are separate files (you operates with them like with all other windows files).

Diptrace import eagle library update#

when you change footpring in some library - it will not be automatically changed in schematic/pcb files where you placed it (you can update it manually though). Currently each program has independent data, i.e. We plan to redesign library/file connection/search system in version 2.3 (maybe will also add project file which unites all data and updates automatically). They also have a few issues with the way they handle their library folders. Handling a large bom is a bit of trouble. The PCB design and Schematic is ok, but coordination between the four editor programs (pcb, schematic, component, design) is lacking in some regards.

[landoinghomework]

H/FOSS: history and philosophy

Whenever my friends from other majors ask what I have to do for my senior seminar, I find it hard to explain for them that we are working on a free open-source project. I mean, it doesn’t sound cool like business students who try to propose and run a business, we are also not humanitarian majors, who have to write a 50-page long thesis to be able to graduate. At times, I simply resolve to saying that we are working on a coding project.

What is FOSS?

But what is a free open-source software (FOSS)? It’s not only an app or a website that we can use for free on the Internet. It is more than that. Sometimes, the software that you are paying money for has also a part of FOSS too. FOSS has been a huge part in the development of software history and without it, we would be amazed to find out the Internet right now would not be the same. 

A free open-source software means that the source code is open for everyone to use, distribute, and modify it. FOSS also allows users to freely contribute to the source code, and by doing so improve the software even more. 

History 

Software sharing has been as old as the stare of the software itself. Many people in the early age who were able to get a computer were highly educated - they wanted to modify the software and make it better. Manufacturers even encouraged this as they put a heavier emphasis on the hardware and of course, when their products improved, it became more profitable for them. 

As the technology industry matured, hardware was treated as less of a priority and now manufactures focused on developing their software instead. More copyrights reinforcement made it hard for people to freely distribute and share the software. By doing so, proprietary companies can get more profits by selling the machine and the “added values” that come with it. 

But the world would be boring if people adhered to rules without questioning it. There has to be someone who would stand up against these capitalists and do something, right? And that person is Richard Stallman. He started the GNU Project and the Free Software Foundation. Stallman (along with Linus Torvalds) created a new operating system that is essentially the backbone of a lot of many computers today - the only difference is that it is freely used and distributed by everyone. In addition, he also invented a new copyright license - GNU General Public License (GPL) that guarantees his code, or any other software that uses his code will be forever free. 

Philosophy

One other open-source project that was created was the Berkeley Software Distribution (BSD). They did not raise any political statements about propriety properties, but they still practiced FOSS. More and more organizations were created with this philosophy of making the software free and easily distributed. 

The philosophical ideology is divided between software engineers. Some think it is absolutely necessary that people stand together and fight against propriety companies. Others take a more neutral role - they don’t have a problem with it, they just get excited to work and improve the technology that they are using. Just like any political arguments, there’s no ending to it - they just eventually collaborate and live together like communist and capitalist countries. The free open-source projects produce some very high-quality code, and businesses started to take notice of them. Propriety companies aren’t decreasing, and neither are FOSS. 

What do I think?

Like a computer science major, I have never thought much about politics, let alone software politics. However, I have noticed more open-source projects now belong to private companies (some of them can be found in the photo). Pull requests from users (non-employees) rarely ever gets noticed or merged. But it is still a good platform to get feedback from people who are using/ understanding the product as well. If the technology that I am using gets better, I have no complains. 

[alaingonza]

Insights into Why Hyperbola GNU/Linux is Turning into Hyperbola BSD

In late December 2019, Hyperbola announced that they would be making major changes to their project. They have decided to drop the Linux kernel in favor of forking the OpenBSD kernel. This announcement only came months after Project Trident announced that they were going in the opposite direction (from BSD to Linux).

Hyperbola also plans to replace all software that is not GPL v3 compliant with new versions that are.

To get more insight into the future of their new project, I interviewed Andre, co-founder of Hyperbola.

Why Hyperbola GNU/Linux Turned into Hyperbola BSD

It’s FOSS: In your announcement, you state that the Linux kernel is “rapidly proceeding down an unstable path”. Could you explain what you mean by that?

Andre: First of all, it’s including the adaption of DRM features such as HDCP (High-bandwidth Digital Content Protection). Currently there is an option to disable it at build time, however there isn’t a policy that guarantees us that it will be optional forever.

Historically, some features began as optional ones until they reached total functionality. Then they became forced and difficult to patch out. Even if this does not happen in the case of HDCP, we remain cautious about such implementations.

Another of the reasons is that the Linux kernel is no longer getting proper hardening. Grsecurity stopped offering public patches several years ago, and we depended on that for our system’s security. Although we could use their patches still for a very expensive subscription, the subscription would be terminated if we chose to make those patches public.

Such restrictions goes against the FSDG principles that require us to provide full source code, deblobbed, and unrestricted, to our users.

KSPP is a project that was intended to upstream Grsec into the kernel, but thus far it has not come close to reaching Grsec / PaX level of kernel hardening. There also has not been many recent developments, which leads us to believe it is now an inactive project for the most part.

Lastly, the interest in allowing Rust modules into the kernel are a problem for us, due to Rust trademark restrictions which prevent us from applying patches in our distribution without express permission. We patch to remove non-free software, unlicensed files, and enhancements to user-privacy anywhere it is applicable. We also expect our users to be able to re-use our code without any additional restrictions or permission required.

This is also in part why we use UXP, a fully free browser engine and application toolkit without Rust, for our mail and browser applications.

Due to these restrictions, and the concern that it may at some point become a forced build-time dependency for the kernel we needed another option.

It’s FOSS: You also said in the announcement that you would be forking the OpenBSD kernel. Why did you pick the OpenBSD kennel over the FreeBSD, the DragonflyBSD kernel or the MidnightBSD kernel?

Andre: OpenBSD was chosen as our base for hard-forking because it’s a system that has always had quality code and security in mind.

Some of their ideas which greatly interested us were new system calls, including pledge and unveil which adds additional hardening to userspace and the removal of the systrace system policy-enforcement tool.

They also are known for Xenocara and LibreSSL, both of which we had already been using after porting them to GNU/Linux-libre. We found them to be well written and generally more stable than Xorg/OpenSSL respectively.

None of the other BSD implementations we are aware of have that level of security. We also were aware LibertyBSD has been working on liberating the OpenBSD kernel, which allowed us to use their patches to begin the initial development.

It’s FOSS: Why fork the kernel in the first place? How will you keep the new kernel up-to-date with newer hardware support?

Andre: The kernel is one of the most important parts of any operating system, and we felt it is critical to start on a firm foundation moving forward.

For the first version we plan to keep in synchronization with OpenBSD where it is possible. In future versions we may adapt code from other BSDs and even the Linux kernel where needed to keep up with hardware support and features.

We are working in coordination with Libreware Group (our representative for business activities) and have plans to open our foundation soon.

This will help to sustain development, hire future developers and encourage new enthusiasts for newer hardware support and code. We know that deblobbing isn’t enough because it’s a mitigation, not a solution for us. So, for that reason, we need to improve our structure and go to the next stage of development for our projects.

It’s FOSS: You state that you plan to replace the parts of the OpenBSD kernel and userspace that are not GPL compatible or non-free with those that are. What percentage of the code falls into the non-GPL zone?

Andre: It’s around 20% in the OpenBSD kernel and userspace.

Mostly, the non-GPL compatible licensed parts are under the Original BSD license, sometimes called the “4-clause BSD license” that contains a serious flaw: the “obnoxious BSD advertising clause”. It isn’t fatal, but it does cause practical problems for us because it generates incompatibility with our code and future development under GPLv3 and LGPLv3.

The non-free files in OpenBSD include files without an appropriate license header, or without a license in the folder containing a particular component.

If those files don’t contain a license to give users the four essential freedoms or if it has not been explicitly added in the public domain, it isn’t free software. Some developers think that code without a license is automatically in the public domain. That isn’t true under today’s copyright law; rather, all copyrightable works are copyrighted by default.

The non-free firmware blobs in OpenBSD include various hardware firmwares. These firmware blobs occur in Linux kernel also and have been manually removed by the Linux-libre project for years following each new kernel release.

They are typically in the form of a hex encoded binary and are provided to kernel developers without source in order to provide support for proprietary-designed hardware. These blobs may contain vulnerabilities or backdoors in addition to violating your freedom, but no one would know since the source code is not available for them. They must be removed to respect user freedom.

It’s FOSS: I was talking with someone about HyperbolaBSD and they mentioned HardenedBSD. Have you considered HardenedBSD?

Andre: We had looked into HardenedBSD, but it was forked from FreeBSD. FreeBSD has a much larger codebase. While HardenedBSD is likely a good project, it would require much more effort for us to deblob and verify licenses of all files.

We decided to use OpenBSD as a base to fork from instead of FreeBSD due to their past commitment to code quality, security, and minimalism.

It’s FOSS: You mentioned UXP (or Unified XUL Platform). It appears that you are using Moonchild’s fork of the pre-Servo Mozilla codebase to create a suite of applications for the web. Is that about the size of it?

Andre: Yes. Our decision to use UXP was for several reasons. We were already rebranding Firefox as Iceweasel for several years to remove DRM, disable telemetry, and apply preset privacy options. However, it became harder and harder for us to maintain when Mozilla kept adding anti-features, removing user customization, and rapidly breaking our rebranding and privacy patches.

After FF52, all XUL extensions were removed in favor of WebExt and Rust became enforced at compile time. We maintain several XUL addons to enhance user-privacy/security which would no longer work in the new engine. We also were concerned that the feature limited WebExt addons were introducing additional privacy issues. E.g. each installed WebExt addon contains a UUID which can be used to uniquely and precisely identify users (see Bugzilla 1372288).

After some research, we discovered UXP and that it was regularly keeping up with security fixes without rushing to implement new features. They had already disabled telemetry in the toolkit and remain committed to deleting all of it from the codebase.

We knew this was well-aligned with our goals, but still needed to apply a few patches to tweak privacy settings and remove DRM. Hence, we started creating our own applications on top of the toolkit.

This has allowed us to go far beyond basic rebranding/deblobbing as we were doing before and create our own fully customized XUL applications. We currently maintain Iceweasel-UXP, Icedove-UXP and Iceape-UXP in addition to sharing toolkit improvements back to UXP.

It’s FOSS: In a forum post, I noticed mentions of HyperRC, HyperBLibC, and hyperman. Are these forks or rewrites of current BSD tools to be GPL compliant?

Andre: They are forks of existing projects.

Hyperman is a fork of our current package manager, pacman. As pacman does not currently work on BSD, and the minimal support it had in the past was removed in recent versions, a fork was required. Hyperman already has a working implementation using LibreSSL and BSD support.

HyperRC will be a patched version of OpenRC init. HyperBLibC will be a fork from BSD LibC.

It’s FOSS: Since the beginning of time, Linux has championed the GPL license and BSD has championed the BSD license. Now, you are working to create a BSD that is GPL licensed. How would you respond to those in the BSD community who don’t agree with this move?

Andre: We are aware that there are disagreements between the GPL and BSD world. There are even disagreements over calling our previous distribution “GNU/Linux” rather than simply “Linux”, since the latter definition ignores that the GNU userspace was created in 1984, several years prior to the Linux kernel being created by Linus Torvalds. It was the two different software combined that make a complete system.

Some of the primary differences from BSD, is that the GPL requires that our source code must be made public, including future versions, and that it can only be used in tandem with compatibly licensed files. BSD systems do not have to share their source code publicly, and may bundle themselves with various licenses and non-free software without restriction.

Since we are strong supporters of the Free Software Movement and wish that our future code remain in the public space always, we chose the GPL.

It’s FOSS: I know at this point you are just starting the process, but do you have any idea who you might have a usable version of HyperbolaBSD available?

Andre: We expect to have an alpha release ready by 2021 (Q3) for initial testing.

It’s FOSS: How long will you continue to support the current Linux version of Hyperbola? Will it be easy for current users to switch over to?

Andre: As per our announcement, we will continue to support Hyperbola GNU/Linux-libre until 2022 (Q4). We expect there to be some difficulty in migration due to ABI changes, but will prepare an announcement and information on our wiki once it is ready.

It’s FOSS: If someone is interested in helping you work on HyperbolaBSD, how can they go about doing that? What kind of expertise would you be looking for?

Andre: Anyone who is interested and able to learn is welcome. We need C programmers and users who are interested in improving security and privacy in software. Developers need to follow the FSDG principles of free software development, as well as the YAGNI principle which means we will implement new features only as we need them.

Users can fork our git repository and submit patches to us for inclusion.

It’s FOSS: Do you have any plans to support ZFS? What filesystems will you support?

Andre: ZFS support is not currently planned, because it uses the Common Development and Distribution License, version 1.0 (CDDL). This license is incompatible with all versions of the GNU General Public License (GPL).

It would be possible to write new code under GPLv3 and release it under a new name (eg. HyperZFS), however there is no official decision to include ZFS compatibility code in HyperbolaBSD at this time.

We have plans on porting BTRFS, JFS2, NetBSD’s CHFS, DragonFlyBSD’s HAMMER/HAMMER2 and the Linux kernel’s JFFS2, all of which have licenses compatible with GPLv3. Long term, we may also support Ext4, F2FS, ReiserFS and Reiser4, but they will need to be rewritten due to being licensed exclusively under GPLv2, which does not allow use with GPLv3. All of these file systems will require development and stability testing, so they will be in later HyperbolaBSD releases and not for our initial stable version(s).

I would like to thank Andre for taking the time to answer my questions and for revealing more about the future of HyperbolaBSD.

What are your thoughts on Hyperbola switching to a BSD kernel? What do you think about a BSD being released under the GPL? Please let us know in the comments below.

If you found this article interesting, please take a minute to share it on social media, Hacker News or Reddit.

from It's FOSS https://itsfoss.com/hyperbola-linux-bsd/

Insights into Why Hyperbola GNU/Linux is Turning into Hyperbola BSD was initially seen on http://alaingonza.com/

from https://alaingonza.com/2020/01/16/insights-into-why-hyperbola-gnu-linux-is-turning-into-hyperbola-bsd/

[johanlouwers]

GitHub Announces that Free Accounts Now Can Create Private Repositories, Bash-5.0 Released, iPhone Apps Linked to Golduck Malware, Godot Game Engine Reaches 3.1 Beta, NSA to Open-Source Its GHIDRA Reverse-Engineering Tool

News briefs for January 8, 2019.

GitHub's CEO Nat Friedman yesterday announced that free accounts now can create private repositories (previously only paid accounts could have private repositories). Ars Technica reports that "Now every GitHub account can create an unlimited number of private repositories. These are still restricted—only three people can collaborate on these repositories—but a great many of those projects that once had no option but to be opened up might now be marked as private." The Ars Technica article also expresses concern that one possibility with this change is that "programs that would previously have been published as open source will now be closed up forever".

Bash-5.0 was released yesterday. This release fixes several bugs and introduces many new features. From the release announcement: "The most notable new features are several new shell variables: BASH_ARGV0, EPOCHSECONDS, and EPOCHREALTIME. The `history' builtin can remove ranges of history entries and understands negative arguments as offsets from the end of the history list. There is an option to allow local variables to inherit the value of a variable with the same name at a preceding scope. There is a new shell option that, when enabled, causes the shell to attempt to expand associative array subscripts only once (this is an issue when they are used in arithmetic expressions). The `globasciiranges' shell option is now enabled by default; it can be set to off by default at configuration time."

Security researchers at Wandera recently discovered "more than a dozen iPhone apps covertly communicating with a server associated with Golduck, a historically Android-focused malware that infects popular classic game apps." According to TechCrunch, the malware was discovered more than a year ago and affected retro-style games on Google Play "by embedding backdoor code that allowed malicious payloads to be silently pushed to the device". See the post for more details.

Godot, the open-source, cross-platform game engine, announced it has entered the beta phase for Godot 3.1. New features include the OpenGL ES 2.0 renderer, visual shader editor, improved animation editor, WebSockets support and much more. See the Changelog for the full list. Note that this is a beta build and not intended for use in production.

The NSA plans to open-source its GHIDRA reverse-engineering tool. It's FOSS reports that senior NSA advisor Robert Joyce wrote in his session description for the March RSA Conference 2019, "NSA has developed a software reverse engineering framework known as GHIDRA, which will be demonstrated for the first time at RSAC 2019. An interactive GUI capability enables reverse engineers to leverage an integrated set of features that run on a variety of platforms including Windows, Mac OS, and Linux and supports a variety of processor instruction sets. The GHISDRA platform includes all the features expected in high-end commercial tools, with new and expanded functionality NSA uniquely developed. and will be released for free public use at RSA."

News

GitHub

Bash

Programming

Security

Android

Mobile

gaming

NSA

open source

http://bit.ly/2TDmcAk via @johanlouwers . follow me also on twitter

[hodldrgn-blog]

New Post has been published on https://cryptomoonity.com/meet-the-enigma-ambassadors-5-celeste-seberras/

Meet the Enigma Ambassadors #5: Celeste Seberras

Meet the Enigma Ambassadors #5: Celeste Seberras

As part of a new series, Enigma will be highlighting some of the awesome Ambassadors helping us build a more decentralized future with our privacy solutions. Read on to meet them — and to learn how you can join us!

The new Enigma Ambassadors program is comprised of talented individuals who represent our project and communicate our technology and vision to their communities and industries. Our goal has been to build a program where everyone feels valued, learns daily, builds skills, and has direct access to the Enigma team. Being involved at the early stages of an ambitious blockchain project like Enigma is an incredible opportunity — and becoming an Ambassador can mean gaining lifelong friends and colleagues.

With over 40 Ambassadors now across 16+ countries, we are slowly building what we believe is the best core community in the blockchain space — curious, committed, and kind. Our Ambassadors bring many different skills and backgrounds to their work, including development experience, artistic talents, business acumen, community-building expertise, and much more.

Today we highlight Celeste Seberras, one of the awesome people behind Enigma’s success as well as our documentation. Read her story below.

“To me, privacy is more than a concept, a talking point or an afterthought — it is a way of life.”

Who are you?

My name’s Celeste, and I’m an Information Security Engineer and Technical Writer. I’m known professionally for my entrepreneurial spirit, writing skills and tinfoil hat, known personally for my blunt honesty, off-color humor and love of chinchillas.

I’ve always been the type of person who’s forever dissatisfied, from my personal achievements to the status quo — though while sometimes overwhelming, this trait has brought me down many paths in life, from international racing, heavy metal fabrication, launching several tech start-ups to even working in Africa. A habitual creature of solitude with a logician mind, I constantly crave stimulation in the form of information. I can often be found at home alone, researching or writing away until the earliest hours of the morning.

My personal interests vary greatly, but my passion is forever in my work. I have been in the privacy and open-source world for roughly five years now, shortly after becoming introduced to mixnets by the Tor Project (whom, incidentally, I’d end up doing an internship with down the road). Since then I have been fascinated by the potential that anonymity has to offer everyday people in the fight for a voice and unfiltered knowledge, as well as the underlying technology that makes it all possible. After an incalculable amount of hours self-teaching, a couple certificates, endless cups of coffee and equally as many sleepless nights in IRC, I became able to support myself with my work in the privacy industry and haven’t looked back since.

Why Enigma?

To me, privacy is more than a concept, a talking point or an afterthought — it is a way of life. I wake up and go to sleep thinking about technological and social impacts that the software I work with everyday brings to humanity, and it’s what ultimately kindles my inner flame. I’m also a pureblood anarchist, and I believe that every individual has the right to say, share or capitalize to their desire, and that the rights of a person end where the next ones begin.

Bitcoin showed us that we can exist outside of the legacy banking and global financial structure, leaving behind the limitations and servitude involved in centralized power and bodies of authority. The bad actors that comprise our many forms of institutionalism only hamper our personal liberties in the pursuit of collective self-interest; and in the process, effectively slow our development. The only way to reclaim our individual freedom is further extending the impact of existing cash and equity solutions as well as exploring the countless ways that blockchain, decentralization and privacy-focused systems can radically improve many prospects of our (at times, bleak) future.

More personally speaking — being so deeply involved in the privacy / FOSS spaces and having invested in decentralized assets for a while, it was really only a matter of time before I stumbled on Enigma. When I finally did, it was an instantaneous fascination. I had yet to see a blockchain project that was taking the dynamics of privacy and open-source seriously, in the ways that the existing industries had defined — this factor is a widely unacknowledged yet incredibly crucial part of a meaningful collaborative effort. Enigma has exemplified their willingness to learn and grow repeatedly, often looking to others as well as the greater community for insight and fresh perspectives. It is a project that I am proud to associate myself with and contribute to.

What do you enjoy working on?

As is likely abundantly clear at this point in the piece, I love technology — specifically anonymity, cryptography and open-source. Outside of these categories I have an stack of personal projects and interests, such as mixnets, tiny tech / SBCs, vintage laptops, OS development, containers and writing old-school CLI games.

Away from the keyboard things tend to get a lot broader. I’m a very musical person who’s played several instruments in my life, my favorite being the bass guitar. Writing has always been a strength of mine, and I have composed several pieces in my life, some of which are published (mostly in poetry). I also enjoy working with my hands, and have a wide variety of shop skills such as automotive, Arc/MIG/TIG welding, machining and carpentry. One of my businesses is a production company, which got me into photography and videography at one point — a more recent interest of mine. The list goes on.

My downtime is usually much less eventful, and is often filled with bingewatching cartoons or documentaries (what a combo, I know), playing nostalgic video games or tending to my four little beloved furbabies.

My chinchillas!

In the scope of Enigma: I am fortunate enough to be the technical writer behind the protocol documentation, something I very much enjoy working on. In the ambassador program I can be found giving a privacy-focused insight to the many working groups and the crew, as well as sporadically spamming our #random chat (possibly my most valuable skill).

“I believe this year (and the upcoming ones) will be remembered as the dawn of the ‘privacy awakening.’”

What do you want to see in a decentralized, privacy-oriented digital future?

What I personally look the most forward to on the technology side is the continued development of solutions that preserve the individual’s ability to share information, secrets and ideas anonymously, a fundamental part of a free and open society. Up until now this has mostly come in the form of censorship-resistant mixnets (such as Tor) as well as other open-source cryptographic solutions — but blockchain and other new developments in the decentralized space have given us an opportunity to take the vision another step further, potentially incorporating the ideals of liberty into countless other aspects of our lives, from governance to entertainment.

Socially speaking, I think our privacy-oriented future is already being molded. Many organizations have been on the frontlines of the ‘technological battlefield’ since the inception of the internet itself, developing privacy-preserving software and militantly defending our digital rights in courtrooms across the globe. Sadly, due to a combination of external factors, their work and warnings have largely fallen on deaf ears for far too long; it’s unfortunate that things have become as perverse as they are, though I believe this year (and the upcoming ones) will be remembered as the dawn of the “privacy awakening.”

The constant barrage of high-profile data breaches and legal battles has brought a very bright light onto the parties who’ve been taking advantage of us for so long. The public discourse has become more focused on privacy than ever before, and outrage at the exploitation that has occurred is reaching fever pitch. Paired with the continued distrust of traditional systems both financial and otherwise, I’m cautiously optimistic that we are on track to a more independent and decentralized future for all, in many respects. There will likely be incredible hardships and growing pains along the way, but it will be worth it to live in a world designed for openness, freedom and reason.

Why should someone become an Enigma Ambassador?

Because you get to work with me, of course!

[crickets]

You get to work with me, too!

In seriousness though, it’s a fantastic opportunity — other than the obvious ability to network with the many uniquely talented ambassadors in the program and having your skills and passion become assets, there is the chance to have one-on-one collaboration with the core team and the ability to learn about the project in all faucets, past the technology. In the program, there is no one that does not get their voice heard — everyone has a place at the table and the ability to help shape the future of the project with their ideas and contributions.

Ambassadors are also given the tools and knowledge about Enigma and the other ever-changing aspects of the blockchain landscape needed to effectively understand and share the benefits (and at times, downsides) of solutions with the wider community. My experiences thus far have been nothing short of fantastic, and I urge anyone out there who’s as enthusiastic about blockchain or privacy to come join us in decentralizing the future.

Inspired by Celeste’s story? Want to become an Enigma Ambassador? Read this description of the program to learn how you can apply.

Learn more about our project on our website and blog.

Join our developer community: forum.enigma.co

Want to build on our protocol? Check out our documentation to get started — or, if you’re a project or enterprise, submit your interest here.

Join the Enigma Team: enigma.co/team

Telegram: t.me/EnigmaProject

Reddit: reddit.com/r/EnigmaProject

Twitter: twitter.com/enigmampc

Discord: https://discordapp.com/invite/SJK32GY

Meet the Enigma Ambassadors #5: Celeste Seberras was originally published in Enigma on Medium, where people are continuing the conversation by highlighting and responding to this story.

Source

Related

Gold-Based Cryptocurrency: What is it? Gold-Based Cryptocurrency: What is it? The rise of cryptocurrency was so sudden and widespread that before the world could realize what was happening...

Ask Ned: Your Questions About SMTs Title: Ask Ned: Your Questions About SMTs Video duration: 0:19 Views: 455 Likes: 16 Dislikes: 0 Publication date: 2017-10-02 18:59:11 https://www...

Cryptocurrency News: TRON Secret Project, Asura IC... Title: Cryptocurrency News: TRON Secret Project, Asura ICO, Odessy Airdrop, Poloniex Delisting, Red Pulse Video duration: 4:56 Views: 579 Likes: 2...

Get to know SwissBorg’s Referendum II Get to know SwissBorg’s Referendum II Get to know SwissBorg’s Referendum IIWEALTH MANAGEMENT OF THE FUTURE: SWISSBORG’s VISIONIn the history of m...

.yuzo_related_post .relatedthumb background: !important; -webkit-transition: background 0.2s linear; -moz-transition: background 0.2s linear; -o-transition: background 0.2s linear; transition: background 0.2s linear;;color:!important; .yuzo_related_post .relatedthumb:hoverbackground:#fcfcf4 !important;color:!important; .yuzo_related_post .yuzo_text color:!important; .yuzo_related_post .relatedthumb:hover .yuzo_text color:!important; .yuzo_related_post .relatedthumb acolor:!important; .yuzo_related_post .relatedthumb a:hovercolor:!important; .yuzo_related_post .relatedthumb:hover a color:!important; .yuzo_related_post .relatedthumb margin: 0px 0px 0px 0px; padding: 5px 5px 5px 5px;