miwilc

@Bailey no, that's not the issue, it's the custom code written for this forum.

Ah. That makes sense. Too bad I guess.

@craigwil you need to either give a small donation (anything above $1) and request a transfer to your preferred server.

 

Or backup and delete your current account and then sign up for your preferred server when registration is open (midnight UTC I believe.)

EDIT: This a reply to this post: https://www.helionet.org/index/index.php?app=forums&module=post&section=post&do=reply_post&f=13&t=30725&qpid=138571 I need to start checking the last post.

 

EDIT #2: If we running IPB v3 we can still merge into MyBB mentioned below.

-- #3: The current custom theme doesn't matter, it won't be touch my the importer.

-- #4: The importer can be run outside of the main website, MyBB only needs the database.

--

@Krydos

@Bailey wants to upgrade the forum for more features, I think. (I believe it's probably more safer security wise to upgrade.)

 

If anyone is going through with this:

 

MyBB is basically the best customizable forum imo, phpBB tools/import all sucks. (Trust me I tried.)

 

This the MyBB importer: https://mybb.com/download/merge-system/

This is my recommended theme: https://community.mybb.com/mods.php?action=view&pid=165

 

The best way to go about this is my updating the current forum software to the minimum supported version and then merge it into MyBB.

 

I encourage everyone to try MyBB: https://mybb.com

--

 

I can try doing this on my local machine if the staff is interested. It should be simple for me if it's inside the minimum supported version of the merge tool.

Guessing it will look somthing like this: https://bailey.guru/.well-known/heliohost.bailey

No, it will have a .txt extension so that it's easy to semi automate, otherwise you got everything.

 

Yes we'd just manually verify. I can easily check that domain is (or at least was) registered to an account here, even if the DNS doesn't reflect that by looking in the account database. There is no way to prevent someone from having it added to an account here and actually hosted elsewhere though.

 

It is worth noting that we don't recommend CF unless it's absolutely necessary because it conflicts with a lot of things.

 

We'd need to manually verify dedicated ip users too, but those are few and far between.

CF doesn't conflict a whole lot with my site (thank flexible design ), and some stuff requires it.

 

I don't think there will be too many of these users

 

 

@Krydos as for verification, would a text file in <website>/.well-known/heliohost.txt suffice?

Sure, but only people using cloudflare (or something similar) would even need to do that. 99% of our accounts are on 1 of 3 IPs.

There is deflect.ca which is a non profit thing, supposed to be a alternative to CF.

But yes, I think most users will be on the main heliohost nameservers.

@Bailey you need to create .well-known/heliohost.txt file manually and enter something like

"================================================== ================

https://bailey.guru

-------------------------------------------------- ------------------

 

I hereby claim:

 

* I am an admin of https://bailey.guru

* I am Bailey (https://www.helionet.org/index/user/123463-bailey/) on Helionet

 

 

And finally, I am proving ownership by this host by posting or

appending to this document.

 

================================================== ================"

 

Refer to: https://miwilc.keybase.pub/.well-known/keybase.txt

 

@wolstech What if they are using cloudflare? Like I am on https://www.miwilc.com do we manually verify in that case?

 

@mrj yes, please use GitHub for development.

 

If you wish, I could mirror the repository on https://code.miwilc.com.

Can the size be reduced to the default?, like the badge sizes on shields.io

The IP is still blacklisted in some places

Server owners are required to take some steps to get the IP (65.19.141.67) delisted.

 

Delist Links:

http://blacklist.lashback.com/delist

http://www.barracudacentral.org/rbl/removal-request

http://spfbl.net/en/delist/

http://www.sorbs.net/faq/spamdb.shtml

Hmm.

Your current NS points to both namecheap and heliohost, this is not supported remove/disable the namecheap DNS (ref: image)

https://s10.postimg.org/675nil02x/Screenshot_20171226-105607.png

The heliohost NS is:

 

ns1.heliohost.org

ns2.heliohost.org

 

I recommend ordering namecheap staff to manually set the nameservers to ours or transfer out to a registrar like https://www.namesilo.com

 

 

@Krydos it appears that namecheap is disallowing the same IP for both nameservers, which is weird that they would completely disallow using NS servers for that. They should've just issued a warning.

It appears that Heliohost is not a part of the giving fund for some reason, could we apply for this? Since it would allow Helio to receive funds from participating companies like humble bundle with its fundraiser (https://www.humblebundle.com)

 

Heres the link: https://www.paypal.com/us/givingfund/

Is there support for bcash?

@mrj I don't recommend using PHP here since it is probably a security risk.. and probably slow.

 

I recommend using plain HTML.

 

@Krydos as for verification, would a text file in <website>/.well-known/heliohost.txt suffice?

Merry Christmas! 🎉

-1 This is bad for SEO for any website associated with this.

 

It's better to organically grow your website via Reddit/social media imo.

 

If you have a audience they most likely don't care about other unrelated websites.

 

We do have a thread for sharing websites as @Krydos mentioned.

 

https://www.helionet.org/index/topic/58-websites/

See: https://stackoverflow.com/a/15168033

 

Generally, mod_deflate is easier to configure than mod_gzip.

 

You don't even need high compression if you have a Cloudflare account, they do minification via CDN and other things.

I just ran across this on Reddit, it appears to be proven real.

 

https://www.reddit.com/r/Bitcoin/comments/7jj0oa/im_donating_5057_btc_to_charitable_causes/

 

The tr;Dr is they are donating ~$86 million in BTC to charities and nonprofits.

 

I was wondering if heliohost could apply for this, I'm sure even a small donation from the fund would help the service greatly .

 

The website is at https://pineapplefund.org, they have a form to apply from.

 

From what I could gather from Reddit, they were looking for smaller organizations to donate to.

@Bailey too many... Maybe small "wiki news" subforum in https://www.helionet.org/index/forum/1-news/ so we don't clutter the News forum.

 

Wiki users can post in https://www.helionet.org/index/forum/5-other-discussion/

Is it possible to sort out who will keep the wiki up-to-date over at https://wiki.helionet.org or will one of the admins do it?

Yeah, I'd like to add my name to that list (if the admins don't want to maintain the wiki.) as a wiki maintainer.

 

I assume we'll be given access to separate SFTP accounts as wiki maintainer(s?).

 

Also, if we are going to do this, how are our activities to be audited, and where do we post changes/maintainence task updates(a.k.a downtime announcements.)

 

Is there a reason we can't just link to an external image like we can now?

 

I think it's missing HTML tag plugin but I can't add that yet as I'm out...

toomanyplugins.club

 

It is a option disabled by mediawiki by default

I assume you mean "need to be embedded"...some of those can't be embedded/stored as part of the wiki since they're actually PHP scripts that output image data (server load images).

 

Is there a reason we can't just link to an external image like we can now?

I meant directly embed*, I sentenced that wrong.

 

I believe that direct/(RAW) images is disabled for security reasons.

 

https://m.mediawiki.org/wiki/Manual:$wgAllowExternalImages#Why_disallow_external_images.3F

It is sftp not FTP.

It doesn't break things if you use it properly... and no, it's not being moved to /wiki/$1 because Krydos requests it how it is. Read up a few posts to see what he said about it.

 

It may not work when we go back, as there imbedded it should work fine. I'll have a look anyway, and it is a priority as we can't move it back wishing that it will be fixed!

I know that I requested /$1 but directly modifying .htaccess is always a bad idea, I know this for a fact. And I still believe you can change the title path in the MW settings. If that's impossible we can move /$1 to /wiki/$1 to maintain backwards compatibility.

 

I can't explain this better than that.

Also to clarify Krydos said we need /$1 to avoid search engine/links breaking, my solution clears all of that, if you can't modify the title in settings.

 

About the external images: yeah, it will need to be embedded.

@wolstech it _should_ be fixed once we move it back to the main domain.

 

Edit: Nvm, it appears to bad shortcodes, @OP should be able to fix.

 

Edit #2: uploaded Images on the old wiki will have to be copyed to the new wiki, not really a priority since it will be fixed once we moved.

@OP you can use the dos2unix program (on Linux, maybe cygwin) or some option in sublime text3 to convert to utf8.

Hmm. Will there be a more strict checking for badly written programs then?

 

I can see the advantages of this but the abuse can ruin the server. 🤔