❌

Vista Normal

Hay nuevos artículos disponibles. Pincha para refrescar la página.
Hoy — 21 Febrero 2025IT And Programming

A New 8-bit CPU for C

✇Hackaday
Por: Al Williams
21 Febrero 2025 at 12:00

It is easy to port C compilers to architectures that look like old minicomputers or bigger CPUs. However, as the authors of the Small Device C Compiler (SDCC) found, pushing C into a typical 8-bit CPU is challenging. Lessons learned from SDCC inspired a new 8-bit architecture, F8. This isn’t just a theoretical architecture. You can find an example Verilog implementation in the SDDC project and on GitHub. The name choice may turn out to be unfortunate as there was an F8 CPU from Fairchild back in the 1970s that apparently few people remember.

In the video from FOSDEM 2025, [Phillip Krause] provides a nice overview of the how and why of F8. While it might seem odd to create a new 8-bit CPU when you can get bigger CPUs for pennies, you have to consider that 8-bit machines are more than enough for many jobs, and if you can squeeze one into an FPGA, it might be a good choice as opposed to having to get a bigger FPGA to hold your design and a 32-bit CPU.

Many 8-bit computers struggle with efficient C code mainly because the data size is smaller than the width of a pointer. Doing things like adding two numbers takes more code, even in common situations. For example, suppose you have a pointer to an array, and each element of the array is four bytes wide. To find the address of the n’th element, you need to compute: element_n = base_address + (n *4). On, say, an 8086 with 16-bit pointers and many 16-bit instructions and addressing modes can do the calculation very succinctly.

Other problems you frequently run into with compiling code for small CPUs include segmented address spaces, dedicated registers for memory indexing, and difficulties putting wider items on a stack (or, for some very small CPUs, even having a stack, at all).

The wish list was to include stack-relative addressing, hardware 8-bit multiplication, and BCD support to help support an efficient printf implementation.

Keep in mind, it isn’t that you can’t compile C for strange 8-bit architectures. SDDC is proof that you can. The question is how efficient is the generated code. F8 provides features that facilitate efficient binaries for C programs.

We’ve seen other modern 8-bit CPUs use SDCC. Writing C code for the notorious PIC (with it’s banked memory, lack of stack, and other hardships) was truly a surreal experience.

Acoustic Engine Harnesses the Power of Sound

✇Hackaday
Por: Dan Maloney
21 Febrero 2025 at 09:00

If you think sonic booms from supersonic aircraft are a nuisance, wait until the sky is full of planes propelled by up-scaled versions of this interesting but deafening audio resonance engine.

Granted, there’s a lot of work to do before this “Sonic Ramjet” can fly even something as small as an RC plane. Creator [invalid_credentials] came up with the idea for a sound-powered engine after listening to the subwoofers on a car’s audio system shaking the paint off the body. The current design uses a pair of speaker drivers firing into 3D printed chambers, which are designed based on Fibonacci ratios to optimize resonance. When the speakers are driven with a low-frequency sine wave, the chambers focus the acoustic energy into powerful jets, producing enough thrust to propel a small wheeled test rig across a table.

It’s fair to ask the obvious question: is the engine producing thrust, or is the test model moving thanks to the vibrations caused by the sound? [invalid_credentials] appears to have thought of that, with a video showing a test driver generating a powerful jet of air. Downloads to STL files for both the large and small versions of the resonating chamber are provided, if you want to give it a try yourself. Just be careful not to annoy the neighbors too much.

Thanks to [cabbage] for the tip via [r/3Dprinting].

3D Print Yourself A Split Flap Display

✇Hackaday
Por: Lewin Day
21 Febrero 2025 at 06:00

Split flap displays! They’re mechanical, clickety-clackity, and largely commercially irrelevant in our screen-obsessed age. That doesn’t mean you can’t have a ball making one of your own, though! [Morgan Manly] did just that, with tidy results.

