This repository has been archived by the owner on Oct 22, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
/
index.xml
125 lines (103 loc) · 9.01 KB
/
index.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Vidify</title>
<link>https://vidify.org/</link>
<description>Recent content on Vidify</description>
<generator>Hugo -- gohugo.io</generator>
<language>en-us</language>
<lastBuildDate>Sat, 01 Apr 2023 00:00:00 +0000</lastBuildDate><atom:link href="https://vidify.org/index.xml" rel="self" type="application/rss+xml" />
<item>
<title>The End of an Open Source Journey: Archiving Vidify</title>
<link>https://vidify.org/blog/archived/</link>
<pubDate>Sat, 01 Apr 2023 00:00:00 +0000</pubDate>
<guid>https://vidify.org/blog/archived/</guid>
<description>Vidify was one of my first big software engineering projects, and I invested a tremendous amount of effort into its development. Supporting multiple platforms, building an audio synchronization extension, communicating between devices through DNS-SD, and releasing a website and Discord server were just some of the many tasks which helped shape my growth as a software developer.
The most rewarding part, however, was collaborating so closely with the open source community.</description>
</item>
<item>
<title>The state of Vidify in 2021</title>
<link>https://vidify.org/blog/202105-update/</link>
<pubDate>Sat, 15 May 2021 00:00:00 +0000</pubDate>
<guid>https://vidify.org/blog/202105-update/</guid>
<description>I wanted to give some closure regarding Vidify to its followers, I&rsquo;m very grateful for the support I&rsquo;ve received. I haven&rsquo;t been working on this lately; I&rsquo;ve been with other projects and more stuff outside of programming so I had put Vidify aside for some time. I wanted to explain why in this article.
The Issues I have some very big issues that I have to deal with before continuing, which have prevented me from working on Vidify further until now:</description>
</item>
<item>
<title>Optional parameters in Rust</title>
<link>https://vidify.org/blog/rust-parameters/</link>
<pubDate>Sat, 10 Oct 2020 00:00:00 +0000</pubDate>
<guid>https://vidify.org/blog/rust-parameters/</guid>
<description>Disclaimer: I will now be posting these kind of posts at my personal blog: https://nullderef.com/blog/rust-parameters/
Optional or default parameters are a very interesting feature of some languages that Rust specifically doesn&rsquo;t cover (and looks like it won&rsquo;t anytime soon ). Say your library has lots of endpoints like so:
fn endpoint&lt;T1, T2, T3, ...&gt;(mandatory: T1, opt1: Option&lt;T2&gt;, opt2: Option&lt;T3&gt;, ...); In this case, when you call endpoint, you have to use endpoint(mandatory, None, None, .</description>
</item>
<item>
<title>Discord server</title>
<link>https://vidify.org/blog/discord/</link>
<pubDate>Fri, 25 Sep 2020 00:00:00 +0000</pubDate>
<guid>https://vidify.org/blog/discord/</guid>
<description>I have created a Discord server for Vidify! You can join using this link. It&rsquo;s meant for quick conversations outside of GitHub, for both depelopment and user reasons.
I was initially going to use an open source alternative but decided to go for Discord because it&rsquo;s the easiest. If you&rsquo;d like to suggest any other platform please let me know.
If you have experience with Discord servers I&rsquo;d love to get some help as well, as I haven&rsquo;t managed one before :)</description>
</item>
<item>
<title>FAQ</title>
<link>https://vidify.org/wiki/faq/</link>
<pubDate>Sun, 05 Apr 2020 00:00:00 +0000</pubDate>
<guid>https://vidify.org/wiki/faq/</guid>
<description>My favorite music player isn&rsquo;t supported by Vidify Vidify was created with this in mind. There are many different music players and we are working on supporting as many of them as possible. Please do let us know so that we know what players are more popular.
Vidify doesn&rsquo;t recognize some downloaded songs If the song doesn&rsquo;t have a metadata field with its title and artist (the latter is optional), Vidify is unable to know what song is playing.</description>
</item>
<item>
<title>Linux Media Players</title>
<link>https://vidify.org/wiki/linux-media-players/</link>
<pubDate>Sun, 05 Apr 2020 00:00:00 +0000</pubDate>
<guid>https://vidify.org/wiki/linux-media-players/</guid>
<description>This is the most recommended API for Linux users. It obtains information from any MPRIS compatible media player (MPRIS is a standard interface widely used for media players on Linux). All you may need to install are the following libraries, although they will probably be installed in your system already:
PyGI (not packaged on PyPi, you need to install it from your distribution&rsquo;s repository - it&rsquo;s usually called python-gi, python3-gobject or pygobject).</description>
</item>
<item>
<title>Spotify for Windows and Mac OS</title>
<link>https://vidify.org/wiki/spotify-for-windows-and-macos/</link>
<pubDate>Sun, 05 Apr 2020 00:00:00 +0000</pubDate>
<guid>https://vidify.org/wiki/spotify-for-windows-and-macos/</guid>
<description>This is the default API for Windows and Mac OS users. You don&rsquo;t have to install anything, since it&rsquo;s already installed by default on these platforms.
Current limitations The library used to access information from the Spotify API is unable to obtain its position. Mac OS usage hasn&rsquo;t been tested because their emulators are really limited. If you&rsquo;re having issues, please open an issue with detailed information. </description>
</item>
<item>
<title>Spotify Web API</title>
<link>https://vidify.org/wiki/spotify-web-api/</link>
<pubDate>Sun, 05 Apr 2020 00:00:00 +0000</pubDate>
<guid>https://vidify.org/wiki/spotify-web-api/</guid>
<description>All the supported platforms have a way to obtain song data from the desktop Spotify app, but it may not be as reliable as the official web API, or may lack features in comparison to it. For example, with the Spotify Web API, you can control the music on other devices other than where Vidify is running. However, it also brings other downsides:
You have to sign in and set it up manually (only once though) Only Spotify Premium users are able to use some functions API calls are limited More internet usage is needed to continuously communicate with Spotify The simplest way to activate the web API is by selecting it in the GUI when the app is launched for the first time.</description>
</item>
<item>
<title>The Audiosync extension</title>
<link>https://vidify.org/wiki/audiosync-extension/</link>
<pubDate>Sun, 05 Apr 2020 00:00:00 +0000</pubDate>
<guid>https://vidify.org/wiki/audiosync-extension/</guid>
<description>You&rsquo;ll realize that some videos aren&rsquo;t exactly in sync. That&rsquo;s because the videos are played from YouTube, and they are usually different versions of the song, have intros and outros&hellip; which mess up the timing. Although this is very complicated to fix, Vidify has an audio synchronization extension that tries to.
The full repository is in vidify/audiosync. It&rsquo;s still Work-In-Progress, so it might be harder to use.
Audiosync is only available on Linux for now.</description>
</item>
<item>
<title>Website Launch</title>
<link>https://vidify.org/blog/launch/</link>
<pubDate>Thu, 02 Apr 2020 00:00:00 +0000</pubDate>
<guid>https://vidify.org/blog/launch/</guid>
<description>I&rsquo;m officially releasing Vidify&rsquo;s website!
This site is intended for non-developers, I&rsquo;ll migrate part of the GitHub documentation here on how to use Vidify. The wiki is also better managed in here because multiple languages can be used easily, and anyone can still contribute by making a PR to vidify/vidify.org-source, which is better than wiki contributions.
I still have to polish it a lot, but it&rsquo;s ready to be public already.</description>
</item>
<item>
<title>The external player protocol</title>
<link>https://vidify.org/wiki/the-external-player-protocol/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://vidify.org/wiki/the-external-player-protocol/</guid>
<description>The external player defines a public model to follow to communicate with other devices. That way, anyone can implement their own app or program to display the videos. Here&rsquo;s a more detailed description of how to do so:
Establishing the connection To connect the devices, a DNS-based Service Discovery (DNS-SD) mechanism is used. The Vidify server will register itself in the network, and anyone inside it will be able to connect to it.</description>
</item>
</channel>
</rss>