Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Hyperspace

hypercritical.co

Post reply on HN
Print view View original

481–490 of 503 posts

Re: Hyperspace

#481

Post by [deleted] »

cmckn wrote: post #434
0x0203 wrote: post #413

Earlier quoted context omitted.

Absolutely no judgement for however people want to licence and distribute their software, but I've seen the support burden used as justification for closed source/selling software quite a bit recently, and wonder how often people might be conflating open source with open development. There's no reason an open source project has to accept bug reports or pull requests from anyone. See SQLite or many of the tools from F…

Didn’t SQLite developer(s) famously receive a flood of phone calls because McAfee antivirus used it in a way that was visible (and “suspicious”) to its users? One does not simply “not accept bug reports”. https://github.com/sqlite/sqlite/blob/e8346d0a889c89ec8a78e6...

[deleted]

Re: Hyperspace

#482

Post by cxr »

notatallshaw wrote: post #458
wubrr wrote: post #446

Earlier quoted context omitted.

> he doesn't want to deal with thousands of support requests when making his apps open source and free. Who says you have to deal with support requests if you open source something? > All his apps are personal itches he scratched and he sells them not to make a profit but to make the barrier of entry high enough to make user feedback manageable. That makes no sense

> Who says you have to deal with support requests if you open source something? Almost anyone who has ever maintained popular open-source software, even if dealing with them means putting up a notice that says "Don't ask support questions" and having to delete angrily posted issues. My understanding from listening to his explanation is he wants to be able to support users and have an income stream to incentivize that…

> issues

So GitHub created a mess, and the whole of open source is considered to be GitHub now.

The solution is the same as being able to avoid tons of Windows-related headaches when you don't use Windows. Just don't use GitHub.

A tar or zip file with source code posted online (or bundled with the program, even) under an open source license is still open source.

Re: Hyperspace

#483

Post by cxr »

least wrote: post #479
karparov wrote: post #466

Earlier quoted context omitted.

I still maintain that if that's the case then something is wrong. More users reporting bugs for relevant edge cases is not a nuisance, it's the crowdsourcing of testing and each such reported issue is gold because then he can fix it before he as a user of his own software runs into it. Assuming he actually uses the software. (I also do maintain a bunch of packages and I do use them daily.) Making software proprietary…

> why should I spend the time to for free report sth to somebody who is making money off my testing and doesn't even bother to be transparent about how things work exactly (i.e. the source)? You don’t have to. No one is saying you are compelled to report bugs in software you paid for. Most people don’t. The benefit to you as a customer is it can help get the bug fixed. That is clearly a mutual benefit. > If you reall…

You're vastly overestimating how the norms of GitHub are able to account for how things have to be. Recognizing that GitHub's userbase has a certain type of problem is no different than realizing that HN, Reddit, Tumblr, etc. all have their own respective userbases and each tends to behave in certain ways (desirable or not) that are characteristic to that group.

Re: Hyperspace

#484

Post by jonhohle »

gurjeet wrote: post #389
jonhohle wrote: post #341

I made a command line utility called `dedup` a while back to do the same thing. It has a dry-run mode, will “intelligently” choose the best clone source, understands hard links and other clones, preserves metadata, deals with HFS compressed files properly. It hasn’t destroyed any of my own data, but like any file system tool, use at your own risk. 0 - https://github.com/ttkb-oss/dedup

Thank you for creating and sharing this utility. I ran it over my Postgres development directories that have almost identical files. It saved me about 1.7GB. The project doesn't have any license associated with it. If you don't mind, can you please license this project with a license of your choice. As a gesture of thanks, I have attempted to improve the installation step slightly and have created this pull request:…

Thanks for the PR. Individual files were licensed, but I’ve also added a LICENSE file as well.

Re: Hyperspace

#485

Post by 620gelato »

borland wrote: post #158
astennumero wrote: post #149

What algorithm does the application use to figure out if two files are identical? There's a lot of interesting algorithms out there. Hashes, bit by bit comparison etc. But these techniques have their own disadvantages. What is the best way to do this for a large amount of files?

I don't know exactly what Siracusa is doing here, but I can take an educated guess: For each candidate file, you need some "key" that you can use to check if another candidate file is the same. There can be millions of files so the key needs to be small and quick to generate, but at the same time we don't want any false positives. The obvious answer today is a SHA256 hash of the file's contents; It's very fast, not t…

Oh the sha-256 hashes are precisely what I used for a quick script I put together to parse through various backups of my work laptop in different places (tool changes and laziness). I had 10 different backups going back 4 years, and I wanted to make sure I - 1) preserved all unique files, 2) preserve the latest folder structure they showed up in.

Using sha256 was a no-brainer, at least for me.

Re: Hyperspace

#486

Post by unclebucknasty »

pornel wrote: post #455
unclebucknasty wrote: post #271