An ESP32 C3 SuperMini serves as the boss of the operation, running the whole display. The display is designed to be modular, so you can daisy chain multiple characters together to spell longer words. Each module has 37 characters, so it can display the alphabet, numerals 0 to 9, and a blank. Each module contains a 28BYJ-48 stepper motor for controlling the flaps, and a ULN2003 driver board to run it and a PCF8575 IO expander to handle communciation. An A3144 hall effect sensor is also used for positional feedback to ensure the display always shows the right character. The flap mechanism itself is relatively straightforward—a drum with all 37 flaps is until the correct character is reached, with the blank flaps hosting a magnet to trigger the aforementioned hall effect sensor. The flaps themselves are 3D-printed, with filament changes used to color the characters against the background.

If you’ve ever dreamed of building a flap-display clock or ticker, you needn’t dream of finding the perfect vintage example. You can just build your own! The added bonus is that you can make it as big or as small as you like. We’ve seen some interesting variations on the split flap concept recently, too. If you’re cooking up your own kooky electromechanical displays, don’t hesitate to let us know!

Microsoft (Again) Claims Topological Quantum Computing With Majorana Zero Mode Anyons

✇Hackaday
Por: Maya Posch
21 Febrero 2025 at 03:00

As the fundamental flaw of today’s quantum computers, improving qubit stability remains the focus of much research in this field. One such stability attempt involves so-called topological quantum computing with the use of anyons, which are two-dimensional quasiparticles. Such an approach has been claimed by Microsoft in a recent paper in Nature. This comes a few years after an earlier claim by Microsoft for much the same feat, which was found to be based on faulty science and hence retracted.

The claimed creation of anyons here involves Majorana fermions, which differ from the much more typical Dirac fermions. These Majorana fermions are bound with other such fermions as a Majorana zero mode (MZM), forming anyons that are intertwined (braided) to form what are in effect logic gates. In the Nature paper the Microsoft researchers demonstrate a superconducting indium-arsenide (InAs) nanowire-based device featuring a read-out circuit  (quantum dot interferometer) with the capacitance of one of the quantum dots said to vary in a way that suggests that the nanowire device-under-test demonstrates the presence of MZMs at either end of the wire.

Microsoft has a dedicated website to their quantum computing efforts, though it remains essential to stress that this is not a confirmation until their research is replicated by independent researchers. If confirmed, MZMs could provide a way to create more reliable quantum computing circuitry that does not have to lean so heavily on error correction to get any usable output. Other, competing efforts here include such things as hybrid mechanical qubits and antimony-based qubits that should be more stable owing to their eight spin configurations.

Open-Source Random Numbers

✇Hackaday
Por: Bryan Cockfield
21 Febrero 2025 at 00:00

Whether it’s a game of D&D or encrypting top-secret information, a wide array of methods are available for generating the needed random numbers with high enough entropy for their use case. For a tabletop game this might be a single die but for more sensitive applications a more robust method of generating random numbers is needed. Programmers might reach for a rand() function of some sort, but these pseudorandom numbers don’t cut the mustard for encryption. For that you’ll need a true random number generator (RNG), and this open-source hardware RNG uses one of the better methods we’ve seen.

The device, called RAVA, is based on a property found in many electronic devices called avalanche breakdown. Avalanche breakdown occurs when a high voltage (in this case approximately 25V) is applied in the reverse bias direction, with this device using a pair of Zener diodes. When this high voltage is applied, an “avalanche” of electrons occurs which allows the diodes conduct in the opposite direction that they would when they are forward biased. This isn’t a constant current flow, though; there are slight variations over time which can be amplified and used as the random number generator. The noise is amplified over a series of op amps and then fed to an ATmega32U4 microcontroller which can provide the user with 136.0 Kbit/s of random data.

Unlike other random number generators, this device is based on a method generally accepted to be truly random. Not only that, but since it’s based on discrete hardware it can be accessed directly for monitoring and replacement in case of faults, unlike other methods which are more “black boxes” and are more opaque in their processes which are thus harder to audit. We also appreciate it’s open-source nature as well, and for some more information on it be sure to check out the paper on it in IEEE. If you’re looking for something to generate random numbers but will also bring some extra flair to the next game night, take a look at this radioactive dice replacement.

