SoundCloud once messed up a huge song import - hundreds (as in more than 9 hundreds). There was no way to batch clean/edit, or even clear/nuke (i.e delete everything). Support refused to help. They clearly said they "won't" do it and they helpfully asked me to do it one by one because that was the way users were supposed to do it. I kept requesting that they could just delete everything and I would set up everything again because at that point my profile looked all garbage and noise. They refused and stopped responding. I found a CxO email and mailed seeking help. I never received a reply. A few days later, I just deleted that really old account. I used to use the site very regularly since the beginning. But after that, they never even came to my mind until I saw this here on HN.
same here. been a paying customer for 2 years, a soundcloud listener for 5+. this is where i switch back to downloading music off russian pirate websites.
well, life isn't all sunshines and rainbows after all :)
i'm glad there are lots of people who think just like i do and are ready to sacrifice convenience for the sake of privacy
Have you considered whether you really need to use git? You could just take regular snapshots if you are concerned about needing to revert/undo. Or use a tool like git wip to automatically make commits every time you save, if you really like the git UI.
I mean, git is useful even without "human-readable" commit messages.... 99% of my commit messages are complete garbage ("fixes" "farming, music and shit" "update" ".", etc.)
but in practice it's not a huge problem, IDE shows you the commit history of a specific file so bisecting changes is easy, there's only a few entries with the roughly correct date modifying the file you're looking for :D
"low quality code/commit messages" hasn't really slowed me down so far and probably won't in the future either
I can't wait until it is easy to rotoscope / greenscreen / mask this stuff out accessibly for videos. I had tried Runway ML but it was... lacking, and the webui for fixing parts of it had similar issues.
I'm curious how this works for hair and transparent/translucent things. Probably not the best, but does not seem to be mentioned anywhere? Presumably it's just a straight line or vector rather than alpha etc?
The main idea of renaming from Perl6 to Raku was to allow this beautiful and seductive new language to escape the black hole gravity well formed by the collapse of the Perl star. Seems like Raku is stuck inside the Perl event horizon for ever, with no hope of reputational escape.
I think it was based on the misconception that the mainstream turned away from Perl because of a handful of warts and mistakes, not because Perl's unconstrained flexibility made it impractical, and that Perl "done right" could recapture the excitement and mainstream attention that Perl once enjoyed. I think they should have accepted that the existing community was already the largest subset of programmers that could embrace Perl's trade-offs, with or without the historical warts.
fwiw I think Perl was so popular in the late 90s that a transition like Python2.0 to 3.0 that traded some backward compatibility for some structure COULD have been successful. However, the Perl community also got tired of waiting such a long time for what is now Raku, and it was so different with no incremental migration path, that the lifeboat never materialized. Its not like Larry and the community didn't know that a transition was needed, but the execution was not there.
> a transition like Python2.0 to 3.0 that traded some backward compatibility for some structure COULD have been successful.
I think Perl was a lot further away than Python was from anything that would have allowed "trading some backward compatibility for some structure".
This was a clear case of a language collapsing under the weight of its own poor decisions and lack of coherent design. Could it have been kept on life support with a series of incremental improvements? Probably, but things wouldn't have gotten materially better for its users, and it would have bled users anyway as the industry left it behind.
Does this analyze the video itself with AI or does it just use the text / description and other metadata? Would love to know more details on how that works
It analyzes the entire video along with the metadata so that the entire context is captured. It even extracts important info like it is a travel itinerary, it will give you a list of places with direct links to Google Maps, or if it is a movie review, it will give a button that will take you to the trailer on YouTube. I am supporting 9 different specific genres and 9 genre-specific UI.
I recently discovered a static site generator called Astro, which supports many syntaxes but the .astro is a nice mix of TypeScript and JSX-like syntax. Content can use MDX which is like Markdown but with {JSX} style markup for variables and etc. The static components are used very similar to React, with familiar import statements and <ComponentName props=etc> patterns. It is extremely easy to pick up. Best of all, it has plugins to support all sorts of other interactivity, so you can create interactive 'islands' of content using React or Preact or SolidJS or Vue etc. That way you have most of your content statically generated, and then the dynamic parts can be done from the client side.
Best of all, if you use simple unchanged files for other dynamic stuff like JSON etc, you can just generate those on build and serve those files in the host directly as the 'response' to a simple REST request, which is sometimes overlooked despite being the most fundamental form of a REST API.
I came across this after researching various options for a website that had, mostly for my own entertainment, restrictions on wanting to be mostly statically generated but customizable easily without learning a lot of new syntax / etc, something JSX-like with Markdown support etc, and MDX was an immediate find - and astro was the easiest SSG I found for it after trying with 11ty and several others. Actually felt like a delight playing with it.
> if you use simple unchanged files for other dynamic stuff like JSON etc, you can just generate those on build and serve those files in the host directly
Other web frameworks support this too, if you look for "static export" options. Next.js, for example, supports this via the getInitialProps function.
What I like especially about Astro, that you perform this data loading during build time from any component/file on your page. With Next.js, this is only possible via the top level Page component.
Built a few reusable templates and JSON for storing game data (maybe not ideal at scale, but seems to be working for now). JavaScript, CSS, and MDX. Hosted on Netlify which is an 'Official Deployment Partner'. It's light and simple. So far has been a joy to work with.
I create music videos which can be provocative, though not necessarily pornographic, and this kind of thing really bothers me since I've run into similar problems even just with hosting and donations. Thankfully, I don't try to make this anything more than a creative outlet, so I don't have to worry about taking payments, and I'm happy enough that any expenses are at least covered by a few donations. But it concerns me that it is not an option for others who might find themselves in similar gray areas.
