The core argument they are making is one of resources, I can find myself seeing their point. Another abuse of the service would be to convert videos into ASCII text and check them into git, for example.
The issue with the crypto argument is that it is purely political, it is not affecting the service at all. You may think that you agree because it happens to align with your political sentiment, but it's entirely possible they come for your projects next.
I don't think you want to store your source code in a place where they ban projects based on politics [1]:
> Allowing these projects is not a neutral stance; the effects to the environment are severe. The "DarkFi" (seemingly some crypto designed for criminals, citing an FBI director) project for example uses a "PoW blockchain" (per their readme). PoW (Proof-Of-Work) projects waste an astonishing amount of computational energy, with Bitcoin alone using more energy than the entire countries of Argentina or the Netherlands. This energy is almost always from fossil fuels, which directly contributes to greenhouse gas emissions and undermining any global efforts to fight climate change.
> This is not a neutral space, Codeberg is political. If you disagree with someone, be constructive and don't call them merely political and think that's a reason for the discussion to stop.
Cryptocurrency is bad, but LLMs are fine? What next? Maybe you can't store your simulation source there because it is deemed to resource intensive for the expected results? When did source code itself become dangerous?
Just ordered myself the LilyGo T5 E-Paper S3 Pro [1]. The other good options on the hardware tab are sold out [2]. I quite like the idea of having GPS capability, and maybe I can experiment with LoRa gateways. I originally missed out on the M5 Paper and have been looking for an entry since.
My plan is to not use this firmware and use MicroPython instead (based on a high-level OS I already developed that is extremely low battery consumption). I carry around with me an A6 notebook with TODOs for each day - just the other day I temporarily lost it and realized that I actually need to have a backup for this stuff synced with a private VPS.
> I did not expect much, and because the bottlenecks were the HDD and CPU I did not feel any noticeable performance improvement. Still, it occurred to me that it might be fun to take the netbook completely apart and start replacing its hardware piece by piece.
I would look at swapping out the HDD for something solid state - lighter, less power, higher performance for random R/W.
Then it's just a case of lightening the load of the CPU as much as possible, strip out everything that is not needed.
I've run modern Firefox on much lighter devices. One of my netbooks is the same spec as this, and I do browsing + coding on it easily.
> Exposed terminals would need a lot more than a single transistor. It would need ESD protection and it would change the outer case from being a complete sealed over mold into something that had to seal against two exposed terminals. That’s a big change.
This is a solved problem though. Wireless earbuds can do it. We're probably just talking about a TVS diode.
> For a niche, low volume product with an unknown market demand I think making the simplest possible version of the product is a good idea to start, but at $99 it’s getting into the range where buyers don’t want to think of it as a disposable item.
> The bigger problem is that the 2 year battery life depends on the device being used for only short notes like “Add milk to the grocery list”. The people who expect to use this for taking notes or thinking out loud could exhaust the battery in a couple months.
$75 for a use once device that could last as little as a few months under normal usage, or $100 for something that could operate for 5+ years. Knowing whether there is a market is always difficult, but if you do crack a market you typically only get one chance to get people onboard.
> Roughly 12 to 15 hours of recording. On average, I use it 10-20 times per day to record 3-6 second thoughts. That's up to 2 years of usage.
2 years is optimistic I think. 3-6 second thoughts is not much, most ideas I'm having past TODOs are >15 seconds. Plus this would definitely depend also on how regularly you sync to the app.
Bare in mind, these devices have not yet been used in the wild on people outside of the product creator. Maybe one of the use cases is to note down monologues, or to easily record conversations with clients for later review.
1 month battery life is also highly usable, but there at least should be a way to charge it.
Not sure that would work. Charging is not 100% efficient, and if I remember correctly most batteries need to reach a minimum current to start actual charging. When you're talking micro or pico amps, it barely registers as a signal in most cases.
I think the "dock" itself could be USB C easily, it would probably also significantly reduce the cost of the dock.
> Adding the port, the USB-C PD circuitry may take up too much room.
You don't need PD circuitry for this. 5V 500mA over USB2 is more than enough. But the actual port and battery charging circuit is a bit ridiculous at this size.
I'm not sure precisely what the EU rules are, but the requirement should really depend on the dimensions/power of the device.
> We considered this but decided not to for several reasons:
> You'd probably lose the charger before the battery runs out!
> Adding charge circuitry and including a charger would make the product larger and more expensive.
> You send it back to us to recycle.
I don't think this is true. The charging circuit could have been in the charger itself. To provide access to the battery, one of the terminals could be behind a transistor enabled by the micro. The charger could then send a signal to the ring to unlock the battery terminal. Then all you needed to do was expose two/three pads externally.
I think this was somewhat predictable. The USB cable from the hub is too long, and it's not thick enough. USB3 can also kick off a decent amount of heat, it's not a good sign when the case is in plastic.
If you're looking for a good USB3 hub, look for one with a short thick USB cable, metal chassis. If it has HDMI it's a good since because you're unlikely to pump that via USB2.
I used to have a script running that whenever somebody failed to SSH into my laptop, it would blurt out "I hate this hacker crap" [1]. I had mostly forgotten about it until I was at a conference and it starts going off - followed by a guy nobody knew quickly leaving.
I've been messing with the magic value weights, and it doesn't take too much to push them in any given direction. The TEAMS_2026 should really be taken with a pinch of salt.
I've done a decent amount of traveling - honestly the most important thing has always just been to have stuff that works. Charging things has rarely been an issue. A few extra cables in the luggage is not a big deal.
Terrence's issue here is that he is over complicating things:
- Toothbrush - Just take a non-battery toothbrush, it's perfectly fine and will not break down or need charging.
- Tracker - I'm doubtful you will get it back in most countries. Always keep the essentials such as phone, wallet and passport on your physical person where possible.
- Bug Bite Zapper - Do as the locals do, they too don't want to be swamped with insects.
The only metric that really matters is 'profit per amount invested'. This is very difficult to quickly evaluate, and therefore we resolve to use simplified metrics such as cost per unit tokens.
The point at which the metrics become meaningless is when others become aware of them, and begin to optimise for them. Lines per code is is not a bad insight for development activity, only when the developers are not aware of the metric. Price per 1M tokens became meaningless when LLM providers started to optimise for it. It seems to be that Sonnet 5 is optimised to score well on AA intelligence whilst seemingly having a lower price per 1M tokens.
I think generally we are in an AI bubble, and it will at some point pop. The numbers simply don't make sense. I would gamble heavily on local cost per task to survive the LLM winter. Given that hardware is pretty much a fixed overhead, you probably want to optimise for task per kW - that's where I'm betting.
> I agree with the rest but Pi Zero W is a specific machine with 512 MB RAM:
I thought they came in different variants - my meat-based LLM must have hallucinated it.
> It's also the one everyone can buy online for $19, not Pi Zero 2 W (always out of stock)
I get the impression that they don't actively manufacture Pi Zero W anymore and it's all old stock. Rapid for example say they have an availability of 761 (at time of writing) [1], but are those all within Rapid's control, or what is reported at Raspberry Pi's remaining stock? If you sell 1k printer units, can you put a Pi Zero W in all of them?
Compute modules are probably a bit more reliable and there is some capability with other modules, specifically the DDR2 form factor ones [2] (which is my favorite form factor). For example, ClockWork sold their own compatible compute modules [3].
> With Openprinter, you are free to choose between standard sheets or a roll of versatile paper.
A few other comments have concentrated on the printer head and ink cartridge, but the roll vs sheets interests me. Manipulating sheets of paper is actually quite a difficult problem to solve - and there is only a demonstration of paper placement. Loading page after page is actually really not easy at all. There is no example of it printing.
I see they got a nomination for a design award [1], which in my personal experience has been a negative signal for successful projects. On the same page they mention that they also mention that they don't even know how much this will cost yet:
> We know this is your most frequently asked question! Final pricing depends on a moving puzzle of production volumes, BoM costs, industrialization expenses, regulatory certifications, and final engineering developments.
On the crowd funding page it mentions for parts [2]:
> Main board: Raspberry Pi Zero W
> Cartridge board: STM32 MCU
Not a specific MCU variant, and the specifics of the Pi variant (i.e. RAM) are not mentioned. I would expect these parts would be locked in by now. I have a feeling that this is not quite as ready as made out - I think there is still R&D going on.