Amazing: API quotas for requests to read a list of likes (50 results per page) and adding each item to another playlist are completely exhausted by ~ 180 items. Per day. Of the 1200+ likes that I have. That is, the API does not allow to solve the problem without resorting to hand migration of one video once a minute, because the new interface lags and constantly slows down, loading useless elements.
Dear ... No. Fucking darling #youtube:
* Why do you introduce such big changes without explaining why they are being introduced?
* Why now I have to get into my account to show the videos I like to anyone else?
* Why do I have to make three clicks to bypass this (Save - Mark playlist - Save) instead of one?
* What should I do with thousands of videos already tagged? Move to separate playlist? Okay, I can still automate this through your API, but what can other people do?
I spent all day formulating this text in (native) Russian, please do not tell me that the project is being used abroad.
Much issues. Very NaN. #godot
Yesterday I had a good night programming stream with chatter and improved code of #word. ☺️
If I were doing the game alone for a year, then the same work could be done in just a couple of months if there was a team of 5 people, each of which simultaneously does a certain area of work for one on all projects. If you turn on the file openness fighter and enough attention to it, then the time spent can be safely divided into tens and hundreds of people.
I like the way OpenSource solutions (with due support from the audience) are developing much faster than proprietary ones. At least this is due to the fact that 10 "closed" developers are unable to sufficiently improve their product compared to 5,000 open enthusiasts. This is a simple matter of time and asynchronous tasks.
#word now support custom redirects and changing taxonomies urls by general config file! 🎉
I published a useful bookmark for semi-automatic removal of duplicate scrobbles in the #lastfm library: https://gist.github.com/toby3d/531f7790eee15c17b307479ca0f4aea4
Nice and cute #nsfw for you and good night 👋🏻
If everything goes like clockwork, then in the summer I will actively use my own engine in order to identify unexpected bugs and introduce improvements that could improve the experience of use #word. The most important thing in this is that the engine is open and available for use and modification for everyone. I hope that its simplicity and minimalism will appeal to its future users, and potential developers will support my undertaking with useful patches.
I am surprised that this is already working well and am preparing to wrap sensitive routes in protective layers. I do not want to resort to the use of passwords, as they are insecure, preferring a passwordless authentication mechanism. I have already tested this separately from the #word and, I think, it will be a good solution.
Let's talk about my current big project - #word. This is a long-term project of my own blog engine on #golang, which I have already started three times, but not very successfully. But on the fourth attempt to completely rewrite from scratch, I achieved significant success in less than a month: full basic support for publishing posts and pages on behalf of one user. As well as support for customization of the theme and reactive dashboard for administrator.
By the way, advise some decentralized and open analog of Facebook, like Diaspora or something else. I want to finally get rid of a social network that I have not been using since registering there due to overload of functionality, advertising and the imposition of business functions. This should be a social network, not a blog. For a blog I am developing my own engine.
aka One-Aloner. Creative person from Russia.
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!