Ruskiwaffle1991
New member
Is it just me or I can't download things from OHM?
It is httpsChange thehttp
part of the URL tohttps
if one found.
@dbeachy1 are you aware of this?The only problem is that it seems I can't download anything off it. Yeah, unavailable file (although it sees its size). And a weird XML message if I actually try to download anything off it. I think the only real risk is losing the database. Many have their personal backups as well, but some aren't in the community anymore, either by choice or for physical reasons. Doug's page redirects to asian pr0n, and I'm quite sure it's not the browser at fault.
It's probably my fault, related to a change I made yesterday ahead of taking an export. Apologies! I'll take a look at it.Yep, confirmed :
XML:<Error> <Code>NoSuchKey</Code> <BucketName>ohm</BucketName> <RequestId>blah blah blah</RequestId> <HostId>blah-blah</HostId> </Error>
Wow, that sounds like some waaay oversensitive code...this was as I suspected something I broke by looking at the code funny
Well, yes but also no. The API platform is written in Rust, using a framework called Rocket, which was pretty new at the time and required a nightly build of the rust toolchain to compile it. That kind of bleeding edge development is fine while you're keeping pace with it, but since I haven't looked at it in a while the underlying platform has moved quite a long way ahead of where my code is at, and I took a shortcut that didn't pay off in order to get things done.Wow, that sounds like some waaay oversensitive code...
using a framework called Rocket
And to add to this; we’ve developed a little web service that will redirect old OHM links to the new resource location.The preliminary work for the migration has now been completed, and as such we're ready to merge OHM into OF, which will take place in the maintenance window announced for Sunday night (see the notice). The forum will be closed just for data consistency as the import is effectively three large SQL queries, so I'd like to ensure we have exclusive access to the database at that time to avoid any concurrency issues.
The add-ons that we can map to an OF user will be owned directly by that user. This means that you'll have full control over the add-on once it's turned into a Resource here, including changing the description and releasing new versions, and so on.
Those add-ons we can't map to an OF user will be owned by a catch-all "Unknown OHM Addon Dev" user. In testing this accounted for a reasonable amount of add-ons, which isn't ideal, but is a facet of OHM having had its own distinct authentication system for much of its life. Those add-ons can be claimed by their author if the author so desires; we'll make a process for this to be done, so that content creators of older add-ons can provide updates and own their content.
The import is a compromise, and the resultant resource is passable, but does not take advantage of many of the improvements we can utilise by having the add-ons in the forum site directly. New, or updated add-ons, will be able to benefit fully from these improvements.
I'll produce some guidance on how to use the system at some point, but for the most part I hope it's pretty intuitive.