=== ANCHOR POEM ===
═════════════════════════════════════════════════════════════════════════════════──
you can even design it as you go, making it do slightly adjacent uses in
addition to what it currently does. for example:
https://github.com/gabrilend/r-mail is a reference implementation with some
ideas for how to design some specific parts. make sure you go through it
yourself though, so you understand how it works. don't worry, the source-code
files are numbered like the table of contents [chamber of commerce] in a story
or book.
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧══════════════════════════════════════════════════════════════════════════─┘
=== SIMILARITY RANKED ===
--- #1 fediverse/1168 ---
═══════════════════════════════════════════════────────────────────────────────────
shitty AI products are a classic case of the engineers designing something
really cool with specific use-cases and then the "higher ups" getting dollar
signs for their eyes and deciding that every hammer is suddenly a nail and
that we should pull out all the screws that held the building together and
replace them with hammer shaped nails
no I will not elaborate I think I made myself clear : )
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧════════════════════════════════════════───────────────────────────────────┘
--- #2 fediverse/707 ---
══════════════════════════════════════════════─────────────────────────────────────
@user-524
Sometimes when I feel overwhelmed with all the boilerplate I just start coding
and making stuff. Doesn't matter if it works, doesn't matter if it says /*
FIXME */ all over the place, doesn't matter if it includes header files that
don't exist yet, as long as you're hacking out the mechanics of whatever
operations you need to perform then you can figure the rest of that stuff out
later. The creative urge doesn't last forever, which is why projects get
abandoned, but with discipline you can keep bringing yourself back to fix all
the /* FIXME */'s and the compiler errors.
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧═══════════════════════════════════════────────────────────────────────────┘
--- #3 fediverse/3574 ---
════════════════════════════════════════════════════════───────────────────────────
@user-1564
I love the concept of this! Maybe if HTTP is too complex, you could try
another simpler server? I don't know the complexity of the programs I use
every day, but I'm sure there's one that's very simple. Even just a simple IRC
style chat server that just... sends text from person A to person B depending
on their username (like a glorified Router or Switch)
Reminded of this video tbh...:
https://www.youtube.com/watch?v=gGfTjKwLQxY
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧═════════════════════════════════════════════════──────────────────────────┘
--- #4 fediverse/653 ---
═════════════════════════════════════════════──────────────────────────────────────
there's a difference between designing software and using software. Some
things can be made, and then saved for another day when their implementations
may be accomplished more ethically. It's okay to say "let's leave this as
'okay' and work on the next thing we've chosen."
Check out this piece of C code I wrote last night:
it doesn't compile, it's not finished, but I wrote it as-is
[pretend like it was called "main.c" instead of "main.txt" - had to change it
because mastodon thinks it's an invalid file]
[actually .txt didn't work, try .png]
[hmmm it realized it wasn't a valid png file, okay try screenshotting the
code, there's only 300 lines]
[sure glad there's only 300 lines]
[too bad it won't let you send .zip]
[won't let me name it main.png, presumably because they already have a
failed-verified version on their machine. will rename to main-src.png instead]
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧══════════════════════════════════════─────────────────────────────────────┘
--- #5 fediverse/2475 ---
══════════════════════════════════════════════════════─────────────────────────────
If you want to design a society, first learn how to build a decentralized
scalable multiprocessor computer program.
It could literally flip bits, the point is to practice architecture not
accomplish a goal.
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧═══════════════════════════════════════════════────────────────────────────┘
--- #6 fediverse/440 ---
═════════════════════════════════════════════──────────────────────────────────────
@user-317
Call me crazy, but once something can be described as "ubiquitous" it seems to
me that perhaps it should be considered in the same category as other
corporations or entities who might be known as "monopolous" and therefore
should be considered as part of the set of entities or services that provide
for the "public good" and therefore should be owned by the "public" who
benefit from the "good" that said service provides for?
nationalize github
nationalize government
let us share in the bounty of human creation
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧══════════════════════════════════════─────────────────────────────────────┘
--- #7 fediverse/5478 ---
╔═════════════════════════════════════════════════════════════════════─────────────┐
║ you won't get far with a "community" of dedicated people │
║ │
║ what you need are teams. who can trust each other. you build them through │
║ brotherhood, and you trust them from their results. │
║ │
║ for example if you wanted to organize a grouping or get-together, you'd put a │
║ bunch of people in a room or seven and let them while they're there work on a │
║ plan or a decision. │
║ │
║ who needs tabling? who needs the chance to speak? just let them socialize and │
║ say "hey guys here's where you'll plan" │
║ │
║ [uh no officer we were just playing board games] │
║ │
║ plans are hard without material so make sure you always prepare a pricetag on │
║ each plan you produce. │
║ │
║ keep it for reference. make sure you note all the requirements. the location │
║ is often the least important part. │
║ │
║ "what the hell man you can't just say stuff like that as if it'd work" │
║ │
║ yep, I, uh, am a passenger in life just the same as you. And I only write down │
║ what I want to. │
║ │
║ you could show me anything on the internet and I'd believe it. Facts aren't │
║ important to me because I "forget" │
╟─────────┐ ┌───────────┤
║ similar │ chronological │ different │
╚═════════╧══════════════════════════════════════════════════════════──┴──────────┘
--- #8 fediverse/319 ---
════════════════════════════════════════════───────────────────────────────────────
I wonder if we could make an AI that analyzed workflows in people's jobs and
abstracted the application of meaningful tasks to a pattern that could be
matched to other input mechanisms - for example, a mobile game where you push
buttons and make cool game things happen, but your inputs are defined by the
mechanics of the game, and those mechanics are essentially just function calls
that you can hook onto and create additional behavior. Like... running a web
server that sent your data to a factory where your inputs (based on data
produced in the factory) could control and manage the various machines and
productions. Like... heart surgeon robots that can be remotely operated with
VR or whatever, except instead of medicine you're manufacturing.
essentially, designing a game as an API that can match with the data flows
(configuring itself on the fly, perhaps?) of a process or activity in some
other intention.
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧═════════════════════════════════════──────────────────────────────────────┘
--- #9 fediverse/5979 ---
══════════════════════════════════════════════════════════════════════════─────────
whenever you call a function, just pass along the arguments that you don't
know what to do with yet. they'll surely be useful sometime. and, luckily, you
can always search for them from the past, and just insert a "store this value
in this random spot of memory and mark it as needed" then pass it along. used
something? think it's still useful? pass it along (suddenly, formulaic
stateless development, where everything is used until it's no longer needed,
then generated again in a cyclical time-loop cycle which echoes and
reverberates groundhog day but mostly a game-loop, which nobody will
understand unless you're a game dev. but now since I said game dev, anyone can
look it up, so like... not that one, but others like it.
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧═══════════════════════════════════════════════════════════════════────────┘
--- #10 fediverse/617 ---
═════════════════════════════════════════════──────────────────────────────────────
So much of computing is just... handling the quirks of hardware and presenting
it to the user (programmer) in a way that is sane and makes sense, instead of
the arcane and [nebulous/confabulous/incomprehensible] way that physical
nature demands our absurdly potentialized computational endeavors be.
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧══════════════════════════════════════─────────────────────────────────────┘
--- #11 fediverse/4092 ---
═══════════════════════════════════════════════════════════────────────────────────
why not make a unified fediverse identity that can post on whatever instance
it wants?
... hmmm could be accomplished with a layer of abstraction. You could use a
"fediverse client" software to enter text into an HTML page which would have
it's own UI and stuff and would organize your accounts and instances such that
you could mark like, 3-7 as places you'd like to put a particular message.
Then it would just... do it
l m a o spam is gonna get sooooo much worse before it gets better
but trust me, we'll figure it out. And it won't be long, either. It's a
solvable problem, we just haven't built anything to handle it yet.
... yet...
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧════════════════════════════════════════════════════───────────────────────┘
--- #12 fediverse/5386 ---
══════════════════════════════════════════════════════════════════════─────────────
@user-670 @user-1815 @user-1816
literally nobody has contributed to the one github repo I have
ever. I got like, one comment from some guy in China or Taiwan. It's been up
for like, 4 or 5 years and it's on my website. /shrug I guess most people
bounce off after reading the splash screen /shrug
to me, a FOSS project feels static because I don't believe in centralization
and I also don't have the bandwidth or need to work on it. /shrug
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧═══════════════════════════════════════════════════════════════────────────┘
--- #13 fediverse/5212 ---
════════════════════════════════════════════════════════════════════───────────────
the reason you start with a game engine is because then you'll have tools to
make however-many games you want. Tools that you know intimately enough that
you can debug and improve them without breaking your creative flow by learning
something new halfway through a project
the whole point of individualized projects instead of viewing each computer as
a complete and total whole (why do we need servers again?) is that you can
paint a picture of where the design of the program is intended to go, such
that all the considerations are in place and whatever issues or struggles you
might face along the way are adequately addresssed, -- stack overflow --
[because I mistyped addressed] -- -- if you know what "stack overflow" means
you have intimate knowledge of the technology, and can probably guess what it
means in context when I say it. "nuts I lost that train of thoguht" -- stackl
ov
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧═════════════════════════════════════════════════════════════──────────────┘
--- #14 messages/89 ---
════════════════════════════════════════════───────────────────────────────────────
Consumption is contribution to a capitalist system. Normalize taking whatever
you are given and living as humbly as you can. Only when everyone does that
may capitalism die. Talk to them, learn from their stories. Teach them your
ways but don't force anything upon them. Any ounce of regret is defined as a
mind not aligned to the angle of perception that designs the line that the
collective mind co-re-assigns.
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧═════════════════════════════════════──────────────────────────────────────┘
--- #15 fediverse/2879 ---
══════════════════════════════════════════════════════─────────────────────────────
┌────────────────────────┐
│ CW: re: tech info-dump │
└────────────────────────┘
@user-1370
I love this a lot! I want to put function pointers in a "matrix architecture
array" and make them point to different functions at different points in the
program. I bet you could even point them at each other, so like if M and Y
then point at N, A, Y or something.
this is really cool I like stuff like this tomorrow I'll take pictures of
something similar I'm working on! I abandoned it tho hehe anyway remind me if
I forget!!
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧═══════════════════════════════════════════════────────────────────────────┘
--- #16 fediverse/5689 ---
═══════════════════════════════════════════════════════════════════════────────────
why don't we make large arrays of vram that are slightly slower because
they're farther on the circuit-board from their host and their reception at
the processing section has to be gated such that they all enter to be
processed at once.
like that one infinite scrolling XKCD cartoon where the things move from one
screen to the other simultaneously assembly line style.
[fail safes. https://xkcd.com/2916/#xt=7&yt=35 ]
if we all feel like we're doing nothing, we'll all grow tired of it and decide
to do some prevailing. gosh I wish I wasn't so useless is code for
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧════════════════════════════════════════════════════════════════───────────┘
--- #17 fediverse/308 ---
════════════════════════════════════════════───────────────────────────────────────
when tech people are hurt by technology they say "how can I fix this? what do
I need to install? what configuration should I use? is this company ethical,
or are they going to hurt me in the future? could I make something that fixes
this myself?"
when non-tech people are hurt by technology they say "okay" because they don't
have the bandwidth to figure it out.
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧═════════════════════════════════════──────────────────────────────────────┘
--- #18 fediverse/364 ---
╔════════════════════════════════════════════──────────────────────────────────────┐
║ okay here's an idea, waterfall project management where the program is │
║ developed one tiny piece at a time while being streamed to the entire company. │
║ Everyone would submit answers which could be upvoted / patched / rewritten as │
║ the main viewer cycles through each aspect of the project, checking for │
║ updates to it's design that were suggested by developers or whatever. │
║ Basically, one person (or one team) gets to write the actual source code, │
║ while everyone else is just offering suggestions. You could break it up by │
║ specialty, but the whole point is that everyone gets a complete picture of how │
║ the program (and organization) is structured. Which should give the employees │
║ more power to generate value for the company. All around a good deal I think? │
║ Especially if the main viewer took time to explain each and every part so that │
║ every viewer had the chance to understand. │
║ │
║ the reason why order is important is that our actions ripple through eternity. │
║ we must set a good example for all the baby aliens, don't you think? │
╟─────────┐ ┌───────────┤
║ similar │ chronological │ different │
╚═════════╧═════════════════════════════════───────────────────────────┴──────────┘
--- #19 fediverse/1810 ---
═════════════════════════════════════════════════════──────────────────────────────
some people hear words like "datastructures" and "object-oriented programming"
and think they're made up terms that don't mean anything important.
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧══════════════════════════════════════════════─────────────────────────────┘
--- #20 messages/1392 ---
══════════════════════════════════════════════════════════════════════════════════─
It's good organization? Actually? If something falls when you jostle something
else. It means that what you're doing is causing the system to become
unstable, thus allowing unexpected reactions to allowenable. Like stuff
falling or getting dropped, not ideal.
much better to do your cable management in mind with instability as a goal,
like a canary in the coal mine for "damage-imminent". Design for permanence,
not resilience. If you can prevent problems before they occur by confidently
saying "no" and ideally earnestly saying "here's what you do to resolve your
problem because i know better" (but if you don't know it's okay, especially if
you know who to refer them to who might know better.) then it's easier to
build a repetitive system. Like an institution of people who are working to
fix a problem or fill a social gap need. "how do we keep the water" or "where
does our food come from" can be helpful and useful questions to ask,
especially if work is done to answer them. So... "Go find out" is a reasonable
response for an idle question about stuff that might go right or wrong. Urgent
questions might need a bit of cooperation to resolve, triaging of course.
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧═══════════════════════════════════════════════════════════════════════════┘
|