❌

Vista Normal

Hay nuevos artículos disponibles. Pincha para refrescar la página.
Ayer — 5 Abril 2025IT And Programming

A Look Inside MacPaint

✇Hackaday
Por: Al Williams
5 Abril 2025 at 14:00

Usually when we talk about retrocomputing, we want to look at — and in — some old hardware. But [Z→Z] has a different approach: dissecting MacPaint, the Apple drawing program from the 1980s.

While the program looks antiquated by today’s standards, it was pretty hot stuff back in the day. Things we take for granted today were big deals at the time. For example, being able to erase a part of something you drew prompted applause at an early public demo.

We enjoyed the way the program was tested, too. A software “monkey” was made to type keys, move things, and click menus randomly. The teardown continues with a look inside the Pascal and assembly code with interesting algorithms like how the code would fill an area with color.

The program has been called “beautifully organized,” and [Z→Z] examines that assertion. Maybe the brilliance of it has been overstated, but it did work and it did influence many computer graphics programs over the years.

We love digging through old source code. Even old games. If you do your own teardowns, be sure to send us a tip.

Disney’s Bipedal, BDX-Series Droid Gets the DIY Treatment

✇Hackaday
Por: Donald Papp
5 Abril 2025 at 11:00

[Antoine Pirrone] and [Grégoire Passault] are making a DIY miniature re-imagining of Disney’s BDX droid design, and while it’s still early, there is definitely a lot of progress to see. Known as the Open Duck Mini v2 and coming in at a little over 40 cm tall, the project is expected to have a total cost of around 400 USD.

The inner workings of Open Duck Mini use a Raspberry Pi Zero 2W, hobby servos, and an absolute-orientation IMU.

Bipedal robots are uncommon, and back in the day they were downright rare. One reason is that the state of controlled falling that makes up a walking gait isn’t exactly a plug-and-play feature.

Walking robots are much more common now, but gait control for legged robots is still a big design hurdle. This goes double for bipeds. That brings us to one of the interesting things about the Open Duck Mini v2: computer simulation of the design is playing a big role in bringing the project into reality.

It’s a work in progress but the repository collects all the design details and resources you could want, including CAD files, code, current bill of materials, and links to a Discord community. Hardware-wise, the main work is being done with very accessible parts: Raspberry Pi Zero 2W, fairly ordinary hobby servos, and an BNO055-based absolute orientation IMU.

So, how far along is the project? Open Duck Mini v2 is already waddling nicely and can remain impressively stable when shoved! (A “testing purposes” shove, anyway. Not a “kid being kinda mean to your robot” shove.)

Check out the videos to see it in action, and if you end up making your own, we want to hear about it, so remember to send us a tip!

8 Pins For Linux

✇Hackaday
Por: Jenny List
5 Abril 2025 at 08:00

We’ve seen a Linux-based operating system made to run on some widely varying pieces of hardware over the years, but [Dimity Grinberg]’s latest project may be one of the most unusual. It’s a PCB with 3 integrated circuits on it which doesn’t seem too interesting at first, but what makes it special is that all three of those chips are in 8-pin SOIC packages. How on earth can Linux run on 8-pin devices? The answer lies as you might expect, in emulation.

Two of the chips are easy to spot, a USB-to-serial chip and an SPI RAM chip. The processor is an STM32G0 series device, which packs a pretty fast ARM Cortex M0+ core. This runs a MIPS emulator that we’ve seen on a previous project, which is ripe for overclocking. At a 148 MHz clock it’s equivalent to a MIPS running at about 1.4 MHz, which is just about usable. Given that the OS in question is a full-featured Debian, it’s not running some special take on Linux for speed, either.

We like some of the hardware hacks needed to get serial, memory, and SD card, onto so few pins. The SD and serial share the same pins, with a filter in place to remove the high-frequency SPI traffic from the low-frequency serial traffic. We’re not entirely sure what use this machine could be put to, but it remains an impressive piece of work.

Lockdown Remote Control Project is Free and Open

✇Hackaday
Por: Elliot Williams
5 Abril 2025 at 05:00

If you flew or drove anything remote controlled until the last few years, chances are very good that you’d be using some faceless corporation’s equipment and radio protocols. But recently, open-source options have taken over the market, at least among the enthusiast core who are into squeezing every last bit of performance out of their gear. So why not take it one step further and roll your own complete system?

Apparently, that’s what [Malcolm Messiter] was thinking when, during the COVID lockdowns, he started his own RC project that he’s calling LockDownRadioControl. The result covers the entire stack, from the protocol to the transmitter and receiver hardware, even to the software that runs it all. The 3D-printed remote sports a Teensy 4.1 and off-the-shelf radio modules on the inside, and premium FrSky hardware on the outside. He’s even got an extensive folder of sound effects that the controller can play to alert you. It’s very complete. Heck, the transmitter even has a game of Pong implemented so that you can keep yourself amused when it’s too rainy to go flying.

Of course, as we alluded to in the beginning, there is a healthy commercial infrastructure and community around other open-source RC projects, namely ExpressLRS and OpenTX, and you can buy gear that runs those software straight out of the box, but it never hurts to have alternatives. And nothing is easier to customize and start hacking on than something you built yourself, so maybe [Malcolm]’s full-stack RC solution is right for you? Either way, it’s certainly impressive for a lockdown project, and evidence of time well spent.

Thanks [Malcolm] for sending that one in!

The Transputer in your Browser

✇Hackaday
Por: Al Williams
5 Abril 2025 at 02:00

We remember when the transputer first appeared. Everyone “knew” that it was going to take over everything. Of course, it didn’t. But [Oscar Toledo G.] gives us a taste of what life could have been like with a JavaScript emulator for the transputer, you can try in your browser.

If you don’t recall, the transputer was a groundbreaking CPU architecture made for parallel processing. Instead of giant, powerful CPUs, the transputer had many simple CPUs and a way to chain them all together. Sounds great, but didn’t quite make it. However, you can see the transputer’s influence on CPUs even today.

Made to work with occam, the transputer was built from the ground up for concurrent programming. Context switching was cheap, along with simple message passing and hardware scheduling.

The ersatz computer has a lot of messages in Spanish, but you can probably muddle through if you don’t hablar español. We did get the ray tracing example to work, but it was fairly slow.

Want to know more about the CPU? We got you. Of course, these days, you can emulate a transputer with nearly anything and probably outperform the original. What we really want to see is a GPU emulation.

First PCB with the Smallest MCU?

✇Hackaday
Por: Elliot Williams
4 Abril 2025 at 23:00

[Morten] works very fast. He has already designed, fabbed, populated, and tested a breakout board for the new tiniest microcontroller on the market, and he’s even made a video about it, embedded below.

You might have heard about this new TI ARM Cortex MO micro on these very pages, where we asked you what you’d do with this grain-of-rice-sized chunk of thinking sand. (The number one answer was “sneeze and lose it in the carpet”.)

From the video, it looks like [Morten] would design a breakout board using Kicad 8, populate it, get it blinking, and then use its I2C lines to make a simple digital thermometer demo. In the video, he shows how he worked with the part, from making a custom footprint to spending quite a while nudging it into place before soldering it carefully down.

But he nailed it on the first try, and honestly it doesn’t look nearly as intimidating as we’d feared, mostly because of the two-row layout of the balls. It actually looks easy enough to fan out. Because you can’t inspect the soldering work underneath the chip, he broke out all of the lines to a header to make it quick to check for shorts between those tiny little balls. Smart.

We love to see people trying out the newest hotness. Let us know down in the comments what new parts you’re trying out.

Thanks [Clint] for the tip!

Vintage Computer Festival East This Weekend

✇Hackaday
Por: Elliot Williams
4 Abril 2025 at 20:00

If you’re on the US East Coast, you should head on over to Wall, NJ and check out the Vintage Computer Festival East. After all, [Brian Kernighan] is going to be there. Yes, that [Brian Kernighan].

Events are actually well underway, and you’ve already missed the first few TRS-80 Color Computer programming workshops, but rest assured that they’re going on all weekend. If you’re from the other side of the retrocomputing fence, namely the C64 side, you’ve also got a lot to look forward to, because the theme this year is “The Sounds of Retro” which means that your favorite chiptune chips will be getting a workout.

[Tom Nardi] went to VCF East last year, so if you’re on the fence, just have a look at his writeup and you’ll probably hop in your car, or like us, wish you could. If when you do end up going, let us know how it was in the comments!

Filestash v0.6 - Building a Better Dropbox, brick by brick

✇Self-Hosted Alternatives to Popular Services
Por: ／u／mickael-kerjean
5 Abril 2025 at 03:18

Hello everyone, Mickael from Filestash here.

Today marked the 18th birthday of the Dropbox initial launch on Hacker News, with the infamous top comment from the legendary "FTP guy". Fast forward to 2017, as I was frustrated with all the other Dropbox alternatives, I figured we should have a better path, instead of forcing parts you can't swap over to another, the better way integrates with an ecosystem of 3 different kind of interoperable packages: a storage, a web UI and a sync tool. There's literally more than 100 storage servers available, a couple great options for sync, but what we were really missing is the web UI that integrate everything together. That missing piece became my mission, and 8 years later, I'm very proud of the result even though there's still a very long way to go.