DIY Yagi Antenna Sends LoRa Signals Farther

✇Hackaday
Por: Lewin Day
20 Febrero 2025 at 21:00

LoRa gear can be great for doing radio communications in a light-weight and low-power way. However, it can also work over great distances if you have the right hardware—and the right antennas in particular. [taste_the_code] has been experimenting in this regard, and whipped up a simple yagi antenna that can work at distances of up to 40 kilometers.

The basic mathematics behind the yagi antenna are well understood. To that end, [taste_the_code] used a simple online calculator to determine the correct dimensions to build a yagi out of 2 mm diameter wire that was tuned for the relevant frequency of 868 MHz. The build uses a 3D-printed boom a handle and holes for inserting each individual wire element in the right spot—with little measuring required once the wires are cut, since the print is dimensionally accurate. It was then just a matter of wiring it up to the right connector to suit the gear.

The antenna was tested with a Reyas RYLR998 module acting as a base station, with the DIY yagi hooked up to a RYLR993 module in the field. In testing, [taste_the_code] was able to communicate reliably from 40 kilometers away.

We’ve featured some other unique LoRa antenna builds before, too. Video after the break.

UNIX Archaeology Turns Up 1972 “V2 Beta”

✇Hackaday
Por: Jenny List
20 Febrero 2025 at 19:30

In 1997 a set of DEC tapes were provided by Dennis Ritchie, as historical artifacts for those interested in the gestation of the UNIX operating system. The resulting archive files have recently been analysed by [Yfeng Gao], who has succeeded in recovering a working UNIX version from 1972. What makes it particularly interesting is that this is not a released version, instead it’s a work in progress sitting somewhere between versions 1 and 2. He’s therefore taken the liberty of naming it “V2 Beta”.

If you happen to have a PDP-11/20 you should be able to run this operating system for yourself, and for those of us without he’s provided information on which emulator will work. The interesting information for us comes in the README accompanying the tapes themselves, and in those accompanying the analysis. Aside from file fragments left over from previous users of the same tape, we learn about the state of UNIX time in 1972. This dates from the period when increments were in sixtieths of a second due to the ease of using the mains power frequency in a PDP, so with a 32-bit counter they were facing imminent roll-over. The 1970-01-01 epoch and one second increments would be adopted later in the year, but meanwhile this is an unusual curio.

If you manage to run this OS, and especially if you find anything further in the files, we’d love to hear. Meanwhile, this is not the oldest UNIX out there.

PDP-11/20 image: Don DeBold, CC BY 2.0.

Devs please put screenshots of your project on your GitHub pages!

✇Self-Hosted Alternatives to Popular Services
Por: ／u／Darkchamber292
21 Febrero 2025 at 13:18

This is my #1 pet peeve. I always tell devs, if you don't have screenshots you can say goodbye to a significant percentage to your potential user base.

I'm not going to install something if I don't even know what the UI looks like. Especially if I can't have it up in less than 2 minutes or it requires a DB of some kind.

Nothing pisses me off more than installing something, finding out I hate the UI and then have to uninstall it and drop any related DBs, when I could have saved all my time with a single screenshot on your GitHub.

submitted by /u/Darkchamber292
[link] [comments]

This Week in Self-Hosted (21 February 2025)

✇Self-Hosted Alternatives to Popular Services
Por: ／u／shol-ly
21 Febrero 2025 at 13:00

Happy Friday, r/selfhosted! Linked below is the latest edition of This Week in Self-Hosted, a weekly newsletter recap of the latest activity in self-hosted software and content.

This week's features include:

  • A redesigned listing for software updates, launches, and changes (!)
  • Arduino's 2024 open-source report
  • Software updates and launches
  • A spotlight on Eigenfocus - a self-hosted project management and task-tracking app (u/vinioyama)
  • A ton of great guides and content from the community

