Looking for Secure Cloud Storage that Respects Data Privacy

This post is the second in a series of three posts about some changes I have been making in my personal life with respect to how I interact with online social media platforms, and how that affects this blog. When I published the first post in this series, I had completely deleted the Facebook and Twitter pages associated with this blog, and I mentioned that I was on the lookout for a secure cloud storage site that respects data privacy (which meant options like Google Drive, Dropbox, or Flickr were not going to satisfy my desires). Since then, I have conducted almost all of my frequent conversations on platforms not owned by Facebook, and I have been in the process of conducting all other infrequent conversations away from Facebook platforms too. However, I have still been on the lookout for such a secure cloud storage site that would also allow me to securely share files, especially pictures, with others, without compromising the privacy of my data. This post goes over some information that I have compiled over different potential candidate services. This is not a review, because I have not actually tested any of these services yet. Follow the jump to see more about each candidate and where I lean.


Shifting Away from Social Media Platforms

This post is the first in a series of three posts about some changes I have been making in my personal life with respect to how I interact with online social media platforms, and how that affects this blog. The points most relevant to this blog are as follows. This blog used to have associated Facebook & Twitter accounts, and I used to share each new post on my own personal Facebook timeline to encourage others to read it. While I'm aware that a few contacts on Facebook did read my & share recent blog posts, there weren't many. Meanwhile, looking back at the Facebook & Twitter accounts associated with this blog, almost no new readership came from those, so I didn't feel too badly about deleting those accounts (after deleting each individual post), especially because the synchronization of new posts from this blog being automatically shared to its associated Facebook page didn't work for the first few months that I tried it (over 10 years ago), and then I stopped caring about that Facebook page afterwards. Furthermore, I added a lot of tools to connect this blog to social media sites over 10 years ago, when I, being in high school and then in the first & second years of college, had more time on my hands & had high hopes for this blog becoming popular online (especially in the domain of Linux distribution reviews); for the last several years, I have had neither the time nor the interest to continue pursuing such popularity contests, and I'm almost certain that I won't feel inclined toward such things again, so I have no problem with removing those connectivity features. I know there are still some widgets built into each post or page on this blog which are connected to different social media sites for easier sharing of posts, and I should remove those eventually, but simply as a practical matter (with respect to my own time), I'm less concerned about removing those right away. In the meantime, I think it is still possible to get updates about this blog via email, RSS, or Atom. Follow the jump to see why I have taken these steps for my blog and am currently undertaking similar steps with my personal presence on social media platforms owned by Facebook or Twitter.


Copyright, Police Interactions, Transparency, and Corporate Dependence

When I started this blog when I was in high school, I was quite interested (at least at a superficial level) in issues of technology law, including the abuse of copyright & patent laws. (This is an example of such a post on this blog from 12 years ago, when my maturity & writing skills were far less than they are now.) Since then, my interests have shifted a lot, so I don't follow news stories about technology law abuses as much as I did in high school or college, I certainly don't post about these issues so often, and I'd like to think my reactions on this blog are a bit more carefully considered now than they were 12 years ago. That said, as far as my older interests go, I saw a story on the website Vice, by Dexter Thomas, about how a few police officers in Beverly Hills, California, have been found to have played copyrighted music from their phones loudly when they believe they are being filmed by an ordinary person. Essentially, those particular police officers have depended on zealous copyright enforcement algorithms on social media & video sharing platforms like Instagram & YouTube to ensure that any ordinary person who tries to post a video on such a popular corporate platform will have that video automatically removed due to copyright violations. If the police officer deliberately chooses to interact with the person recording while the song is playing, that means that even if the person recording decides to mute that section of the audio before uploading, the audio from that interaction will be removed one way or another. Additionally, on many sites, if the person uploading such videos ends up doing this multiple times, that person can be blocked temporarily or permanently from uploading videos in the future.

On the one hand, my beliefs about police behavior & copyright law are such that this behavior disappoints me on both fronts (as I believe this is a gross abuse of the spirit of copyright law and of trust in police officers), but on the other hand, I can't help but appreciate the ingenuity of this "solution" to the "problem" of being recorded. Additionally, it is worth noting that the main instance of this happening as described in this story is in a police station, where it can be argued that police departments could rightfully enforce rules against using cell phones; that said, the story also mentions other instances of this happening in outdoor public spaces. In any case, beyond these issues, this story has raised several broader questions in my mind, which I list below, and which I do not intend to be merely rhetorical.

  1. Would police officers be fined for broadcasting such music as a "public performance" in an unauthorized way?
  2. Should this motivate an alliance between groups aiming to reform police departments & groups aiming to reform copyright laws?
  3. Should this motivate greater use of the site Wikileaks or other existing sites, or creation of a similar site, as a well-known not-for-profit repository to document police abuses (instead of relying on for-profit platforms that might zealously enforce copyright laws)?
  4. What should be the mechanism for determining which videos of police officers get publicized, in order to ensure that trivial misunderstandings don't get blown out of proportion at the expense of the livelihood of the police officer?

There are certainly many other questions that could be asked about this issue going forward. In any case, it is unfortunate that enforcement of copyright laws is being twisted in this way, but it will be interesting to see how similar cases develop in the future.


My Time at the 2021 TRB Annual Meeting

This is a quick update from my attendance of the 2021 Transportation Research Board (TRB) Annual Meeting. The conference was held in a fully online format, and as a result, events were spread over the entire month, with the first & second weeks being filled with committee meetings, and the third & fourth weeks being filled with research presentations & workshops. This was my first time attending this particular conference, and it was my first time attending a conference of this size in the field of transportation since switching into this field. That said, I knew going in that certain aspects, like networking, might feel less satisfying compared to what they would have been if this conference had happened in person in normal circumstances.

I really enjoyed the committee meeting about the transportation needs of people with disabilities, and the later presentation session about the same subject, as those are among my primary research topics right now. I also really enjoyed the workshop about the history & future of road pricing, precisely because that topic is only tangentially related to my research interests, so it was fun to think about these issues that I wouldn't normally think about. Plus, in all of those sessions, I was able to meet people and expand my professional network to some degree.

Of course, the networking aspect fell far short of what I would have expected for normal circumstances, but that wasn't too surprising. More disappointing was that the last week of this conference was plagued by technical difficulties that led to me missing several sessions that I wanted to attend. In particular, the website was designed quite badly, as it often didn't load correctly, and when it did load, it was often quite difficult to navigate to the desired sessions (as it was set up to "mimic" the "spatial layout" of a convention center). Furthermore, although setting up poster sessions as a series of chat rooms may have seemed like a good idea at first, it ended up being quite frustrating to use in practice (when it worked at all), so I felt rather discouraged from signing up for further sessions.

Overall, I'm glad to have attended the committee meetings, and while I generally enjoyed the research presentation sessions that I did attend, I was rather frustrated by how this conference was rife with technical difficulties. I hope this will be a lesson for future online conferences, and I hope too that progress with vaccines against this coronavirus will mean that in-person conferences can return soon enough. (Please note that I have no expertise in epidemiology, virology, or vaccine development, so I cannot claim to prognosticate on this matter.)

Unrelated to this, please note that the public Facebook & Twitter pages for this blog have been deleted. This is because of my unhappiness with those companies' recent actions and my desire to migrate away from those platforms. Of course, this blog will continue to be published here until further notice, and it is still possible to sign up for an email subscription for new posts on this blog.