71–80 of 83 posts
Took a look, seems to me like the title is a bit misleading. Maybe I'm mistaken but from watching the video I don't get the sense that this copies 'React code', from any site, it just takes a section of the dom from any site and copies over the relevant css and js. I think something like this is going to take off though, as frontend devs we keep reinventing the wheel needlessly. You should be able to point to a site,…
Earlier quoted context omitted.
Two absurd claims: 1. Getting sued 2. Getting your work pulled off the internet You say that you or your employer would be sued if you did this. Going through a legal battle over some copied HTML, CSS & JavaScript is expensive, distracting and time consuming. You'd first get a cease and desist letter. Who has the time or energy to sue over this? Getting your work pulled off the internet against your will. How would t…
C&D is a low effort shot to stop infringement. Suits follow where wilful and especially profitable or profit-damaging activity that can be shown. Eg, you stick it in your product. Saying suits are fanciful is harmful because they do happen . They often settle early, but that's attention your employer won't thank you for. It'll be grounds in many cases. Very familiar with TPB. Their founders did time for their involve…
Your original comment stated, as fact, "you'll get yourself or your employer sued, and/or your work pulled off the internet against your will."
You're right that suits do happen, and while there is a grain of truth in what you said, stating it the way you did is just too bold in my opinion. I highly doubt the individual developer would be sued. How would a company seeking damages know who made the git commit so they could target the developer?
The clarification in your reply about copying being willful, profitable and profit-damaging is where things start to make sense. And if you had said something along the lines of that, I wouldn't have replied and would have found myself in agreement.
Nice work! Love how simple the landing page is. Does it copy adaptive styles as well?
And it’s open source. This file does all the parsing magic to get clean html.
https://github.com/kdzwinel/SnappySnippet/blob/master/js/too...
I host 2 sites there:
I’ve found it quite nice for maintaining static sites which I update once a month or so.
This is pretty cool. Are you worried about copyright at all though? Especially if this get used in a commercial context?
It's up to users of the tool to ensure they comply with the law. Just like you somehow restrain yourself from photographing someone else's picture and then selling it.
But screenshotting and reselling peoples NFTs is one of my favorite hobbies.
There’s a hidden part of Aspect that is very functional, with some rough edges: https://sites.aspect.app I host 2 sites there: - https://everettberry.com - https://prcvlabs.org I’ve found it quite nice for maintaining static sites which I update once a month or so.
Coming from Asia, these are some of the slowest sites I've seen this morning. Aspect seems to be running on Express hosted on DO. Not sure why they don't cache properly and/or go JAMstack and/or have a proper CDN.
Remember: others' work is theirs unless they license it to you. Just because you technically can copy something doesn't mean you're allowed to make and distribute copies or derivatives. If you do this professionally, you'll get yourself or your employer sued, and/or your work pulled off the internet against your will. You wouldn't steal a policeman's helmet, etc.
> Remember: others' work is theirs unless they license it to you. But Google scraping the web is somehow allowed? I'm not against it but these laws seem arbitrary.
One is ripping out a technical inner working from a website and using that to create your own.
The other is just making a directory of where to find things that are intentionally publicly available
Earlier quoted context omitted.
At the time of posting, the extension actually allows you to export either jsx (which you can directly place in a react file) or html. That detail just isn't shown in the video, which shows an earlier version of the feature. Will update video.
Some logic to rename variables and perhaps wrap on-screen text with an instruction to rephrase, coupled with watermarking images so they have to be replaced, might effectively render copyright objections void/unenforceable ... it's not like you can copyright the general techniques. This would make it a far more viable commercial tool. If this could be combined with tooling to facilitate the use of generated code to m…