Thanks, and as usual, feel free to reach out with feedback!

This Week in Self-Hosted (21 February 2025)

submitted by /u/shol-ly
[link] [comments]

Is Authentik that resource heavy?

✇Self-Hosted Alternatives to Popular Services
Por: ／u／applescrispy
21 Febrero 2025 at 10:01

I just went to install Authentik using the Proxmox Helper scripts and noticed it states 'Authentik is very resource-heavy, it is recommended to use at least 8GB RAM anytime!'

Is this the case? Authentik's documentation states minimum is 2 CPU's and 2GB RAM for a docker install.

I only have a fairly low spec Proxmox environment I wanted to spin this up on.

submitted by /u/applescrispy
[link] [comments]

(Updates) I built a free, open source, locally hosted search engine for all your memes

✇Self-Hosted Alternatives to Popular Services
Por: ／u／neonwatty
21 Febrero 2025 at 12:35

The open source engine indexes your memes by their visual content and text, making them easily searchable. Drag and drop recovered memes into any messager. (original post )

Thanks to community feedback, we're excited to release a major update, featuring quality-of-life improvements, new image-to-text models, UX enhancements, and local build/test upgrades!

Some of these updates include:

  • 4 new image to text new models ranging in size from 200M to 2B parameters enabling much faster local processing on most machines
  • 10x reduction in Docker image size for app services
  • Easier custom setup of the for local NAS, Portainer, Unraid, etc., use with newly enabled customize hosts names and ports
  • new model selection panel added in Settings allowing for choice of image-to-text model at will
  • new grid view added to both home and search pages for a broader view of your memes

See the repo CHANGELOG.md for further details on updates and bugfixes!

submitted by /u/neonwatty
[link] [comments]

🆕 Cosmos 0.18 - All in one secure Reverse-proxy, container manager with app store, integrated VPN, authentication provider, Storage, and Monitoring, now with Automated Backups, CA, OpenID Gate and more!

✇Self-Hosted Alternatives to Popular Services
Por: ／u／azukaar
20 Febrero 2025 at 17:58
🆕 Cosmos 0.18 - All in one secure Reverse-proxy, container manager with app store, integrated VPN, authentication provider, Storage, and Monitoring, now with Automated Backups, CA, OpenID Gate and more!

link: https://github.com/azukaar/Cosmos-Server/

0.18 is out! And it is juicy!

https://preview.redd.it/b47y2yu3ebke1.png?width=1280&format=png&auto=webp&s=b2f151e4d2145f789691cbb6623cd8415af456ff

2 years ago, I started a journey to try and make self-hosting an accessible and safe alternative to SaaS product. Make servers reliable, well setup, and secured, for people to be able to manage their personal corner of the web, without sacrificing all their weekend and without sacrificing utility. Updates after updates, Cosmos has slowly built-up toward that goal, slowly adding important, large features such WAF, then VPN, then monitoring, etc... And finally, 2 years later, the final pillar of the Cosmos ecosystem has been built: backups! With this in, Cosmos is finally what I would consider to be an extensive but flexible 360 solution to self-hosting your digital life at home.

Additionally to this, other changes have been made to improve quality of life, with (among other things) a focus toward support for standalone, non-FQDN setups (basically improving support for .local and self-sign HTTPS certificate, with the new integrated CA)

