Hacker Newsnew | past | comments | ask | show | jobs | submit | more codingpanic's commentslogin

Thanks for the feedback, I'll work on fixing this. Alternatively, you can also open an issue here: https://github.com/gnormandin/Archive-Page/issues


New build submitted.


I don’t see any changes on the repo. The permissions in your case should just be activeTab and storage. That’s it.

You can run the extension via chrome.browserAction.onClick and it will receive the URL. You also don’t need the tabs permission just to create a tab.


The issue is that if you do not set permissions in the manifest, clicking allow in the safari UI would only return a blank URI, "". The original extension in this case would also just return an error.

I've modified the manifest so that it is asking Safari for wider permissions, so that when the permission is granted by the user, the proper URL is returned.


I think that’s a Safari bug with activeTab, you just have to click twice.

Regardless, with activeTab you can just inject script into the page itself through which you can open a regular popup.

    chrome.scripting.executeScript({
      func: () => window.open(' archive.ph' + location.href)
    })
Currently the extension will suggest that it needs access to every page the user visits, occasionally opening a popup automatically if I remember correctly.

For something that’s a glorified bookmarklet, that’s a lot to ask.


Apple has some SSL export restrictions I've yet to successfully navigate. Will have this fixed in the next version.


Thanks!


New build has been approved and the extension is now in France.


This should be the expected behavior when pressing the button on a new Safari tab. Otherwise, should redirect to the URL your current open tab is displaying.


Then something in the UX is broken. From your store images, I understood that clicking on that tab menu item, it would display last archive date and ask to rearchive, no?

There is a reason why most Safari extensions apps do not just show an icon and a label, but actually explain how to use their embedded extensions.


The extension is open source, I'm open to new ideas on how to improve this further. The current Edge/Firefox extensions just error out, and this was not acceptable for this version of the extension per the AppStore rules.

You can make any suggestions here: https://github.com/gnormandin/Archive-Page/issues


Yeah, there should be two redirects. The first is searching for the URL you entered, the second should either newly cache the page, or load the cached page. Same behavior as firefox.

If this is not what you are seeing, please open an issue on the github at: https://github.com/gnormandin/Archive-Page/issues

So I can keep track of issues encountered.

Thanks!


Ah, yep, changing the permissions from "Ask" to "Allow" is a workaround:

Settings > Safari > Extensions > Archive Page > All Websites > Allow


Issue fixed, and a new build has been submitted


Finally published my first anything on the Apple AppStore by porting the Archive.Today extension to Safari. Works on iPad, iPhone, and Mac.

I was tired of copying and pasting when I wanted to use the Archive service on HN articles, so here you go!


Congrats man, this should be useful!


Weird, I use cashapp as my daily debit card. Figure it reduces overall risk by only having a set amount available for use at any time.

If I need to spend more? I move it to cash app, then spend it.

My main checking and savings accounts do not even have cards that are active. Its all cash app all the time.

Not saying they aren't doing anything wrong, just that there are plenty of legitimate uses for the service.


I don't believe Hindenburg is claiming that 100% of all uses of Block is fraudulent. For any service, something between 0 and 100% of use case generally is fraud; their claim is that the actual percentage is much higher than what the public knows, and thus the market is overvaluing Block.


While I agree with andrewstuart, there are not many other boards with the community, developer support, and ecosystem backing that Rpi has. Unfortunately, they really put the work in early to make sure they were positioned well in the ARM SBC space. (The fact that you can run some workstation loads with 4 or 8GB of ram on Pi is a bonus)

I'm hoping with Risc-V boards coming out, that maybe the cycle can start new and someone else can build a similar community, but actually value them.


If you can make do with a microcontroller then the esp32 has excellent software.

Alternatively maybe buy ex business/government mini machines for less than $35 off eBay. Intel CPUs have better software than rpi.

https://www.ebay.com/itm/224882648354?hash=item345c0ce522:g:...


Did you read the description? That $35 computer you linked has "no memory, no cpu, no hard drive".


As far as buying cheap government computers goes... price is only one factor here. Formfactor and power use are huge wins with ARM SBCs.


Excellent! Cant wait to see what the performance is on M1 Max.

Just purchased and they sent me two keys... opened a ticket to let them know.


During the early access / beta period one of the keys might be for X-Plane 11. I think that's the deal.


I would have thought the second email would have stated "Xplane 11 key"?

Both say 12.


Hmm odd, not sure then. I'll take it, if it's not being used ;)

I had a look on where I read about the X-Plane 11 keys during the beta, it's here - https://developer.x-plane.com/2022/05/x-plane-12-development...


I've switched my main domain to iCloud, once they announced custom domains. It "just works" with the Apple devices I usually use for main domain stuff. If I do end up leaving Apple, this will likely get moved to another service.

I do have a few other domains I use for various tasks and testing, I've moved those to the free Zoho Tier for now. I'll keep an eye out if anything else comes up thats worth looking at. These work well with any device, and not just Apple ones.


Nouveau would likely want to remain a "cleanroom" project, with most of the functionality developed through good ol fashioned reverse-engineering. Incorporating anything from the leaked documentation would likely throw the project in legal jeopardy.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: