 Show Posts
|
|
Pages: [1] 2 3 4 5 »
|
Hello, we are working on migration details at the moment. The source code for migration details aren't public for security reasons. Thanks but we're trying to be as thorough as possible for the sake of the community and the rich history that have been collected on this forum. Millions went to this project, while there is no product. just github files keep getting updated from day to day to kill time.
GitHub files aren't updated to kill time. If you look at the commits, every commit message has some information along with it which explains what exactly the files are updated for. What scares me is, the last commit was around July 7th https://github.com/epochtalk/epochtalk/pull/457/commits/91599ad083e33fc0314628fdae9c88f297894760 and not sure if the website is being actively developed. I mean, activity definitely seems low. But looking at dev history, there may be private repos they are working on. IF Epoch (the database layer) is related to EpochTalk (which I'm assuming it would be) the last commit wasn't July. It was commited to 12 days ago. https://github.com/epochtalk/epoch |
|
|
|
|
This is an inappropriate sample size (lol). We can do another vote later!
|
|
|
|
Absolutely right. I will give an update on the next deployment update. Thanks for pointing this out. We will have this fixed in the near future.
Thanks for your attention to security! I will look forward to checking out the beta site. Is this reported at all in other browsers, or are Bitcoin users (who should know better) clicking through browser warnings as they never, never, ever should? I’m guessing that at least all Firefox users get the same warning. I guess also I could fiddle with s_client and figure out what the problem actually is... As for epochtalk.org, this is actually static content so there is no need for SSL at the moment.
Hey, it’s a cypherpunk thing! (grin) Encrypt the whole Internet. A free certificate from letsencrypt.org, a few minutes twiddling the webserver, use public-key crypto to control your personal fortune... It all fits together, no matter whether a site is static or not. N.b. that injected Javascript can harm users, even on static sites. In the wild: NSA does it, some ISPs do it, and skiddies with firesheep on the wifi do it, too. TLS is needed on every site. |
|
|
|
|
Thanks for pointing this out. We will have this fixed in the near future. As for epochtalk.org, this is actually static content so there is no need for SSL at the moment.
|
|
|
|
in General I have the same problem ( Error: Abuse Detected. You have been banned from performing this action. Please contact an administrator), as I understand it no one even really knows what to do with that?
I'm too can't log in - Abuse Detected. Why?
I'm not abuse!
Looking into your accounts... |
|
|
|
|
The choice may have been different if we were to start the project now. But I believe that interfaces are what matters. Also, we kind of didn't have a choice on the frontend. If you would like to see, our migration layer and database schema design is written in Elixir and Ecto. As for JS, there are definitely shortcomings but performance-wise, Node is good enough on the server side for the time being.
Do you have any specific questions?
|
|
|
|
Epochtalk is extremely complicated especially on the admin side of things. That includes moderation/accountability, etc. For comparison, forums like Discourse have been in development a lot longer than us. Take a look at the issues we have on the Github and try it out or something. Note, that the dependencies that are being developed are also under the entire epochtalk organization. I feel like a broken record because these questions have been answered over and over. Apologies for not having anything more central and easier to digest than the Github repos. Really? Is beta.bitcointalk.org legit the latest version? It's been 3 years and this is it? What is it being coded in... assembly? If I remember correctly, the budget for the site was in the tens of thousands of BTC. At today's value, it'd probably be a $50MM bid. I'm thinking the admins were swindled in the bid... I think it should go back open or at least make a more open competition for the new software. Edit: Found the source. It's freaking Javascript... that's why. Who would want that ungodly mess to manage? ew. Edit2: https://github.com/epochtalk/epochtalk for those that can't google. |
|
|
|
Will the new forum be released in the year 2018? http://epochtalk.org/Those who know (Slickage team members), one of the following answers (if possible) would be highly appreciated. No Yes It's planned It's not planned Thank you so much and keep up the nice work All of the above! (jk) Planned for release before the end of the year and finishing migration in 2018. This stuff is incredibly sensitive because we don't have access to the full database and we're migrating data based on a running system. If you have any issues on the development. Please submit something here or on Github. Thanks for the nice words! |
|
|
|
Yeah, it's long overdue but it is being worked on constantly as we speak. Personally, I would rather wait until it's absolutely finished/watertight and has been tested thoroughly before being released. The last thing we need is a buggy forum ready to be exploited.
Check our Github if you guys have questions. There are issues and constant branches being worked on. Keep in mind that the entire epochtalk organization has repositories and not all code is in the main project. Thank you for being patient. |
|
|
|
Is it possible to remotely terminate another device's session on bitcointalk that's using the same account? I noticed that I can login with my phone and PC simultaneously and also post with the same device at the same time. Would this feature be added on the new forum software? In this way, users can track where are they logged in and to possibly know whether their account is compromised by looking on their active session history. It might be a cool feature to add in the future tbh.
This is a very good point. Introduction of sessions being tracked on the server side is definitely part of our authentication and security features. We will reach out for usability concerns once this is in place. |
|
|
|
LOL, I promise you the searching will be way better. Demo for you guys pretty soon.
Wait, better then before it was scaled back? Dude, you just made dick hard - AGAIN (damn, will this hour ever end?). You bring up an interesting point about search. I had no idea the old search was so bad. |
|
|
|
|
LOL, I promise you the searching will be way better. Demo for you guys pretty soon.
|
|
|
|
|
Just wanted to drop in and say that I personally know one of the members of this project, and he's a sharp guy. I met him twelve years ago at a programming conference and we've kept in touch since. This is an exciting project which could be very transformative for trading, and I wish him the best of luck.
Edit: he can post images now.
|
|
|
|
|
Fixed it. Sorry about that. There are branches being merged in. I will completely be honest that we are untangling some things at the moment. Thanks for being patient guys!
|
|
|
|
|
Thank you for your support and I urge you to point out anything you'd like addressed!
|
|
|
|
|
Thanks for your enthusiasm and the information for others in this post (although the question mark in the title is a bit misleading).
|
|
|
|
We'll be providing more of a schedule moving forward. There are a lot of things to do at the time. If you pay attention to our github history, you can see that we have work in many branches happening at the same time and also contributions from a few folks. Commit history: https://github.com/epochtalk/epochtalk/commits/masterOther projects: https://github.com/epochtalkWe take privacy very seriously and we're engaged in a huge migration project for this forum. Although working with Theymos hasn't been the fastest, we're trying to ensure that everything is done correctly. There are also a few things regarding the privacy of this forum that we can't put in public repositories. (These are in private repos.) There are 2-3 sections we'll push to the beta first. We'll have a clearer schedule for this in the upcoming week. Sorry for the lack of updates. Will do better moving forward. |
|
|
|
Not sure if this has been discussed before but are you accepting any pull requests at the moment ? I can write end to end tests with jasmine and cross verify if the things are working as they should be.In case of a feature request or a bug,it would only make sense to write code if you're accepting requests..
Yes we are. It'd be great if you're open to contribute! There's also a developer slack. Please contact me on Github if you would like access. |
|
|
|
|
Sorry about this sorting out data migration issues. Will update when finished.
|
|
|
|
|
