Homebrew [release] QR Web Installer (cia installer)

ksanislo

Well-Known Member
OP
Member
Joined
Feb 23, 2016
Messages
386
Trophies
0
Location
Seattle, WA
XP
512
Country
United States
"clone my project"? FYI, I coded the feature entirely from scratch, didn't even know of this, and had the idea proposed to me and looked into by another months ago.

Strange that you would say such, given that I started and demo'd this months ago, fixed ctrulib to allow streaming HTTP on files larger than system RAM, first implemented http based, and then callback based install in your citrus lib for this, and your initial code commit in fbi 2.1.0 looked like a near copy/paste from my codebase... but whatever you say.
 
D

Deleted User

Guest
Strange that you would say such, given that I started and demo'd this months ago, fixed ctrulib to allow streaming HTTP on files larger than system RAM, first implemented http based, and then callback based install in your citrus lib for this, and your initial code commit in fbi 2.1.0 looked like a near copy/paste from my codebase... but whatever you say.
I updated my post with a precise date, which by the way is before the date of the first post. Also, FBI 2.x doesn't use citrus anymore. Finally, how is this "near copy/paste from my codebase"? https://github.com/ksanislo/QRWebLoader/blob/master/source/camera.cpp vs https://github.com/Steveice10/FBI/blob/master/source/ui/section/task/capturecam.c
 

ksanislo

Well-Known Member
OP
Member
Joined
Feb 23, 2016
Messages
386
Trophies
0
Location
Seattle, WA
XP
512
Country
United States
I updated my post with a precise date, which by the way is before the date of the first post. Also, FBI 2.x doesn't use citrus anymore. Finally, how is this "near copy/paste from my codebase"? https://github.com/ksanislo/QRWebLoader/blob/master/source/camera.cpp vs https://github.com/Steveice10/FBI/blob/master/source/ui/section/task/capturecam.c

Copied from the FBI 2.0 fork I had made, which has been dropped off github since there was no point in keeping it after the release of 2.1.x and things were advancing too quickly to keep up.

This project has been going since January, I brought HTTP based direct install to the system, first merged by you into citrus here: https://github.com/Steveice10/citrus/pull/13

Oh, and here's where I pointed out you should even add a hook that would let you load a graphic image into FBI that wasn't from a file:
https://github.com/Steveice10/FBI/pull/49

Oh, and here's the merge that fixed httpc so you could actually download the .cia in pieces, since it wasn't actually possible before I started this:
https://github.com/smealum/ctrulib/pull/258

While I greatly appreciate your work, and actively encourage people to upgrade to FBI 2.2.1 instead of using this app anymore, it seems a bit dishonest to claim this was a unique and original idea which you implemented on your own...
 

spinda

New Member
Newbie
Joined
Dec 27, 2014
Messages
3
Trophies
0
Age
28
XP
84
Country
United States
Strange that you would say such, given that I started and demo'd this months ago, fixed ctrulib to allow streaming HTTP on files larger than system RAM, first implemented http based, and then callback based install in your citrus lib for this, and your initial code commit in fbi 2.1.0 looked like a near copy/paste from my codebase... but whatever you say.

I suggested the idea and built a prototype back on February 6. The FBI implementation comes from that, not your project, which began on February 22. To my knowledge, neither Steven nor I had heard of it beforehand.


kF4vFJj.png


X8t3f93.png



cP3Drkc.png
 
D

Deleted User