As reminder, this is along-side the existing features:

  • App Store 📦📱 To easily install and manage your applications, with simple installers, automatic updates and security checks. This works alongside manual installation methods, such as importing docker-compose files, or the docker CLI
  • Storage Manager 📂🔐 To easily manage your disks, including Parity Disks and MergerFS
  • Network Storages 📡📂 Based on RClone, To easily manage your network storages, including accessing remote ones (ex. Dropbox) or share NFS / FTP / ... from the UI, protected by the smart shield
  • Reverse-Proxy 🔄🔗 Targeting containers, other servers, or serving static folders / SPA with automatic HTTPS, and a nice UI
  • Authentication Server 🔐👤 With strong security, multi-factor authentication and multiple strategies (OpenId, forward headers, HTML)
  • Customizable Homepage 🏠🖼 To access all your applications from a single place, with a beautiful and customizable UI
  • Container manager 🐋🔧 To easily manage your containers and their settings, keep them up to date as well as audit their security. Includes docker-compose support!
  • VPN 🌐🔒 To securely access your applications from anywhere, without having to open ports on your router.
  • Monitoring 📈📊 Fully persisting and real-time monitoring with customizable alerts and notifications, so you can be notified of any issue.
  • Identity Provider 👦👩 To easily manage your users, invite your friends and family to your applications without awkardly sharing credentials. Let them request a password change with an email rather than having you unlock their account manually!
  • SmartShield technology 🧠🛡 Automatically secure your applications without manual adjustments (see below for more details). Includes anti-bot and anti-DDOS strategies. Now includes TCP protection (FTP, SSH, Games, ...)
  • CRON 🕒🔧 To easily schedule tasks on the server or inside containers

https://preview.redd.it/i69tc9n4ebke1.png?width=1792&format=png&auto=webp&s=a9548d2c2c0344c8c717727b2d0d9cb476026a9d

New SSO Web Auth Gate

The Cosmos web auth gate is the feature that allows you to put a login screen on top of applications that do not have them included, or maybe have some less secure version (ex. just a http basic auth form). Thanks to this feature, you can put a proper secure login form in front of any page, with support for 2FA and so on. This was one of the first feature implemented in Cosmos, and it has been overhauled! The main change has been to change it from using a login form to using OpenID internally. The result is that it helps working around the browser limitation of cookies and domains.

Previously, if you had a Cosmos setup with multiple domains/sub-domains (ex cosmos.domain.com and app.domain.com) You would need to log into both those URLs separately (with the same account, but still) because the browser cannot share the cookies. it is now not required anymore, which is going to help a lot for people using .local domains. Also the login time has been extended to one week instead of 48h to ensure you dont need to login all the time.

https://preview.redd.it/0ivb6c7vebke1.png?width=1792&format=png&auto=webp&s=b9dee510acbccac629f88ca4826a96730dcc4694

SUDO Admin Mode

I was always worried about extending the session time (previously 48h) to a longer duration because your account can control everything on Cosmos... On the other hand, having to login all the time is frustrating! Starting 0.18, I was able to extend the duration of the session to one week (please note that means you are logged off after one week of inactivity, not after one week from login).

In order to keep your server safe, your session will now be a non-admin, sudo-able session, just like you would have in a Linux environment. You can use any of your apps normally, but if you want to do some admin stuff in the Cosmos dashboard, there is a new "Admin" button on the top right that allows you to sudo yourself temporarily into an admin to do maintenance work.

https://preview.redd.it/m5kdtbanfbke1.png?width=1920&format=png&auto=webp&s=b934591c1a282ae0208ff514a28d9e8e153769c0

https://preview.redd.it/sdujjczofbke1.png?width=1792&format=png&auto=webp&s=82110986d069d4bdfcfa0c0ae99d6d8c88a4a221

HTTPS Certificate Authority

Self-signed HTTPS certificates have a lot of shortcomings. You need to manually trust them in your browser, and some apps (especially in IOS, like Emby) straight out do not accept them. In 0.18, Cosmos now integrate and manages its own CA. This means, instead of manually trusting certs, you can trust the CA once on your device, and Cosmos will always use it to renew certs.

This will solve most issues self-signed certs will have! Again, a huge leap forward to allow using .local domains instead of FQDN. Any of your user can go to the "trust" tab and trust the CA themselves on their device:

https://preview.redd.it/2cpp3vo7gbke1.png?width=1920&format=png&auto=webp&s=d06476284ed5a466aea5af54bae478ae129bc467