Milestone in v0.6

  • The frontend was entirely rewritten from React to vanilla JS with the idea to get every last bit of performance back so you have the best possible frontend. As of today, the new frontend which was published out of canary release last month is just better by every possible metric than the previous one.

  • A crazy amount of flexibility via plugins. You can change any aspect of the application both in the front and back by creating plugins. With this approach, you don't pay the cost of the features you don't need and don't have to maintain a complete fork just because you want to add or remove some features or customise some other aspects.

  • A new sidebar to navigate around your files - screenshot

  • A dark mode has been revamped to be much nicer - screenshot

  • Compatibility with other storage servers and vendors got greatly improved. You'd think SFTP is a standard that work everywhere? Well every vendor has interpreted the specs differently and they all come with their own quirks, same for S3, FTP, etc...

  • I've added support for a wide range of file type. The list is about to go up significantly this year since we can now make plugins targeting specific file types (eg: the latest one I've made is to handle swf file).

  • Documentation was entirely rewritten

  • The backend has become battled tested by millions of people including many attacks (I guess being used by Ukrainian military didn't help)

  • Thousands of small improvements + features requested by the community, like the video thumbnail plugin, new storages, new integrations with for example office document coming from microsoft, collabora / wopi, support for chunked upload via TUS, MCP server, authorization via signed URLs for QR code and many many more .... The whole list can be seen here

Fun

What's next?

The objective is to reach v1.0, not sure when this happen but when it does, Filestash will be 10x better than anything else. It's still missing many components, such as a mobile app, tag handling, improvements to make the setup simpler, a smaller size overall, make it easy to install it anywhere, better Chromecast support, enhanced video and image support, quota handling, automated workflows, and fixes for hundreds of issues. When we achieve the ultimate file manager, it will be time for v1.0.

In the coming months, I will be releasing a homecloud edition of Filestash which will be a Dropbox like experience outside the box with a set of premade parts that integrate well with each other and you can easily deploy on your server.

Also to achieve sustainability, the goal is to secure sponsorship from outside organisations. If you want access to some of the enterprise feature like SSO, drop me a private message.

What make Filestash different?

  • recognizing Dropbox is 3 parts that should be interoperable: storage, UI and sync. Since the very first day, the whole idea was about sitting on the shoulders of giants by integrating with the ecosystem. There's literally hundreds of storage server out there, from the simple openssh SFTP to proftpd, sftpgo, minio, nfs server, samba, ceph, open stack, Dell ECS, IBM GPFS... Reinventing that wheel is crazy, sitting on the shoulder of the whole ecosystem is a much saner approach.

  • separating storage / authentication and authorisation entirely so you can connect to say an SFTP server from a QR code or delegate authentication to an LDAP directory, a mysql database or anything some code could talk to. That kind of flexibility is unheard of in most selfhosted softwares, as you'd normally would have to fork the whole code base and maintain a fork over time when in Filestash you can just maintain your plugin.

  • going low level when necessary. The best example of this is thumbnail generation. There's a myth going on in this sub that generating thumbnails is slow, hence you have to generate them separatly and possibly cache them somewhere. While it's true genric tools like image magick are slow at generating thumbnails, they are only slow because they aren't 100% focus on that task. For a 768x1024 jpeg of my kid, Filestash generates a thumbnail in 15ms, the only tool we use is custom C code relying on many tricks exposed by libjpeg. If you take a GIF, Filestash can be 10x to 100x faster because of tricks used to parse things more efficiently than a generic tool like image magick. Why nobody does this? You would have to spend days reading C code made by other people and obsess over how to make it faster, but what I found out is if you constantly take the hard path, it potentially make things a lot faster and nicer.

  • obsessing over performance. Filestash is a proxy that open a pipe from your browser all the way to your storage and everything is being streamed on that pipe. The objective has been to ensure all the endpoints latency stay bellow 1ms. That kind of target would have been impossible to achieve with something like node, python, PHP, etc...

  • obsession over UX, nothing less than 60FPS. When you start browsing through a lot of data it would be normal to drop the refresh rate but not with Filestash. I've spent days obsessing of the dev tool performance tab to understand how you can create efficient virtualised list that don't waste CPU cycles. Same for making navigation instant on the folder you've already visited before, apply all the transcient state when you create a file/folder, move things around, delete things, etc... Despite the simple look, there's tons of non obvious things hapening to make things smooth no matter what you throw at it

  • no reliance on databases. Before I got started with Filestash, I wanted to contribute to Owncloud and Nextcloud to fix the speed issues I had with it but the core issue they had was too deep to be fixed, aka they were making dozens of call to a DB anytime you just list the content of a directory or upload something, and because of that db centric design you can't fix the sync issue that happpen if you touch the underlying filesystem.

  • a good architecture that allow crazy extensibility via plugins. Just to name an example, over the last week, I was able to provide support for MCP as a plugin so you can have an AI agent doing what you want in your storage. Because it's a plugin, it's totally optional and you can get rid of it entirely.

  • you shouldn't have to pay the cost for the features you don't need. That's the primary trap software fall onto, you start small and progressively add more and more features even if it does make things slower for everyone else, that's not good!

  • use the standard library as much as possible. I'll keep trimming on third party dependencies that aren't absolutly necessary. It get me sick everytime I use anything made in say node and see 10 critical security issue coming from dependencies of depencies from project build by high profile companies. If those guys can't get their shit together, it has to show something but nobody seem to care enough.

  • share links. There's 2 things I don't like with how everyone else does shared links:

    • why can't I mount the share link as a network drive? Take the link and mount it natively in your favorite operating system, wouldn't that be awesome? Of course, that's the way Filestash does it since the very beginning
    • why can't I share things externally with users who aren't part of the platform? Filestash allows for creating shared link for anyone working at "company.com" and will send a code via email if you set the user to "*@company.com"

  • From the very beginning I have been very mindfull of differentiating ground truth vs opinions so anyone with different opinions could override mine through plugins. It's a lot of small things like:

    • I have a "no slow shit policy". That's why there's no video thumbnail enabled by default, as of today I don't know how to generate thumbnail efficiently for video but if you're fine with "just use ffmpeg" there's a plugin for that
    • how should we handle html files? some people will want to edit them while some other will want to view them through say an iframe. Same for csv where some people will like the table view while some will prefer a simple editor. Filestash try to have sane default but if you don't agree with those default, you can always change those via a plugin.
    • how search should be done? the default is a recursive search but some people might prefer either no search at all or full text search. Filestash ship with a fts plugin that will crawl and index everything if you want but there's no conscencius on that as not everyone will expect a software to keep downloading things on the background to build that index (especially if you use S3 as a storage which could be costly) and we could easily build extra plugin to support things like RAG in the future
    • how should it start itself? a simple HTTP server is nice if you use a proxy to handle SSL termination but some other people might want to do SSL all the way either with their own certificates or self signed certificates or even generating those via letsencrypt directly. Filestash supports all those and more (eg: TOR and HTTP2)
    • there's many more examples but the gist is about being able to customise things the way you want because not everybody will like the decision I took and you have a way to change all those
submitted by /u/mickael-kerjean
[link] [comments]

Tagging the first release of Vigilant - An Open Source Web Monitoring Application

✇Self-Hosted Alternatives to Popular Services
Por: ／u／DutchBytes
5 Abril 2025 at 08:33

Hi all, I'm excited to share that I've tagged the first release of my side project, which I've been building for about a year. It's an open-source application that monitors all aspects of a website which can be self-hosted.

This first release marks a big personal milestone, as it's finally usable and stable enough to use. It probably still contains a few bugs and issues, and not all the features I'd like are implemented yet.

I'd love to get feedback on what you think and how the application can be improved. It's free to use on your own hardware via Docker.

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

Using .local or .lan for internal services using a proxy manager when i don't have a domain

✇Self-Hosted Alternatives to Popular Services
Por: ／u／OmletCat
4 Abril 2025 at 18:53

had a look elsewhere but couldnt find anything other than .local being a multicast DNS so i shouldnt use that for this kind of thing?

i want to use nginx to have a url point something like e.g x.x.x.x:8080 but am not sure what to call the internal domains, would something like pdfsterling.lan be fine?

lmk if i can be clearer

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

What is the open source version for self hosting vercel/netlify/heroku style?

✇Self-Hosted Alternatives to Popular Services
Por: ／u／sprmgtrb
5 Abril 2025 at 11:47

What is the go-to open source solution where if I have a VPS and I want to set up my my website to have CI/CD, where I push to my github repo and it deploys and I can see logs and stuff, basically like vercel/netlify/heroku and how you got a nice dashboard. Ive heard of dokploy, caprover, coolify....what is the best?

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

I made an app.. anybody would be interested to use it?

✇Self-Hosted Alternatives to Popular Services
Por: ／u／TheMzPerX
4 Abril 2025 at 17:00
I made an app.. anybody would be interested to use it?

Hi,

I am not a programmer, but a homelab freak.

I wanted to have a more or less single pane of glass view of my docker app update status. WUD came closest, but I did not like the visual representation. So i went to work with Claude 3.5 and made my own app connecting to WUD's API.

https://preview.redd.it/vnmur5okmuse1.png?width=1867&format=png&auto=webp&s=b7ec79b7803e8546df6f44b848dc5b6503cb9afd

It is hosted on my self hosted non public GitLab. Would you be interested to use it? I could perhaps add it to my Github.

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

Any ideas for windows backup?

✇Self-Hosted Alternatives to Popular Services
Por: ／u／linuxerSl
5 Abril 2025 at 14:35

I work at a company that does corporate backup (small businesses) focused only on Linux servers.

But now they want to implement a new service to target small businesses, to back up Windows computers only. In other words, it is random for machines to be located in different locations in the region.

What the company wants to do is rent a (storage box/hetzner) per company to store the backups there.

  1. The company only uses FOSS in its software. I don't even know where to start, can you suggest some software?
  2. Another question. Would it be ideal to backup what on C:/ ? I don't know if it's feasible to back up the client's entire system.
submitted by /u/linuxerSl
[link] [comments]

Help with README of a project

✇Self-Hosted Alternatives to Popular Services
Por: ／u／Useful_Math6249
5 Abril 2025 at 13:52

Dear community,

I'm the lead dev of the goinfinite/os open source project, a sort of "metamorphic" container that adapts to your needs after deployment. Writing a comprehensive README.md has been a challenge for us due to the project's "peculiar" nature.

Not long ago I came across a post on this subreddit (maybe it was r/opensource) about tips for open source projects, but unfortunately, I didn't save it and couldn't find it through search. The post covered essentials like including screenshots and a "get started" section on the README.

From what I vaguely recall, our latest README seems to cover some of the key points, but I'd love to get your feedback and make sure we're on the right track.

Thank you in advance for your help, and I wish you all a great weekend.

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

Cloudflare DNS CRUD App in Docker

✇Self-Hosted Alternatives to Popular Services
Por: ／u／Human_Umpire7073
5 Abril 2025 at 04:05
Cloudflare DNS CRUD App in Docker

🛠️ Flask Cloudflare DNS CRUD App

Tired of clicking through Cloudflare’s bloated web UI just to tweak a record? This self-hostable Flask app gives you a minimalist, fast interface to manage your DNS zones without the bloat.

<p align="center"> <img src="https://github.com/user-attachments/assets/06d07b4d-9497-45be-b8bd-35a6cf525ad1" alt="UI Screenshot" width="700"/> </p>

🏠 Who's this for?

Anyone self-hosting with domains on Cloudflare who wants: - A lightweight and responsive UI for managing DNS records. - An alternative to the memory-hungry Cloudflare dashboard. - A self-contained app deployable via Docker in seconds.

✨ Features

  • 🔐 Password-protected interface
  • ➕ Add DNS records
  • ✏️ Edit DNS records
  • ❌ Delete DNS records
  • 🔍 Search & filter by type and content
  • 🧾 Supports A, CNAME, TXT, MX, AAAA, SRV, NS

🚀 Quick Start (with Docker)

  1. Copy .env.template to .env and fill in your details: bash cp .env.template .env

  2. Generate a Cloudflare API token.

  3. Then spin it up: bash docker compose up -d

  4. Visit http://localhost:5001, log in with your password from .env, and you're in!

🔐 Security

  • App is secured with a password (set via .env)
  • Uses a read/edit-only Cloudflare token (no account-wide privileges)
  • Deploy behind your reverse proxy of choice (NGINX, Traefik, etc.) for HTTPS

🛠️ How to Generate a Cloudflare API Token

  1. Go to Cloudflare's API Tokens page
  2. Click Create Token
  3. Use the Custom Token template:
    • Zone:Read
    • DNS:Edit
  4. Set the token scope to either All Zones or a specific zone
  5. Copy and paste it into your .env file: CLOUDFLARE_API_TOKEN=your_token_here

🧪 Example .env

dotenv APP_PASSWORD=supersecret CLOUDFLARE_API_TOKEN=your_cloudflare_token DOMAIN=yourdomain.com FLASK_DEBUG=true HOST_PORT=5001

📦 Tech Stack

  • Python + Flask
  • Cloudflare API v4
  • Docker / Docker Compose

🧼 Clean & Lightweight

  • No database required
  • Just one screenshot, because it really is that simple
  • Customize via volume-mounted templates and CSS
submitted by /u/Human_Umpire7073
[link] [comments]

Automated Backup Solution for Docker Volumes

✇Self-Hosted Alternatives to Popular Services
Por: ／u／Ok-Mushroom-8245
4 Abril 2025 at 17:10
Automated Backup Solution for Docker Volumes

I've been developing a solution that automates the backup process specifically for Docker volumes. It runs as a background service, monitoring the Docker environment and using rsync for efficient file transfers to a backend server. I'm looking for feedback on whether this tool would be valuable as an open-source project or if there might be interest in hosting it online for easier access. Any thoughts on its usefulness and potential improvements would be greatly appreciated!

submitted by /u/Ok-Mushroom-8245
[link] [comments]
❌
❌