Guest
Copied from the FBI 2.0 fork I had made, which has been dropped off github since there was no point in keeping it after the release of 2.1.x and things were advancing too quickly to keep up.
What FBI 2.0 fork? I assure you I didn't know of such a thing, and that I implemented camera support on my own over several days of debugging.
This project has been going since January, I brought HTTP based direct install to the system, first merged by you into citrus here: https://github.com/Steveice10/citrus/pull/13
I didn't know of it, however, and I wouldn't automatically link the addition of HTTP support to the idea of QR-based CIA installation.
Oh, and here's where I pointed out you should even add a hook that would let you load a graphic image into FBI that wasn't from a file:
https://github.com/Steveice10/FBI/pull/49
I noted that, however it was long after I had already been presented with the idea, as I said.
Oh, and here's the merge that fixed httpc so you could actually download the .cia in pieces, since it wasn't actually possible before I started this:
https://github.com/smealum/ctrulib/pull/258
I appreciate your work fixing the issue in ctrulib, but this has no relation to coming up with the idea of QR code installation or the actual implementation in either application.
While I greatly appreciate your work, and actively encourage people to upgrade to FBI 2.2.1 instead of using this app anymore, it seems a bit dishonest to claim this was a unique and original idea which you implemented on your own...
I appreciate your work as well, and I'm not trying to claim it's unique or that I was the first to implement it. However, that doesn't change that the idea was suggested to me independently of this, long before I knew about it, and that none of your code was even referenced in implementing it into FBI. You certainly did some impressive work in fixing things up and implementing it well before I got around to it, along with the other contributions you've made to my own works, but I don't take kindly to people claiming that I stole their code.
 
Last edited by ,
  • Like
Reactions: Aurora Wright
D

Deleted User

Guest
Ok, just must be a misunderstanding. You both implemented qr in a unique and different fashion. If you guys worked together (Amazing dev and amazing dev) you could create something amazing!
 
  • Like
Reactions: spinda
D

Deleted User

Guest
Well, I linked third party verifiable, and required pieces required to implement this functionality. You provided easily photoshopped screen caps. Give me /something/ verifiable by a third party then.
That wasn't me, that was the other person I mentioned. Plus, I already linked to code which vastly differs between the two projects.
 

ksanislo

Well-Known Member
OP
Member
Joined
Feb 23, 2016
Messages
386
Trophies
0
Location
Seattle, WA
XP
512
Country
United States
That wasn't me, that was the other person I mentioned. Plus, I already linked to code which vastly differs between the two projects.

So, you haven't a single github commit that predates mine while you were implementing this? I'm not even asking for something _hard_. Just something that shows you didn't directly rip off my app.
 
D

Deleted User

Guest
So, you haven't a single github commit that predates mine while you were implementing this? I'm not even asking for something _hard_. Just something that shows you didn't directly rip off my app.
How exactly am I supposed to prove that the idea had already been suggested to me beyond screenshots from the other party from the moment they suggested and experimented with it? The fact that the code differ so vastly should be proof enough that it wasn't ripped from your app.
 

ksanislo

Well-Known Member
OP
Member
Joined
Feb 23, 2016
Messages
386
Trophies
0
Location
Seattle, WA
XP
512
Country
United States
How exactly am I supposed to prove that the idea had already been suggested to me beyond screenshots from the other party from the moment they suggested and experimented with it? The fact that the code differ so vastly should be proof enough that it wasn't ripped from your app.
So no then? Not a single commit showing you even attempted a web based or we based install before well after this was public?

I'll deal with probable code copying next, this is about general concept and implementation to start with.
 
D

Deleted User

Guest
So no then? Not a single commit showing you even attempted a web based or we based install before well after this was public?

I'll deal with probable code copying next, this is about general concept and implementation to start with.
No, as when the idea was suggested, I was still in the middle of rewriting for FBI 2.0. I never got around to it until up to a week before I committed it.
 

spinda

New Member
Newbie
Joined
Dec 27, 2014
Messages
3
Trophies
0
Age
28
XP
84
Country
United States
Last edited by spinda,

capito27

Well-Known Member
Member
Joined
Jan 19, 2015
Messages
874
Trophies
0
XP
1,230
Country
Swaziland
So no then? Not a single commit showing you even attempted a web based or we based install before well after this was public?

I'll deal with probable code copying next, this is about general concept and implementation to start with.
by all means, show that you also implemented a threaded qr code reader and for the concept...come on, we're talking about QR codes here, there is no need to be credited for the idea to use QR codes for anything ever.
 

dark_samus3

