Skip to main content


if imma build a fedi server and a fedi client it's not gonna be some ongoing project for the commons but an ongoing project for me.

I'll share the code for it, but the ongoing maintenance of it on my end will be to make it keep getting closer to what I want for my website.

because that's what it is, the engine behind my website, ultimately.

in reply to DJ Sundog - from the toot-lab

if I can build it in such a way that I see how to reuse it for other websites I need or want to build, that's gravy and I'll head that direction because I'm lazy and like reusing shit.

if I can build it with lots of inline documentation so I don't confuse future me it might be pretty easy to screw with for future whoever.

in reply to DJ Sundog - from the toot-lab

if I then use it to blog about how I use it, I can probably distill a user's guide out of that. no reason not to share that too, it'd already be on my blog as I wrote it.

if people hit me up and tell me about bugs they found in my stuff, I could look at fixing them. if they pointed towards a fix I could use their fix.

in reply to DJ Sundog - from the toot-lab

this is me talking out loud about being able to do open source projects without it turning into an open source project.

nobody has to take on a git repo and issue tracker and release schedule and kanban board to do an open source thing. you can just do the thing and open the source and walk away as much as you want. no one can stop you.

reshared this

in reply to DJ Sundog - from the toot-lab

"but sundog, I would be giving up vision and control of my idea"

dear friend, control is fleeting and often illusory. be free.

in reply to DJ Sundog - from the toot-lab

"but sundog, how will people find my project if I'm not on github or gitlab or codeberg or my own git repo website?"

not sure how that affects the functioning of your thing, friend, but probably by reading about it on your blog or something? you should blog or something. and tell people about it. there's this place, the fediverse, people do short blogging there. you could tell those people. they like reading stuff and things.

reshared this

in reply to DJ Sundog - from the toot-lab

if you want to start a larger collaborative thing, that's awesome too, do that! but remember that that's what you are building, and it's that thing that's going to actually make software or whatever happen. plan accordingly.
in reply to DJ Sundog - from the toot-lab

I’m pretty much done with β€œopen source software” as it’s conceived of today. that everything has to be a big project that looks like a corpo project and pretends to be a corpo project or maybe takes on the airs of a Foundation or some other important construct. Every project is to get a job or be on a resume or get onto ars or something else Important.

For a while I was just pooping code onto sourcehut that doesn’t even have most of the features that people want from Open Source. (I adore sourcehut, btw, and doing patches by email and all the rest. Everyone should give them money and help them do well because fuck github really a lot.) And then I just stopped doing even that. Now if you want my code, ask.

in reply to DJ Sundog - from the toot-lab

@sungo shit, six people have each bugged me about getting this code, lemme throw it on a website in a zip archive and be done with it.
in reply to sungo

@sungo OMG, and then they relentlessly treat you like a company, demanding you take on responsibilities, but also offering nothing. @djsundog
in reply to Abbie πŸ³οΈβ€βš§οΈ

yes exactly and if I were a company, that offer of zero value in exchange for my labor would still be a big "no".
in reply to sungo

@sungo between big companies there's lots of things that can be done that are just out of the question when dealing with individuals. One of those things is apparently proper compensation. @djsundog
in reply to sungo

@sungo There's a difference between tinkering, and software that is meant to be useful. If your code was supposed to be tinkering for your own curiosity, or as tutorial to others, then sure, it doesn't need a structure.

But if that software was supposed to do something useful, then the corpo-construct is needed to ensure just that. Otherwise, it's just gaslighting users that you might made a, let's say, CAD app that's useless. People don't have time to waste on useless things.

in reply to DJ Sundog - from the toot-lab

Reminder: FOSS licenses have a "no warranty" disclaimer so that you can effectively do this!
in reply to DJ Sundog - from the toot-lab

I get the rest, but no git? Not even a local one?

I can barely write a shopping list without a git repo. How else do you undo the stuff which seemed like a good idea at the time?

Unknown parent

DJ Sundog - from the toot-lab
@raindrops some really great programmers have been absolutely destroyed by letting the code subsume the thing they were trying to do.
⇧