Jason Friedrich

Thoughts, Links & Moods

Back in January, Facebook and Google got caught being very cozy with each other. They both looked very shady, and it seemed to be good ammunition for the antitrust lawsuit they are currently facing.

They found out now that Google wrote a software called “Bernanke” to gain a major advantage over the competition. No one in their sane mind could think that there is not an antitrust problem here. Being a buyer and a seller, at the same time, in the same system, reeks of corruption and illegal activities.

Facebook and Google need to be properly regulated, and with a hard hand, in my opinion. They were unregulated for far too long. It is time to get back some of that competition that they stomped out on their way to success.

#google #facebook #ads #en

When I received the new company Apple Silicon MacBook Pro, I started to use Microsoft Edge for work instead of my old default: Google Chrome. I thought it would be a good idea, as we are making heavy use Office365 Enterprise, but I did not want to miss the features and compatibility the the Chromium engine offers.

So far the transition has been very smooth, but one thing drives me crazy. Whenever you copy and paste a link from Edge, it tries to be smart and adds a link with the title of the page as link text – instead of the plaintext URL.

So fucking annoying! Thank god you can change the default behavior.

#microsoft #edge #en

Ich verstehe beim besten Willen den Hype um Clubhouse nicht. Ein Dienst, der selbst chinesische Dienstleister nutzt und es nicht erlaubt das man Mitschnitte anfertigt, ist in meinen Augen nutzlos. Gerade wo wir anfangen uns von linearen Inhalten zu lösen, gehen wir zurück auf exklusive, lineare Inhalte?

Ich verstehe natürlich, wieso die Leute von der Idee, die hinter dem Dienst steckt, so angetan sind. Der Appeal von (in Corona Zeiten) rar gewordenen „Live Events“ zieht eine Menge Menschen an, die diese Art von Events vermissen, die danach dürsten. Auch wenn ich selbst nie einer von ihnen war.

Jetzt versuchen es alle zu kopieren, um noch schnell ein Stück vom Kuchen zu ergattern, bevor das Ende der Pandemie den Hype vermutlich extrem abflachen lässt – vielleicht sogar beendet.

#clubhouse #covid #hype

Shit, I am feeling really old today. macOS was released 20 years ago. Of course, it was called “Mac OS X” back then 😄.

I never worked with MacOS 9 myself, but I rembember driving to Düsseldorf to get one of the first copies of MacOS X Tiger in 2005. Back then I had a PowerPC Mac Mini. I remember feeling excited. After years of using a Linux desktop system, it was great to finally have a well-designed graphical user interface, but at the same, don't miss out on the powerful UNIX tools.

Nowadays Windows has caught up a lot with “Windows Subsystem for Linux(WSL)” and their increased support for Open Source software and services. But Apple has a revival of their with their new ARM hardware — even though macOS Big Sur is not so great 😞.

#macos #software #en

Trying something new. I realized that I have not blogged in quite a while. like, a real long, elaborated blog post. I guess there is not much happening at the moment that would justify that. Maybe for the new homelab project.

In the meantime, I will blog more here. It wont be as elaborate, not as well versed. Quite the contrary, rough thoughts, ideas and commented links.

At least until I have finished writing my own blog backend. I am not a software developer by heart, so it will take a while. It is going a bit slow, but I think it is worth it.


I never thought I would be getting used to Visual Studio Code after I used Sublime Text 3, a native macOS application with Python backend. But here I am. It performs better than Atom, is soon to be compatible with the Apple Silicon and has a lot of powerful plugins. Don't want to live without GitHub Codespaces or without developing in Remote Containers anymore.

#misc #editors

I guess I have to finally learn how to properly use npm, if I really want to invest in writing my own (micro-)blogging software. The django-tailwind package seems to use it to manage the css framework. So far I was able to avoid any of that software that surrounds the dumpster fire that is NodeJS. Fuck me.

#development #npm

Just tried to search for some Django modules in pip and got a very nasty surprise.

ERROR: Exception:
Traceback (most recent call last):
  File "/usr/local/lib/python3.8/site-packages/pip/_internal/cli/base_command.py", line 224, in _main
    status = self.run(options, args)
  File "/usr/local/lib/python3.8/site-packages/pip/_internal/commands/search.py", line 62, in run
    pypi_hits = self.search(query, options)
  File "/usr/local/lib/python3.8/site-packages/pip/_internal/commands/search.py", line 82, in search
    hits = pypi.search({'name': query, 'summary': query}, 'or')
  File "/usr/local/lib/python3.8/xmlrpc/client.py", line 1109, in __call__
    return self.__send(self.__name, args)
  File "/usr/local/lib/python3.8/xmlrpc/client.py", line 1450, in __request
    response = self.__transport.request(
  File "/usr/local/lib/python3.8/site-packages/pip/_internal/network/xmlrpc.py", line 46, in request
    return self.parse_response(response.raw)
  File "/usr/local/lib/python3.8/xmlrpc/client.py", line 1341, in parse_response
    return u.close()
  File "/usr/local/lib/python3.8/xmlrpc/client.py", line 655, in close
    raise Fault(**self._stack[0])
xmlrpc.client.Fault: <Fault -32500: "RuntimeError: PyPI's XMLRPC API has been temporarily disabled due to unmanageable load and will be deprecated in the near future. See https://status.python.org/ for more information.">

Python's status site has more nasty details:

Update — Dec 15, 20:59 UTC The XMLRPC Search endpoint is still disabled due to ongoing request volume. As of this update, there has been no reduction in inbound traffic to the endpoint from abusive IPs and we are unable to re-enable the endpoint, as it would immediately cause PyPI service to degrade again. We are working with the abuse contact at the owner of the IPs and trying to make contact with the maintainers of whatever tool is flooding us via other channels. Monitoring — Dec 14, 17:46 UTC With the temporary disabling of XMLRPC we are hoping that the mass consumer that is causing us trouble will make contact. Due to the huge swath of IPs we were unable to make a more targeted block without risking more severe disruption, and were not able to receive a response from their abuse contact or direct outreach in an actionable time frame. Update — Dec 14, 17:30 UTC Due to the overwhelming surges of inbound XMLRPC search requests (and growing) we will be temporarily disabling the XMLRPC search endpoint until further notice. Identified — Dec 14, 15:09 UTC We've identified that the issue is with excess volume to our XLMRPC search endpoint that powers pip search among other tools. We are working to try to identify patterns and prohibit abusive clients to retain service health. Investigating — Dec 14, 09:41 UTC PyPI's search backends are experiencing an outage causing the backends to timeout and fail, leading to degradation of service for the web app. Uploads and installs are currently unaffected but logged in actions and search via the web app and API access via XMLRPC are currently experiencing partial outages.

Damn, had to happen one day I guess. Single point of failure, infrastructure provided by volunteers and goodwill. Hope they can resolve this soon.

#python #development

After Bandcamps hey.com app update was not approved in the Apple App Store, Kosta Eleftheriou shared his story on how ridiculous and arbitrary Apple's guidelines are.

Nilay Patel already summed up his thoughts on the Apple App Store back in December.

Ich habe ja schon immer mal darüber nachgedacht mich selbstständig zu machen. Für alle die auch darüber nachdenken, ein Erfahrungsbericht von Aaron Siller bei Golem.

Enter your email to subscribe to updates.