Well-Known Member
Member
Joined
May 30, 2015
Messages
2,372
Trophies
0
XP
2,042
Country
United States
So no then? Not a single commit showing you even attempted a web based or we based install before well after this was public?

I'll deal with probable code copying next, this is about general concept and implementation to start with.
yes, because the idea of scanning a QR code which links to a download is suuuuuch a new idea....
 

ksanislo

Well-Known Member
OP
Member
Joined
Feb 23, 2016
Messages
386
Trophies
0
Location
Seattle, WA
XP
512
Country
United States
by all means, show that you also implemented a threaded qr code reader and for the concept...come on, we're talking about QR codes here, there is no need to be credited for the idea to use QR codes for anything ever.

Neither of us wrote quirc, it's a third party QR lib. It's the utter lack of attribution on where the first implementation came from. I provided @Steveice10 multiple GitHub pulls about core concepts for doing this, and didn't get any credit for the work what so ever. Hence why I stated that I'd lost ambition on continuing work on the app.
 
D

Deleted User

Guest
Neither of us wrote quirc, it's a third party QR lib. It's the utter lack of attribution on where the first implementation came from. I provided @Steveice10 multiple GitHub pulls about core concepts for doing this, and didn't get any credit for the work what so ever. Hence why I stated that I'd lost ambition on continuing work on the app.
I recall the pull for HTTP installation support in citrus, which I didn't use in FBI or correlate in any way to QR codes (I figured it was for an online store type thing, actually), and the pull to FBI 2.0 for RAM texture loading, which was well after it was suggested to me. Despite it being the first to release, I did not originally get the idea or code from this project, so I see no reason why I would have thought to attribute the feature to it.
 

dark_samus3

Well-Known Member
Member
Joined
May 30, 2015
Messages
2,372
Trophies
0
XP
2,042
Country
United States
Neither of us wrote quirc, it's a third party QR lib. It's the utter lack of attribution on where the first implementation came from. I provided @Steveice10 multiple GitHub pulls about core concepts for doing this, and didn't get any credit for the work what so ever. Hence why I stated that I'd lost ambition on continuing work on the app.
as stated before, the code differs greatly. You've been credited, in a way, with the pull requests with your name on it... Sure they helped make it possible, but if you hadn't I'm SURE someone else would have done it... also, while I get looking to protect your work, you're looking for credit, if you're in the scene for credit then you're in it for the wrong reasons. Credit comes with good, hard work. Thanks for fixing the stuff and making it easier for developers, but you don't see people looking for credit on every application that uses ctrulib, just because they made a pull request, do you?
 

capito27

Well-Known Member
Member
Joined
Jan 19, 2015
Messages
874
Trophies
0
XP
1,230
Country
Swaziland
Neither of us wrote quirc, it's a third party QR lib. It's the utter lack of attribution on where the first implementation came from. I provided @Steveice10 multiple GitHub pulls about core concepts for doing this, and didn't get any credit for the work what so ever. Hence why I stated that I'd lost ambition on continuing work on the app.
as for the lack of attribution for the first implementation, still waiting for CFWs to credit gateway....
 

Aurora Wright

Well-Known Member
Member
Joined
Aug 13, 2006
Messages
1,550
Trophies
3
XP
4,500
Country
Italy
Neither of us wrote quirc, it's a third party QR lib. It's the utter lack of attribution on where the first implementation came from. I provided @Steveice10 multiple GitHub pulls about core concepts for doing this, and didn't get any credit for the work what so ever. Hence why I stated that I'd lost ambition on continuing work on the app.
So let's get things straight:
- I think the idea alone (using QR codes to get stuff) is unoriginal enough that it would be dumb to credit it
- If there's code you think was stolen and put into the FBI codebase just point it out so we can check it out. Just saying "you copied it" without giving proof isn't that conclusive :P
 
  • Like
Reactions: Deleted User

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
  • No one is chatting at the moment.
    Sonic Angel Knight @ Sonic Angel Knight: DAYTONAAAAAAAA!!!!!!!!!!