#roll-your-own — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #roll-your-own, aggregated by home.social.
-
Make what you need might be all wrong for the IndieWeb’s future
IndieWeb has this idea of “scratch your own itch” or “make what you need“. It’s okay in as far as it goes, but I (and I said this at great length before) feel it is wholly incomplete over simple, and, therefore, wrong.
I get the idea. If I want a cheese sandwich, I should go into the kitchen and make myself a cheese sandwich. Fine. Cool. But I’m not making what I need – I’m assembling the prefabricated parts.
I did not first have to make a bread knife, and a butter knife, and a plate, and a chopping board. I did not have to bake the bread. I did not have to spend a year or two maturing milk into cheese. I did not build the kitchen or the worktops. In fact, I did not build what I needed at all. I acquired well-made things I needed so that when the time came, I could put the cheese and the bread together in a pleasing shape.
In the same way, “make what you need” works well when IndieWeb is a frontier wild west of ideas. Where the only ones making the new tools are the ones using those tools and only because those were the only nerds who could make the things.
We no longer live in the wild west. We live in towns. We go to supermarkets and order pizza delivered to our door.
I get that dogfooding is the best way to make sure the tools available are the best they can be. I’m not a novice at this. What I am saying is that it is time we started putting together pre-baked bread, already matured cheese, and a sharp knife that works out of the box.
Early adopters can and should make their own. That’s the innovation scale and space. But there has to come a time when we start embracing pre-sliced bread, cheese someone else made, and all that, without forcing everyone to fire up the forge because you want a sandwich.
If we want indieweb ideas to go from niche coders doing niche coder things, we need something the next wave of later-early adopters can get to grips with. In such an environment, “make what you need” is not good enough. It has to give way to “make what those around you need” or “make something you can use, but your mum could use too”.
One example of “make what you need” screwing the pooch is the number of websites that stopped using WebMention because of spam. WebMention should, by its nature, be nearly spam-proof. I would hazard a guess that the roll-your-own WebMention did not follow the step where it confirms the link that forms the core mention.
When WebMention runs in WordPress, the mention fails if the link is not there. Then the mention, if from an unrecognised blog, is held in a queue to be manually checked. These steps mean that no spam makes it into my blog via WebMention. Via local comments – yeah, loads of spam; but WebMention – never.
There is an expression in developer circles which is a warning against reinventing the square wheel. By rolling their own, some devs will make an objectively worse version. There might be better versions too; its a wild world out there. The point is, though, rather than reinventing the wheel for each and every website, some battle-hardened, mature, production-ready, tested and true tools and libraries might offer something of an advantage.
That’s the power of Open Source development. One person makes a thing; a bunch of people use the thing; someone has an idea for a new feature and adds it. I think IndieWeb needs that too. At the very least, “make what you need” should become “adapt what you need; reuse when possible”.
Check out my longer form post: Let’s talk about making IndieWeb weirder and easier
-
Make what you need might be all wrong for the IndieWeb’s future
IndieWeb has this idea of “scratch your own itch” or “make what you need“. It’s okay in as far as it goes, but I (and I said this at great length before) feel it is wholly incomplete over simple, and, therefore, wrong.
I get the idea. If I want a cheese sandwich, I should go into the kitchen and make myself a cheese sandwich. Fine. Cool. But I’m not making what I need – I’m assembling the prefabricated parts.
I did not first have to make a bread knife, and a butter knife, and a plate, and a chopping board. I did not have to bake the bread. I did not have to spend a year or two maturing milk into cheese. I did not build the kitchen or the worktops. In fact, I did not build what I needed at all. I acquired well-made things I needed so that when the time came, I could put the cheese and the bread together in a pleasing shape.
In the same way, “make what you need” works well when IndieWeb is a frontier wild west of ideas. Where the only ones making the new tools are the ones using those tools and only because those were the only nerds who could make the things.
We no longer live in the wild west. We live in towns. We go to supermarkets and order pizza delivered to our door.
I get that dogfooding is the best way to make sure the tools available are the best they can be. I’m not a novice at this. What I am saying is that it is time we started putting together pre-baked bread, already matured cheese, and a sharp knife that works out of the box.
Early adopters can and should make their own. That’s the innovation scale and space. But there has to come a time when we start embracing pre-sliced bread, cheese someone else made, and all that, without forcing everyone to fire up the forge because you want a sandwich.
If we want indieweb ideas to go from niche coders doing niche coder things, we need something the next wave of later-early adopters can get to grips with. In such an environment, “make what you need” is not good enough. It has to give way to “make what those around you need” or “make something you can use, but your mum could use too”.
One example of “make what you need” screwing the pooch is the number of websites that stopped using WebMention because of spam. WebMention should, by its nature, be nearly spam-proof. I would hazard a guess that the roll-your-own WebMention did not follow the step where it confirms the link that forms the core mention.
When WebMention runs in WordPress, the mention fails if the link is not there. Then the mention, if from an unrecognised blog, is held in a queue to be manually checked. These steps mean that no spam makes it into my blog via WebMention. Via local comments – yeah, loads of spam; but WebMention – never.
There is an expression in developer circles which is a warning against reinventing the square wheel. By rolling their own, some devs will make an objectively worse version. There might be better versions too; its a wild world out there. The point is, though, rather than reinventing the wheel for each and every website, some battle-hardened, mature, production-ready, tested and true tools and libraries might offer something of an advantage.
That’s the power of Open Source development. One person makes a thing; a bunch of people use the thing; someone has an idea for a new feature and adds it. I think IndieWeb needs that too. At the very least, “make what you need” should become “adapt what you need; reuse when possible”.
Check out my longer form post: Let’s talk about making IndieWeb weirder and easier
-
Make what you need might be all wrong for the IndieWeb’s future
IndieWeb has this idea of “scratch your own itch” or “make what you need“. It’s okay in as far as it goes, but I (and I said this at great length before) feel it is wholly incomplete over simple, and, therefore, wrong.
I get the idea. If I want a cheese sandwich, I should go into the kitchen and make myself a cheese sandwich. Fine. Cool. But I’m not making what I need – I’m assembling the prefabricated parts.
I did not first have to make a bread knife, and a butter knife, and a plate, and a chopping board. I did not have to bake the bread. I did not have to spend a year or two maturing milk into cheese. I did not build the kitchen or the worktops. In fact, I did not build what I needed at all. I acquired well-made things I needed so that when the time came, I could put the cheese and the bread together in a pleasing shape.
In the same way, “make what you need” works well when IndieWeb is a frontier wild west of ideas. Where the only ones making the new tools are the ones using those tools and only because those were the only nerds who could make the things.
We no longer live in the wild west. We live in towns. We go to supermarkets and order pizza delivered to our door.
I get that dogfooding is the best way to make sure the tools available are the best they can be. I’m not a novice at this. What I am saying is that it is time we started putting together pre-baked bread, already matured cheese, and a sharp knife that works out of the box.
Early adopters can and should make their own. That’s the innovation scale and space. But there has to come a time when we start embracing pre-sliced bread, cheese someone else made, and all that, without forcing everyone to fire up the forge because you want a sandwich.
If we want indieweb ideas to go from niche coders doing niche coder things, we need something the next wave of later-early adopters can get to grips with. In such an environment, “make what you need” is not good enough. It has to give way to “make what those around you need” or “make something you can use, but your mum could use too”.
One example of “make what you need” screwing the pooch is the number of websites that stopped using WebMention because of spam. WebMention should, by its nature, be nearly spam-proof. I would hazard a guess that the roll-your-own WebMention did not follow the step where it confirms the link that forms the core mention.
When WebMention runs in WordPress, the mention fails if the link is not there. Then the mention, if from an unrecognised blog, is held in a queue to be manually checked. These steps mean that no spam makes it into my blog via WebMention. Via local comments – yeah, loads of spam; but WebMention – never.
There is an expression in developer circles which is a warning against reinventing the square wheel. By rolling their own, some devs will make an objectively worse version. There might be better versions too; its a wild world out there. The point is, though, rather than reinventing the wheel for each and every website, some battle-hardened, mature, production-ready, tested and true tools and libraries might offer something of an advantage.
That’s the power of Open Source development. One person makes a thing; a bunch of people use the thing; someone has an idea for a new feature and adds it. I think IndieWeb needs that too. At the very least, “make what you need” should become “adapt what you need; reuse when possible”.
Check out my longer form post: Let’s talk about making IndieWeb weirder and easier
-
Make what you need might be all wrong for the IndieWeb’s future
IndieWeb has this idea of “scratch your own itch” or “make what you need“. It’s okay in as far as it goes, but I (and I said this at great length before) feel it is wholly incomplete over simple, and, therefore, wrong.
I get the idea. If I want a cheese sandwich, I should go into the kitchen and make myself a cheese sandwich. Fine. Cool. But I’m not making what I need – I’m assembling the prefabricated parts.
I did not first have to make a bread knife, and a butter knife, and a plate, and a chopping board. I did not have to bake the bread. I did not have to spend a year or two maturing milk into cheese. I did not build the kitchen or the worktops. In fact, I did not build what I needed at all. I acquired well-made things I needed so that when the time came, I could put the cheese and the bread together in a pleasing shape.
In the same way, “make what you need” works well when IndieWeb is a frontier wild west of ideas. Where the only ones making the new tools are the ones using those tools and only because those were the only nerds who could make the things.
We no longer live in the wild west. We live in towns. We go to supermarkets and order pizza delivered to our door.
I get that dogfooding is the best way to make sure the tools available are the best they can be. I’m not a novice at this. What I am saying is that it is time we started putting together pre-baked bread, already matured cheese, and a sharp knife that works out of the box.
Early adopters can and should make their own. That’s the innovation scale and space. But there has to come a time when we start embracing pre-sliced bread, cheese someone else made, and all that, without forcing everyone to fire up the forge because you want a sandwich.
If we want indieweb ideas to go from niche coders doing niche coder things, we need something the next wave of later-early adopters can get to grips with. In such an environment, “make what you need” is not good enough. It has to give way to “make what those around you need” or “make something you can use, but your mum could use too”.
One example of “make what you need” screwing the pooch is the number of websites that stopped using WebMention because of spam. WebMention should, by its nature, be nearly spam-proof. I would hazard a guess that the roll-your-own WebMention did not follow the step where it confirms the link that forms the core mention.
When WebMention runs in WordPress, the mention fails if the link is not there. Then the mention, if from an unrecognised blog, is held in a queue to be manually checked. These steps mean that no spam makes it into my blog via WebMention. Via local comments – yeah, loads of spam; but WebMention – never.
There is an expression in developer circles which is a warning against reinventing the square wheel. By rolling their own, some devs will make an objectively worse version. There might be better versions too; its a wild world out there. The point is, though, rather than reinventing the wheel for each and every website, some battle-hardened, mature, production-ready, tested and true tools and libraries might offer something of an advantage.
That’s the power of Open Source development. One person makes a thing; a bunch of people use the thing; someone has an idea for a new feature and adds it. I think IndieWeb needs that too. At the very least, “make what you need” should become “adapt what you need; reuse when possible”.
Check out my longer form post: Let’s talk about making IndieWeb weirder and easier
-
Make what you need might be all wrong for the IndieWeb’s future
IndieWeb has this idea of “scratch your own itch” or “make what you need“. It’s okay in as far as it goes, but I (and I said this at great length before) feel it is wholly incomplete over simple, and, therefore, wrong.
I get the idea. If I want a cheese sandwich, I should go into the kitchen and make myself a cheese sandwich. Fine. Cool. But I’m not making what I need – I’m assembling the prefabricated parts.
I did not first have to make a bread knife, and a butter knife, and a plate, and a chopping board. I did not have to bake the bread. I did not have to spend a year or two maturing milk into cheese. I did not build the kitchen or the worktops. In fact, I did not build what I needed at all. I acquired well-made things I needed so that when the time came, I could put the cheese and the bread together in a pleasing shape.
In the same way, “make what you need” works well when IndieWeb is a frontier wild west of ideas. Where the only ones making the new tools are the ones using those tools and only because those were the only nerds who could make the things.
We no longer live in the wild west. We live in towns. We go to supermarkets and order pizza delivered to our door.
I get that dogfooding is the best way to make sure the tools available are the best they can be. I’m not a novice at this. What I am saying is that it is time we started putting together pre-baked bread, already matured cheese, and a sharp knife that works out of the box.
Early adopters can and should make their own. That’s the innovation scale and space. But there has to come a time when we start embracing pre-sliced bread, cheese someone else made, and all that, without forcing everyone to fire up the forge because you want a sandwich.
If we want indieweb ideas to go from niche coders doing niche coder things, we need something the next wave of later-early adopters can get to grips with. In such an environment, “make what you need” is not good enough. It has to give way to “make what those around you need” or “make something you can use, but your mum could use too”.
One example of “make what you need” screwing the pooch is the number of websites that stopped using WebMention because of spam. WebMention should, by its nature, be nearly spam-proof. I would hazard a guess that the roll-your-own WebMention did not follow the step where it confirms the link that forms the core mention.
When WebMention runs in WordPress, the mention fails if the link is not there. Then the mention, if from an unrecognised blog, is held in a queue to be manually checked. These steps mean that no spam makes it into my blog via WebMention. Via local comments – yeah, loads of spam; but WebMention – never.
There is an expression in developer circles which is a warning against reinventing the square wheel. By rolling their own, some devs will make an objectively worse version. There might be better versions too; its a wild world out there. The point is, though, rather than reinventing the wheel for each and every website, some battle-hardened, mature, production-ready, tested and true tools and libraries might offer something of an advantage.
That’s the power of Open Source development. One person makes a thing; a bunch of people use the thing; someone has an idea for a new feature and adds it. I think IndieWeb needs that too. At the very least, “make what you need” should become “adapt what you need; reuse when possible”.
Check out my longer form post: Let’s talk about making IndieWeb weirder and easier
-
@smallcircles someone could start selling an all-in-one appliance, like a WiFi router with a built-in mail server, ActivityPub server, XMPP server, #Forgejo server, and #Drupal server all rolled into one. Then instead of recommending people “roll their own,” you could recommend people just buy this device, and use it to connect to #ActivityPub, #XMPP, and publish their own blog with the built-in Drupal server, and so on.
-
@smallcircles someone could start selling an all-in-one appliance, like a WiFi router with a built-in mail server, ActivityPub server, XMPP server, #Forgejo server, and #Drupal server all rolled into one. Then instead of recommending people “roll their own,” you could recommend people just buy this device, and use it to connect to #ActivityPub, #XMPP, and publish their own blog with the built-in Drupal server, and so on.
-
@smallcircles someone could start selling an all-in-one appliance, like a WiFi router with a built-in mail server, ActivityPub server, XMPP server, #Forgejo server, and #Drupal server all rolled into one. Then instead of recommending people “roll their own,” you could recommend people just buy this device, and use it to connect to #ActivityPub, #XMPP, and publish their own blog with the built-in Drupal server, and so on.
-
@smallcircles someone could start selling an all-in-one appliance, like a WiFi router with a built-in mail server, ActivityPub server, XMPP server, #Forgejo server, and #Drupal server all rolled into one. Then instead of recommending people “roll their own,” you could recommend people just buy this device, and use it to connect to #ActivityPub, #XMPP, and publish their own blog with the built-in Drupal server, and so on.
-
“Yes. Yes! That’s IT. We have backups instead of blasters, ping instead of parsecs, and df(1) instead of droids, but it’s the same sort of struggle. Okay, fine, planets don’t get blown up… yet.”
#email #RollYourOwn #RunYourOwnMailServer https://www.kickstarter.com/projects/mwlucas/run-your-own-mail-server/
-
“Yes. Yes! That’s IT. We have backups instead of blasters, ping instead of parsecs, and df(1) instead of droids, but it’s the same sort of struggle. Okay, fine, planets don’t get blown up… yet.”
#email #RollYourOwn #RunYourOwnMailServer https://www.kickstarter.com/projects/mwlucas/run-your-own-mail-server/
-
“Yes. Yes! That’s IT. We have backups instead of blasters, ping instead of parsecs, and df(1) instead of droids, but it’s the same sort of struggle. Okay, fine, planets don’t get blown up… yet.”
#email #RollYourOwn #RunYourOwnMailServer https://www.kickstarter.com/projects/mwlucas/run-your-own-mail-server/
-
“Yes. Yes! That’s IT. We have backups instead of blasters, ping instead of parsecs, and df(1) instead of droids, but it’s the same sort of struggle. Okay, fine, planets don’t get blown up… yet.”
#email #RollYourOwn #RunYourOwnMailServer https://www.kickstarter.com/projects/mwlucas/run-your-own-mail-server/
-
“Yes. Yes! That’s IT. We have backups instead of blasters, ping instead of parsecs, and df(1) instead of droids, but it’s the same sort of struggle. Okay, fine, planets don’t get blown up… yet.”
#email #RollYourOwn #RunYourOwnMailServer https://www.kickstarter.com/projects/mwlucas/run-your-own-mail-server/
-
@knapjack @#GeekAllWeek@bonk.cozysumo.space @#RollYourOwn@bonk.cozysumo.space @#BangleJS@bonk.cozysumo.space that’s very cool. I like this interface.
-
@knapjack @#GeekAllWeek@bonk.cozysumo.space @#RollYourOwn@bonk.cozysumo.space @#BangleJS@bonk.cozysumo.space that’s very cool. I like this interface.
-
@knapjack @#GeekAllWeek@bonk.cozysumo.space @#RollYourOwn@bonk.cozysumo.space @#BangleJS@bonk.cozysumo.space that’s very cool. I like this interface.
-
@knapjack @#GeekAllWeek@bonk.cozysumo.space @#RollYourOwn@bonk.cozysumo.space @#BangleJS@bonk.cozysumo.space that’s very cool. I like this interface.
-
@knapjack @#GeekAllWeek@bonk.cozysumo.space @#RollYourOwn@bonk.cozysumo.space @#BangleJS@bonk.cozysumo.space that’s very cool. I like this interface.
-
#Tweet "BM: Well [obscurity is] also a way of maintaining security."
Rolling your own crypto is just too dangerous in 2023. #Tetra #ETSI #Weak #Encryption #RollYourOwn
https://zetter.substack.com/p/interview-with-the-etsi-standards https://waldvogel.family/@marcel/110794990650677584 https://twitter.com/mndell/status/1685208094962257920
-
#Tweet "BM: Well [obscurity is] also a way of maintaining security."
Rolling your own crypto is just too dangerous in 2023. #Tetra #ETSI #Weak #Encryption #RollYourOwn
https://zetter.substack.com/p/interview-with-the-etsi-standards https://waldvogel.family/@marcel/110794990650677584 https://twitter.com/mndell/status/1685208094962257920
-
#Tweet "BM: Well [obscurity is] also a way of maintaining security."
Rolling your own crypto is just too dangerous in 2023. #Tetra #ETSI #Weak #Encryption #RollYourOwn
https://zetter.substack.com/p/interview-with-the-etsi-standards https://waldvogel.family/@marcel/110794990650677584 https://twitter.com/mndell/status/1685208094962257920
-
#Tweet "BM: Well [obscurity is] also a way of maintaining security."
Rolling your own crypto is just too dangerous in 2023. #Tetra #ETSI #Weak #Encryption #RollYourOwn
https://zetter.substack.com/p/interview-with-the-etsi-standards https://waldvogel.family/@marcel/110794990650677584 https://twitter.com/mndell/status/1685208094962257920
-
In addition, there is another tendency to say "we *could* #rollyourown, but let's use a #library instead."
This shouldn't be a hard and fast thing though. A lot of the time you end up net negative because the work you did to 1. install the #dependency 2. #adapt your code to use it is more than it took just to roll your own, if it's a simple process.
You also are asking for situations like the 2016 #leftpad disaster:
https://qz.com/646467/how-one-programmer-broke-the-internet-by-deleting-a-tiny-piece-of-code
-
In addition, there is another tendency to say "we *could* #rollyourown, but let's use a #library instead."
This shouldn't be a hard and fast thing though. A lot of the time you end up net negative because the work you did to 1. install the #dependency 2. #adapt your code to use it is more than it took just to roll your own, if it's a simple process.
You also are asking for situations like the 2016 #leftpad disaster:
https://qz.com/646467/how-one-programmer-broke-the-internet-by-deleting-a-tiny-piece-of-code
-
In addition, there is another tendency to say "we *could* #rollyourown, but let's use a #library instead."
This shouldn't be a hard and fast thing though. A lot of the time you end up net negative because the work you did to 1. install the #dependency 2. #adapt your code to use it is more than it took just to roll your own, if it's a simple process.
You also are asking for situations like the 2016 #leftpad disaster:
https://qz.com/646467/how-one-programmer-broke-the-internet-by-deleting-a-tiny-piece-of-code
-
Might use an old iMac as a Debian box to spin up a personal mastodon server today… if anyone has any advice or links to good howtos or tips/tricks (I’m just using the https://docs.joinmastodon.org) I’m all ears.
-
Might use an old iMac as a Debian box to spin up a personal mastodon server today… if anyone has any advice or links to good howtos or tips/tricks (I’m just using the https://docs.joinmastodon.org) I’m all ears.
-
Might use an old iMac as a Debian box to spin up a personal mastodon server today… if anyone has any advice or links to good howtos or tips/tricks (I’m just using the https://docs.joinmastodon.org) I’m all ears.
-
Might use an old iMac as a Debian box to spin up a personal mastodon server today… if anyone has any advice or links to good howtos or tips/tricks (I’m just using the https://docs.joinmastodon.org) I’m all ears.
-
Might use an old iMac as a Debian box to spin up a personal mastodon server today… if anyone has any advice or links to good howtos or tips/tricks (I’m just using the https://docs.joinmastodon.org) I’m all ears.
-
I finally scored something good at a garage sale; a film bulk loader and a bunch of reloadable metal film canisters for $5! The freezer bag even says “Sweet Rolls.” #BelieveInFilm #BelieveInGarageSales #RollYourOwn
-
I finally scored something good at a garage sale; a film bulk loader and a bunch of reloadable metal film canisters for $5! The freezer bag even says “Sweet Rolls.” #BelieveInFilm #BelieveInGarageSales #RollYourOwn
-
I finally scored something good at a garage sale; a film bulk loader and a bunch of reloadable metal film canisters for $5! The freezer bag even says “Sweet Rolls.” #BelieveInFilm #BelieveInGarageSales #RollYourOwn
-
I finally scored something good at a garage sale; a film bulk loader and a bunch of reloadable metal film canisters for $5! The freezer bag even says “Sweet Rolls.” #BelieveInFilm #BelieveInGarageSales #RollYourOwn
-
I finally scored something good at a garage sale; a film bulk loader and a bunch of reloadable metal film canisters for $5! The freezer bag even says “Sweet Rolls.” #BelieveInFilm #BelieveInGarageSales #RollYourOwn
-
One way to setup a personal Mastodon instance (Docker) with a lot of optional extras 👍 🐘
https://vitobotta.com/2022/11/07/setting-up-a-personal-mastodon-instance
-
I decided to bite the bullet and transfer my account from the "big" server to my own tiny instance.
It looks like my small list of followers transferred across without problems, but I am still having the issue where some of my follows are showing up in a "waiting for approval" state.
This instance feels way snappier than the bigger one, but I guess this is to be expected since right now it has a grand total of 2 users.
-
Well, I rolled out my own Mastodon instance on my tiny Docker host. For now I will probably just use it to figure out what all of the buttons do.
One thing does have me perplexed, following people on certain instances seems to require approval when done so from my own instance, while following the same people from mastodon.social does not.
I'm guessing mastodon.social is somehow whitelisted with most other instances and my own brand new instance is not.
-
@Tutanota
Checking your own code is not an audit. An audit, by definition is conducted by third-parties. Users will decide who they trust to audit the client they use with your service, whether it's yours or a third-party one. If what you're doing is transparently secure, rather than depending on #SecurityByObscurity, surely it's based on common protocols, and standard crypto not #RollYourOwn, and has clearly documented specs that third-parties can follow securely.
@resist1984 -
@Tutanota
Checking your own code is not an audit. An audit, by definition is conducted by third-parties. Users will decide who they trust to audit the client they use with your service, whether it's yours or a third-party one. If what you're doing is transparently secure, rather than depending on #SecurityByObscurity, surely it's based on common protocols, and standard crypto not #RollYourOwn, and has clearly documented specs that third-parties can follow securely.
@resist1984 -
@byuu, author of #bsnes and #higan, wrote a passionate and #inspirational article about daring to learn to experiment and not get put down by people who say you should stick to what you know and use stable things rather than trying to #rollYourOwn:
https://articles.byuu.org/experiment
They describe how they went from being a fan of #RPGe #fanTranslations to getting into #ROMhacking, to #emulation and #electronics. Definitely worth a read.