Topic: Slimcoin | First Proof of Burn currency | Decentralized Web - page 70. (Read 137076 times)

I will most likely change it the way that only "ARM" stays in the menu, so the menu point doesn't become too long.
Another idea would be to directly include a download page, like most software projects have. There, we would not have any restrictions. We could then also link the "get wallet" section to it.
You are totally right - I will change it.

@muf18, you're right, the mobile menu is still flawed, that should be easy to correct for me - most likely I will create a new category "mobile" for pages so only a couple of selected pages get included there. I will also have to cleanup the code a bit - I wrote it so that the HTML structure is easily readable, but that means that one either will have to include lots of HTML comments or misalignments. I think ksdme meant the misalignment between "Slimcoin Home" and the rest of the menu bar, right? I'll look into it.

I've abandoned the plan to include flags after I read a bit about that problem, mainly at http://flagsarenotlanguages.com. They're totally right. I like the integration of the Language Icon in the Peercoin website (peercoin.net), maybe we can do it that way (by the way, I like the Peercoin website design very much, it's clean, rich and modern and not at all "shitcoiny-looking".). Unfortunately, I haven't found that icon at the Semantic UI website, so most likely it would have to be included manually - if I didn't overlook something.

I also would love the integration of the old slimcoin.club features, but yes, the JS files managing that would have to be connected to a node or an external block explorer.

I'd be tempted to replace the BrainWallet code with the more complete (https://github.com/bip32/bip32.github.io, rendered as http://bip32.org) were it not for the fact that most people have migrated to the far more comprehensive “Mnemonic Code Converter” by Ian Coleman - https://iancoleman.io/bip39/, which is what “brainwallets” evolved into ...

First click the “Generate” button (15 words is okay) then choose either “Slimcoin” or “Slimcoin testnet” from the “Coin” dropdown menu (form field #4) - I worked out a set of extended key generation bytes specific to Slimcoin (not widespread knowledge, check out the other coin selections listed in the dropdown and bask in Slimcoin's technical excellence).

The UX is appalling, though and I anticipate little actual use. I severely doubt that none other than a handful of cryptoscenti will have much understanding of how to use extended keys. The feature will still come in handy later, properly insulated and made safe to use.

Cheers

Graham

My educated guess is that you are using a port other than the default (or that networking local to you is).

I have three slimcoin nodes running on the server, a funded slimcoin node linked against the distro's bdb (5, IIRC) and two nodes (1 x each mainnet and testnet) running empty wallets linked against BDB 4.8 (to support the creation of mainnet and testnet datadir snapshots). The mainnet runs off've the default port and that shows up (DE), ditto for testnet. The funded node runs off've a non-default port and doesn't show up in getpeerinfo. Occasionally, you'll see a (GB) in the ACME list - that's the node I sometimes run locally on the old laptop - using the default port.

Cheers

Graham

Welcome to BDB 4.8, vintage Sept 2009. The subsequent later Bitcoin upgrade to use leveldb was in pursuit of faster indexing, I believe.You might get some speed-up in indexing from linking against a newer version of BDB for your architecture, if you haven't already - for backward compatibility of wallets, OS X and Windows binaries are linked against BDB 4.8. Collating your UTXO to a single tx to a single addy might help. I did that and CPU thread use dropped from 99% to 16%. If you hold a large proportion of your current UTXO set as small stake reward txs, it's probably worth collating them on a quarterly schedule.

I've come to see the delay as a feature that, in effect, provides a counterbalance to PoS-1.0's over-weighting of staking for long-unseen wallets and which doesn't affect those users who host a permanently-connected node. The ACME/web2web publishing thing (to which I will return in the New Year) could well provide a greater incentive to keep a node online.

Cheers

Graham

Graham we see benefit, but we just didn't have any node and skills to make this. If it's possible revitalizing these features, they were great. We just didn't know how to make them work, thus I thought about cutting them off, and I have done that.
Also I think, that they could be on another subpage maybe, not on the main site, cause it would bloat main website a little. But I'm 100% for returing original content. Calculator isn't so hard to return, but brain wallet, block explorer, and mining in browser (that was fun, but not efficient at all, so maybe not) needed connecting to node or as you said maybe connect to api of ACME.
Btw. - how are going with ACME? It's a little strange that, I'm connected to Slimcoin network, almost all the time as a node or node+miner, and I don't see my ip-address and country on ACME node listing . And how is going with web2web?

At least nova shouldn't close, so on February, we should see trading going live ones again.

I've been dumping likely-relevant content into the master README.md:

https://github.com/slimcoin-project/Slimcoin/blob/master/README.md

It's due to get edited and published as a resource in docs so feel free to copy any of it over to a web site/blog post/whatever.

I take it that no-one sees any benefit in revitalising the original features such as the in-browser block explorer (I could adjust the Slimcoin ACME to respond to the API calls) or the mining-SLM-in-the-browser? And ditto for the other disabled features in the “Brainwallet” section?

Cheers

Graham

Yeah, I thought similar. So we should leave, as it's now, just replace placeholders, with real content, and that should be it.

I'm still wondering is there any way, to make loading times faster of a wallet. It's sometimes annoying, because loading times are the ones, most obvious issues, rest is good.
On SSD it's rather good (below 1 minute), but on HDD it can take up to 20 minutes.

A predictable namespace collision, guaranteed by ISO 3166-1 vs ISO 639.

The only way out is the right one, use the language string itself and give visually-impaired people a break.

Cheers

Graham

@redacted - that's going to change this month with new website, as you can see, it's quite modern, and fresh looking.

Btw. - I have sent request for adding us to coinsmarket.com and stocks.exchange
@ksdme said about minor flaws to the website design - misaligned menu and red tickers of SLM (no need for now), also mobile menu is overflowing, because text is too long. But it's a minor and easy to repair inconviences.

About flags - it's a nice touch, but I don't know if necessary, because obviously issue with US/UK flag.

Although the team is really operative, I always cautiously concern with projects that don't pay much attention to their lending page

Hello d5000,


Great work, looks good. Just a couple of minor points. Firstly, downloads for ARM should also include V8(aarch64). Secondly, I would suggest making the wallet dowload section slightly different so that "code" and "compiled binary" appear in the same order as the links below them.

Regards

Looks great .
After introduction of new website, I'll try to make some noise in social media.

The website prototype with Jekyll is now ready for testing:

https://d5000.github.io/slimcoin-website-project/

The only unsolved problem, for me, is the big header I mentioned earlier (on the content/help pages). Also, I think it was a good idea to split the About page into smaller pages (besides the Cooperation page, there could be a "Features/Specifications" page) because it's quite long.

Ah, and the flags would be nice still. I'll later look at it, should not be too hard.

https://en.bitcoin.it/wiki/Proof_of_burn#Slimcoin

May anyone explain, how occur selection of PoB miner, who produced the block. Ok, i read that every PoB miner have a burned coin, and have a probability create new block. But who determine that exactly that miner block is necessary add in blockchain. How random is worked? And is there real?
Ok, i understand. Between two PoB blocks follow one PoW block and its like a timer. And randomeless is a number of total burned coins

I've seen it. ksdme replaced JavaScript files and images with smaller/minified versions. That is very easy to update.

It cannot be automatically merged, however, because I changed the file structure (but manually it's easy as I said). Each page, like in the current slimco.in version, includes three HTML files (in the _includes folder): head (HTML head, with the links to stylesheets etc.), header (menu bar), and footer; with the content placed between header and footer (obviously). The design of the content section is managed by the files in the _layout folder (default.html and page.html, post.html is currently not used.). That's where I still need to make changes because the content pages still don't look good.

index.html in my version does only include the content section of the front page (the part with the wallets etc.).

Edit: I now included ksdme's minified/compressed files. In the next days I'll look at the sub-page design and the new categories. If you want to change something more on your/ksdme's design and don't want to bother with the - more complicated - Jekyll site structure, there is no problem if you do it in your own static repository, just advise me when it's ready and I'll port it.

New files for Slimcoin:

Ubuntu compilation X64 from master tree (Slimcoin v.0.5.1 for Ubuntu X64, please test, it's a test compiliation, but should work):

https://mega.nz/#!Un4UzBQB!WhJyO3VKN0UQMQca5n9qDLmrZVlzuoRleuBVJ6gk5K4

Windows executable newest version (minikiz is dead):

https://mega.nz/#!xuRDDTRJ!ObrsY4qASZOkHICkieLncq1wq8mPI1vyG290PdRbwPM

Snapshot from 10.12.2017r.

https://mega.nz/#!QnxkwTbK!et6c6zINNHuGAgU1wqil5fw_oxOyek2Zv_MWl2x8XT4

Slimcoin Client AIO Project with v.0.5.1 and 10.12.2017r. blockchain (please, try it, I can't test it, because I can't have virtual machine right now)

https://mega.nz/#!k64GiRYT!_WG8Ew1sccV_Eit1UHwAJPcQsrLoQ7kl_P8M3FvcicY

The potential of this project is very good, coupled with a team that has great ability (judging by how the team answers all the questions in this forum)

You didn't pull changes, that @ksdme, have submitted, before changing files? I think it was a few substantial changes, with optimalization and other important things.

Just realized that slim can gain a lot.. It is only on novaexchange and there is no deposit option. People can't dump and most big players have taken coins off the exchange because they can mine. I don't like pump and dumps but a price increase would cause more people to be aware of the project. Wish I still had some btc on nova haha.