https://preview.redd.it/y4tkws79gbke1.png?width=1792&format=png&auto=webp&s=d164479c37a08700d502b91c30835b912c734363

Backups

The star of the show: Backups! Backups are a critical part of any system. In the event of a catastrophic failure, backups are the main way to recover your data. It is important to have a backup strategy in place to ensure that your data is safe and secure.

Cosmos includes an entire backup system that allows you to easily create and manage backups of your data. This system is designed to be flexible and easy to use, allowing you to create backups on a schedule or manually. The backups are also encrypted for your security.

It uses Restic under the hood, allowing you more control, even if you were to stop using Cosmos. Please note that this is part of the premium version of Cosmos!

https://preview.redd.it/byha4s9ugbke1.png?width=1920&format=png&auto=webp&s=c761598e9f4247ce77d31f4cc8c4f55dd1a3a0cc

Navigate the snapshots and restore data (fully or partially) in the original folder or elsewhere

https://preview.redd.it/h7d3s2vugbke1.png?width=1920&format=png&auto=webp&s=c2d39dde1ba496606a120a945a42aa8dc3016dd0

The Integration between Rclone and Restic allows you to seamlessly backup any folder into any remote storage supported by RClone (which you can also manage from the Cosmos UI!).

https://preview.redd.it/cxw7z6vzgbke1.png?width=1137&format=png&auto=webp&s=ffc5fe3ad6b84454685f7a1e3c9f3b48bab235a3

Conclusion

This update is yet again a huge leap forward in term of quality of life, and the backup feature wraps up two years of intensive work on feature implementation for Cosmos. Moving forward, the focus will be shifted slightly toward improving existing feature, improving stability, and implementing smaller feature, like the lazy container feature. The only big feature I can think of I'd like to implement sometime in the future are custom dashboard. Something else that I want to focus on eventually, is integration with apps. Finally, a lot of work is left to do in Constellation to improve the VPN feature.

But until then, I am going to take a breather, appreciate and be grateful what we've all been able to achieve together. Cosmos is a HUGE ambitious project, and I still cannot believe how far it has come. As I always say, thanks for all of you, your trust and your support!

Changelog

 - UI to backup and restore containers/folders/volumes using Restic - Implements sudo mode - your normal token last longer, but you need to "sudo" to do admin tasks - Re-Implements the SSO using openID internally - fixes issue where you need to re-loging when app are on different domains (because of browser cookies limitations) - Implements local HTTPS Certificate Authority, to locally trust self-signed certificates on devices - Added new folder button to file picker - Cosmos now waits for CRON jobs to be over before restarting the server - Fixed bug with RClone storage duplication in the UI - Implements hybrid HTTPS with public and self-signed certificates switched on the fly - OpenID now returns more info in case of errors when Cosmos is in debug mode - Localizations improvements (Thanks @madejackson) - Improved local IP detection (Thanks @r41d) - Updated LEGO to 4.21.0 - Largely improved the experience of non-admin users (extra errors should all be gone) - Fixed file picker prefix issue in docker container - Added OpenID IDTokenSigningAlgValuesSupported - Added protocol in openid discovery endpoint - Fix RClone not starting (hopefully) - Added traditional Chinese translation - Avahi now ignores virtual interfaces - Fixed bug preventing the local mDNS broadcaster from publishing over 17 entries - Fixed bug with restarting slave Constellation node's Nebula process - UI to backup and restore containers/folders/volumes using Restic - Implements sudo mode - your normal token last longer, but you need to "sudo" to do admin tasks - Re-Implements the SSO using openID internally - fixes issue where you need to re-loging when app are on different domains (because of browser cookies limitations) - Implements local HTTPS Certificate Authority, to locally trust self-signed certificates on devices - Added new folder button to file picker - Cosmos now waits for CRON jobs to be over before restarting the server - Fixed bug with RClone storage duplication in the UI - Implements hybrid HTTPS with public and self-signed certificates switched on the fly - OpenID now returns more info in case of errors when Cosmos is in debug mode
submitted by /u/azukaar
[link] [comments]

Someone tell me this is a dumb idea

✇Self-Hosted Alternatives to Popular Services
Por: ／u／tartarsauceboi
20 Febrero 2025 at 22:50

My friend wants to:

Setup 10 individual VMs on proxmox. They would all be Ubuntu 22.04.

Then he wants to install docker on each one.

Then install one individual docker container per app per VM.

So for example VM1 is Nextcloud, VM2 is Bookstack, VM3 is Authentik, so on and so forth

He wants to do this segment it even more so that if a container were to get compromised and all of the services were on one VM and if they somehow got into the vm and destroyed it, atleast that would only affect one service instead of all of them. (This is why we have backups. I explained this)

But he's pressed on this.

So I guess my question here is.....is this a waste of time/resources? Would it actually pose any benefit in the name of security?

I thought it was silly but like....he sort of has a point? A stretch of one....

submitted by /u/tartarsauceboi
[link] [comments]

Introducing SPHERE: A Fully Decentralized, Encrypted Identity and Contact Framework (No Central Servers, Full User Control)

✇Self-Hosted Alternatives to Popular Services
Por: ／u／Eravex
20 Febrero 2025 at 20:20
Introducing SPHERE: A Fully Decentralized, Encrypted Identity and Contact Framework (No Central Servers, Full User Control)

Hey everyone,

I’ve been working a project that I believe could help shift control of personal data back into the hands of users—introducing SPHERE: Secure Peer-to-Peer Hosted Encryption Record Exchange.

SPHERE is a fully decentralized, encrypted contact and identity framework that eliminates the need for central servers. It’s designed from the ground up with privacy, security, and scalability in mind, making it a foundation for apps that prioritize user control over data.

What Does SPHERE Do?

  • Decentralized Identity Management: Each user controls their own data and contact list, shared only with approved peers.
  • End-to-End Encryption by Default: Communication is fully encrypted with AES-256, RSA-2048, and ECDSA signatures to ensure secure and private interactions.
  • Distributed Hash Table (DHT): Built-in decentralized storage for efficient peer discovery and secure contact management.
  • Sybil-Resistant Proof-of-Work Token System: Protects the network from spam and bot attacks without the need for financial incentives or mining.
  • Cross-Platform Support (Coming Soon): Currently optimized for .NET 8 with plans to extend support for Java and mobile platforms (Android/iOS).

How Can You Use SPHERE?

  • Self-hosted contact manager → Own your contact list, share only with trusted contacts.
  • End-to-end encrypted messaging → Build decentralized messaging systems without relying on centralized servers.
  • Secure identity verification → Use cryptographic proofs instead of third-party logins (no more "Sign in with Google").
  • Privacy-focused app backbone → Developers can build apps on SPHERE’s decentralized, zero-trust architecture.

Documentation & Resources

Why SPHERE?

Centralized platforms (even some decentralized projects) still rely on federated servers or third-party infrastructure. SPHERE aims to:

  • Eliminate central points of failure
  • Allow users to fully control their personal data
  • Create a privacy-first framework for future decentralized applications

Looking for Feedback & Contributors

I’ve been developing SPHERE for about a month, and I’m now looking for feedback from this community:

  • If you’re a developer interested in decentralized networks, encryption, or peer-to-peer systems, I’d love your thoughts.
  • If you want to contribute, feel free to dive into the GitHub or suggest improvements.
  • If you’re a privacy advocate or security researcher, I’m open to suggestions for improving SPHERE’s security model.

Quick Links

TL;DR:

SPHERE is an open-source, fully decentralized framework designed for privacy-first communication, contact management, and identity verification. It’s built to ensure that users own their data, not corporations or third parties.

I’m excited to hear your thoughts and collaborate with anyone interested in pushing decentralized technology forward!

Ask me anything!

submitted by /u/Eravex
[link] [comments]
❌
❌