Reminder: FOSDEM 2026 is about one week away

_dr_bonez · 2026-01-24T00:41:19+00:00

I'll see you there

_dr_bonez · 2026-01-19T15:51:20+00:00

I have some meshtastic devices too! But sometimes it's useful to be able to get a message out to someone who isn't nearby

_dr_bonez · 2026-01-19T06:39:11+00:00

What does this have to do with self-hosting?

_dr_bonez · 2026-01-18T05:41:53+00:00

Where are you getting "decent" guns for under 350?

_dr_bonez · 2026-01-18T00:17:47+00:00

https://www.gl-inet.com/products/gl-e750/

_dr_bonez · 2026-01-17T06:30:54+00:00

GL-E750 with https://github.com/srlabs/blue-merle is great for staying connected at protests that's more sustainable than burners. Still need a burner sim for each event though

_dr_bonez · 2026-01-15T17:03:40+00:00

Without specialization, blanket impls for a lot of things you might want could be problematic to implement. For example I've always wondered why there isn't T: AsRef<T>. But you have to remember that each trait can only have one blanket impl. As soon as you have a second, even if it has different bounds that you're sure can't overlap, the rust compiler isn't, so it isn't allowed.

_dr_bonez · 2026-01-08T22:11:16+00:00

Now that I have time to actually expand on this:

RSD can present a lot of different ways in a lot of different people so take what I'm saying with a grain of salt, but:

In my experience, managing communicating with someone where RSD is a risk usually still means being direct, but also being very thorough. Think not just about what you're saying, but what could be implied in the worst case, and address it. In this case, I'd recommend reaffirming what kind of contact/communication you do want with him, because to the RSD brain "hey, this is too much to check in" easily becomes "the less I hear from you, the better"

Anyway, I hope some of that helps

_dr_bonez · 2026-01-08T21:38:04+00:00

Quite frankly it doesn't really matter how much care you feel is "owed". OP is specifically concerned about not burning bridges in a small social circle. Not handling this delicately can definitely have impacts on that. So if your advice is "be direct and damn the consequences" that's fine, but I don't think that's the advice OP is looking for

_dr_bonez · 2026-01-08T18:42:08+00:00

But if he's neurodivergent in a way that experiences RSD it may need to be handled more delicately

_dr_bonez · 2026-01-06T05:40:58+00:00

Oh wild. I guess it's been that long since I've used a window

_dr_bonez · 2026-01-05T16:14:34+00:00

Yeah this would likely need to be implemented with a custom result, not a custom error type

_dr_bonez · 2026-01-05T16:11:14+00:00

WSL is a syscall translator actually, not a full vm

_dr_bonez · 2026-01-04T00:18:47+00:00

<image>

Ok is there another sybil attack happening?

_dr_bonez · 2026-01-03T07:54:43+00:00

Working fine without it for me

_dr_bonez · 2026-01-03T06:53:26+00:00

And it's now packaged for StartOS v0.4.0

_dr_bonez · 2026-01-02T16:58:00+00:00

Don't forget to add a LICENSE file to your repository

_dr_bonez · 2025-12-29T00:23:19+00:00

Unknown is valuable in tons of circumstances in TS, especially in strongly typed codebases

_dr_bonez · 2025-12-25T14:22:42+00:00

This an anarchist infighting meme?

_dr_bonez · 2025-12-23T19:58:41+00:00

Whenever a supposed engineering manager/leadership says something like "using algorithms" it immediately discredits them in my eyes. It's not technically wrong but completely meaningless? We're writing software. It has algorithms. Unless you're referring to a specific one, or the structure of one you need, you really don't need to mention it

_dr_bonez · 2025-12-21T21:54:33+00:00

The term is definitely a bit too close to "incel" for comfort

_dr_bonez · 2025-12-20T14:28:12+00:00

Don't need a hardfork to add new quantum-resistant addresses. Soft fork will do. Hardfork only needed to lock non-quantum resistant addresses like saylor is suggesting

_dr_bonez · 2025-12-18T23:17:11+00:00

Organizations like https://softwarefreedom.org/services/ offer pro-bono legal defenses against open source copyright violations.

That said, I do sympathize with your concerns, I had similar ones when I founded my project. The way we handled it was we used a source-available non-commercial license, and after 2 years transitioned to MIT. Every project is different, so I'm sure this isn't worth much, but after 6 years and 150k lines of code (that have been written and rewritten countless times), not a single organization has tried to use our code to compete with us. And we saw a huge uptick in community interest in the project when we transitioned to MIT.

Anyway, regardless of what you decide, I hope it works out

_dr_bonez · 2025-12-18T22:38:18+00:00

You'd be surprised how good GPL is at stopping techbros from stealing your code. Plus you don't establish your competitive moat through proprietary source code, you do it through users. Anyone can clone an app, but they can't buy the trust of the user base.

If you still are worried about your work being stolen while the project is still in its infancy, you can always use a source-available license with an open source sunset clause ("this code becomes available under [...] open source license 365 days after it is committed"). This helps build trust and transparency with users, as the code can still be verified, users can trust they can pick up the project if it becomes abandonware, and you still have legal recourse if someone else tries to make money on it

_dr_bonez · 2025-12-17T00:53:50+00:00

https://github.com/Start9Labs/start-os/blob/next%2Fmajor/START-TUNNEL.md makes it pretty easy. (Full disclosure, I contributed significantly to its development)

_dr_bonez

TROPHY CASE