Earlier quoted context omitted.

> which is probably really unique Wonder what the distribution is here, on average? I know certain file types tend to cluster in specific ranges. > maybe it’s better to just compare byte by byte? You’ll have to read the whole file to generate the hash Definitely, for comparing any two files. But, if you're searching for duplicates across the entire disk, then you're theoretically checking each file multiple times, an…

> exceedingly rare To have a mere one in a billion chance of getting a SHA-256 collision, you'd need to spend 160 million times more energy than the total annual energy production on our planet (and that's assuming our best bitcoin mining efficiency, actual file hashing needs way more energy). The probability of a collision is so astronomically small, that if your computer ever observed a SHA-256 collision, it would…

You know, I've been hearing people warn of handling potential collisions for years and knew the odds were negligible, but never really delved into it in any practical sense.

Context is everything.

Re: Hyperspace

#487

Post by OnlyMortal »

UltraSane wrote: post #245
amzin wrote: post #146

Earlier quoted context omitted.

Is there a FS that keeps only diffs in clone files? It would be neat

VAST storage does something like this. Unlike how most storage arrays identify the same block by hash and only store it once VAST uses a content aware hash so hashes of similar blocks are also similar. They store a reference block for each unique hash and then when new data comes in and is hashed the most similar block is used to create byte level deltas against. In practice this works extremely well. https://www.vas…

That’s very interesting. Typically a Rabin fingerprint is used to identify identical chunks of data.

Identifying similar blocks and, maybe sub-rechunking isn’t something I’ve ever considered.

Re: Hyperspace

#488

Post by least »

cxr wrote: post #483
least wrote: post #479

Earlier quoted context omitted.

> why should I spend the time to for free report sth to somebody who is making money off my testing and doesn't even bother to be transparent about how things work exactly (i.e. the source)? You don’t have to. No one is saying you are compelled to report bugs in software you paid for. Most people don’t. The benefit to you as a customer is it can help get the bug fixed. That is clearly a mutual benefit. > If you reall…

You're vastly overestimating how the norms of GitHub are able to account for how things have to be. Recognizing that GitHub's userbase has a certain type of problem is no different than realizing that HN, Reddit, Tumblr, etc. all have their own respective userbases and each tends to behave in certain ways (desirable or not) that are characteristic to that group.

It's not about the meta-characteristics of a user base. By allowing anyone to create issues, you are creating additional noise. Even if the signal to noise ratio were to be higher, you're still increasing total noise.

There are limits to how practical it is to allow for more and more feedback and that threshold for a solo developer is quite low. Restricting your user base by charging for your work means that there is less noise because the only people sending bug reports are paid users.

The quality of these reports are probably lower than if you had an open issue tracker, but you are substantially reducing the mental overhead and you know the people that are sending feedback are doing so with their own interests in mind.

Re: Hyperspace

#489

Post by cxr »

least wrote: post #488
cxr wrote: post #483

Earlier quoted context omitted.

You're vastly overestimating how the norms of GitHub are able to account for how things have to be. Recognizing that GitHub's userbase has a certain type of problem is no different than realizing that HN, Reddit, Tumblr, etc. all have their own respective userbases and each tends to behave in certain ways (desirable or not) that are characteristic to that group.

It's not about the meta-characteristics of a user base. By allowing anyone to create issues, you are creating additional noise. Even if the signal to noise ratio were to be higher, you're still increasing total noise. There are limits to how practical it is to allow for more and more feedback and that threshold for a solo developer is quite low. Restricting your user base by charging for your work means that there is…

At any given time when I'm at a restaurant or grocery store, there's more food around and on the menu than the threshold for how much food that I as a single person can eat.

Re: Hyperspace

#490

Post by karparov »

crowselect wrote: post #472
karparov wrote: post #395

Earlier quoted context omitted.

I'm a little surprised that folks here are investing so much time into this app. It's closed source, only available for a non-obious amount, time-limited or subscription-based and lots of details of how it works are missing. With a FOSS project this would have been expected, but with a ShareWare-style model? Idk..

Non obvious amount? Scroll to the bottom of the app store page, all the in app purchase prices are listed there. App store prices are localized. If the blog post said it costs “$10” or whatever, that doesn’t mean anything to millions of potential customers who live where they don’t use $, and is confusing for millions more that do use $ but don’t know if the price is in their local $ or USD

If I want to create an entry in Apples DB that I looked at this app, then sure, it's easy to find out.

The local currency argument is wrong btw. I'm located in Europe and use a Spanish IP. The prices shown are in USD.

There are lots of apps called "Hyperspace" in the Apple app store, by the way.

https://apps.apple.com/us/app/hyperspace-lighting/id15371988...

https://apps.apple.com/us/app/hyperspace-gpt-chats-ai-art/id...

...

Post reply on HN