https://bitcointalksearch.org/topic/m.669898
https://bitcointalk.org/first_topics/
Topic: Can we make all of satoshi's posts in restriced sections of this forum public? (Read 180 times)
July 07, 2018, 07:39:40 PM
July 07, 2018, 07:16:23 PM
I was looking at the advertising slot bidding as I often consider bidding for a slot but aren't sure how much ref income I would actually draw in from it and I'd like to donate to the site but only when I actually have enough Bitcoin to do so.
Anyway, I was looking at this thread: https://bitcointalk.org/ad_test.html
Satoshi made the coins!
I then thought, if satoshi came up with the idea for using the coins, maybe there are a lot of other interesting parts of this forum that he also designed. Hence why I'd like stuff in that board that he wrote to make it public.
Or is there any chance that some restricted sections of the forum could have posts released publicly with a 1/2 year delay as certain cases may be useful for other members of the forum to know (e.g. other people who use SMF if there is a software fix or something from a hack then others could also use that fix). These released posts could obviously be restricted if a flaw is found that isn't fixed and is just left "as is" in the hope a fix will be found so that other people don't try to manipulate that error.
Anyway, I was looking at this thread: https://bitcointalk.org/ad_test.html
Satoshi made the coins!
I then thought, if satoshi came up with the idea for using the coins, maybe there are a lot of other interesting parts of this forum that he also designed. Hence why I'd like stuff in that board that he wrote to make it public.
Or is there any chance that some restricted sections of the forum could have posts released publicly with a 1/2 year delay as certain cases may be useful for other members of the forum to know (e.g. other people who use SMF if there is a software fix or something from a hack then others could also use that fix). These released posts could obviously be restricted if a flaw is found that isn't fixed and is just left "as is" in the hope a fix will be found so that other people don't try to manipulate that error.
Jump to: