Recommended Posts

I can't seem to upload images any more atm. It upload images perfectly but when I want to open the url it gives me the "Error" page :s

That is/was a problem with localhostr itself, I tried via the normal website and it does the same thing, report it uploaded ok but not give a URL.

Alright, just though I'd give you a heads-up about it :) I also tried it later on with the website uploader and just like you, it gave me the error page.

Now everything is working like it's supposed to :)

Thanks for the updates Mike, the new uploadr site looks great, I'm loving the new icon too.

Cheers :)

Thanks, although mail designed both so I can't really take the credit :p This version should have fixed the 'randomly turning white' bug so let me know if it does/doesn't.

I'm getting an error message whenever I try to upload something.

I wonder of you could add a feature to save the captured images to desktop besides uploading them. Would be really neat specially images with transparency support.

Thanks, although mail designed both so I can't really take the credit :p This version should have fixed the 'randomly turning white' bug so let me know if it does/doesn't.

I somehow forgot to mention it here, but the white rectangle problem stopped when I did a clean install of version 1.1.1 :)

I somehow forgot to mention it here, but the white rectangle problem stopped when I did a clean install of version 1.1.1 :)

Ah well, it was partially a bug with the app (I think) but it was because it was being sent a message it shouldn't be sent, but I sent a beta version to Radish and it stopped so it shouldn't appear again.

Ah well, it was partially a bug with the app (I think) but it was because it was being sent a message it shouldn't be sent, but I sent a beta version to Radish and it stopped so it shouldn't appear again.

Good to know! A bit off-topic, but what is mEdit? I saw it on your site and the idea of a good minimal editor sounds interesting.

EDIT: oops, looks like it's no longer there lol. Canceled perhaps?

  • 1 month later...
  • 2 weeks later...

Just to let people know, localhostr.com has had an update which also introduced a new API and so the current version (1.2.0) of localhostr uploadr has stopped working. I'll be releasing 1.2.1 in the very near future and I'll post here when it's released.

As the app only checks every 24 hours (at most) you may not see the update straight away. You can do 2 things, either remove the "lastupdatecheck" line from the config (%appdata%\localhostr uploadr\localhostr.conf) or manually download the new version from the site.

Finally, starting today I'll be using Twitter to make announcements on localhostr uploadr (will probably keep posting in this thread too). The Twitter feed is strictly for localhostr uploadr and is at http://twitter.com/uploadr

Ok, 1.2.1 has been released. As I said in the post above, it'll update within 24hours or you can edit the config* and remove the "lastupdatecheck" line and re-run it and it'll force a check for a new version and update. The only change is compatibility with the new localhostr API.

*: config is either %appdata%\localhostr uploadr\localhostr.conf or in the portable directory.

You can of course also re-download it from the website and re-run the installer which will update it for you.

I'm getting an error message whenever I try to upload something.

I wonder of you could add a feature to save the captured images to desktop besides uploading them. Would be really neat specially images with transparency support.

There's a hidden feature in the preferences that allows you to run a command on the temporary file the uploadr makes, I use it to correct the colours in the captured image and copy them to a sub folder of the program directory.

It's adv_command or something, I wrote a batch file to make it a bit easier.

I'd like to try this, but how does one get a localhostr account? They have a pretty website, but no registration link :(

Edit: Nevermind. Invite-only. Bah.

Edited by Darrian
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Wonder what MPs have ties to these privacy/verification/data harvesting companies that are going to step in this time. Last time under the Tories half the cabinet had fingers in the pies, heck even the PM and his wife at the time was working for silicon valley, probably made a fortune.
    • Google Chrome is killing all uBlock Origin bypasses, Microsoft Edge, Opera to follow by Sayan Sen For a while now the transition away from Manifest V2 (MV2) to MV3 has been on-going and it looks like it is entering its final phase of deprecation, at least, in the case of Google Chrome. A recent discussion thread in the w3c WebExtensions Community Group GitHub repo has highlighted how the latest and upcoming versions of the most popular browser are expected to be its final releases with support for MV2 extensions. Chromium contributor Andrey Bershanskiy shared details about recent Chromium changes and according to comments from Google engineer Devlin Cronin, Chrome has now started removing the flags that previously controlled MV2 availability. kExtensionManifestV2Disabled, the Chromium feature flag that allowed controlled disabling of MV2 add-ons, is now completely removed, which means you will likely no longer find uBlock Origin in your browser extensions list. He wrote: "The kExtensionManifestV2Disabled feature has been default-enabled for over a year. Remove the feature and the effectively-dead code. ... Any tests that relied on being in the "warning" phase (i.e., with the kExtensionManifestV2Disabled) for their sole behavior testing are removed, since this stage is no longer reachable." Cronin further explained why MV2 extensions are no longer allowed in supported Chrome versions as maintaining the associated functionality indefinitely is no longer possible. He cited growing technical difficulties and implementation complexities as well as security concerns. He wrote: "MV2 extensions are no longer allowed in any supported version of Chrome, and we are removing support for them and the associated functionality. We won't be able to provide / maintain this functionality indefinitely due to the complexity and tech debt, as well as the security risks it entails (we've actually found a number of bugs that are specific to MV2 lately). Of course, other browsers can continue supporting these if they so desire. Unfortunately, we won't be putting code behind a compilation flag ... We won't be removing all the MV2 code wholesale right away, so many of these things will continue working for awhile (but they will go away eventually, and some may go away sooner than others)." What this essentially means is that the tricks and bypasses that were used to keep MV2 extensions like uBlock Origin and others alive will not work any more on Chrome, or at least not for very long. For example the Windows Registry mod that could extend MV2 availability will cease to function after Chromium version 151. Here is a rundown of the changes coming in the final such releases of Chromium releases: Chromium 150 lost ExtensionManifestV2Disabled option Chromium 151 will loose ExtensionManifestV2Unsupported option Chromium 151 will loose ExtensionManifestV2Availability option Chromium 151 will likely loose AllowLegacyMV2Extensions option Other Chromium-based browsers like Opera and Microsoft Edge could soon follow suit too. Although it is not specified, Edge began disabling uBlock Origin back in February, and Opera could also stop the functioning of MV2 add-ons, even though it had committed to support MV2 for longer in October 2024. uBlock Origin developer Raymond Hill (gorhill) apparently stated the following: "For Opera I did submit 1.70.0 rather late, but this was weeks ago. A while ago I received an email from Opera that they plan to abandon MV2-based extension so maybe they are no longer allocating resources for reviewing such extensions." The email which developers like Gorhill mentions was received from Opera last year. Here is what it seemingly said: Hence for now the only Chromium browser that seems to be on-board fully with MV2 support is Brave, and perhaps Vivaldi as well. Meanwhile if you want to ditch Chromium browsers entirely then Mozilla Firefox is an excellent alternative as MV3 and MV2 are both supported. Of course the easiest solution is to switch to uBlock Origin Lite if you want to remain on Chrome, as it is MV3-based, but from our experience, uBO Lite does not seem to be as good as the original non-Lite version. Source: w3C (GitHub repo) As an online publication, Neowin too relies on ads for operating costs and, if you use an ad blocker, we'd appreciate being whitelisted. In addition, we have an ad-free subscription for $28 a year, which is another way to show support!
    • Write to your MP 😄 Like believing in Santa. Total surveillance IS the goal. Wake up.
    • This whole dumb age verification thing needs to die and be replaced by giving parents tools to control devices. Why am I required to plaster my ID all over the internet to prove I'm old enough when parents should be the ones dictating what their kids are doing on their phones. Apple released great set of tools for iPhones coming to iOS 27 that do just that. Why are governments not mandating that kind of control to phone makers to built them into phones. This whole thing is so absolutely idiotic it's wild.
  • Recent Achievements

    • Very Popular
      Captain_Eric earned a badge
      Very Popular
    • One Month Later
      amusc earned a badge
      One Month Later
    • One Month Later
      DJC50PLUS earned a badge
      One Month Later
    • Week One Done
      DJC50PLUS earned a badge
      Week One Done
    • Proficient
      Eric Biran went up a rank
      Proficient
  • Popular Contributors

    1. 1
      +primortal
      511
    2. 2
      PsYcHoKiLLa
      220
    3. 3
      ATLien_0
      92
    4. 4
      +Edouard
      90
    5. 5
      Steven P.
      83
  • Tell a friend

    Love Neowin? Tell a friend!