“I Don’t believe in Giannis anymore”…

https://antetokounmpo1.wordpress.com/2026/06/17/i-dont-believe-in-giannis-anymore/

i have just spent my afternoon sorting out my weekly routine now that university is back in session.
Most of Wednesday I will be online for lectures from from 1:30 to 4:30 in the afternoon, then again from 5:30 to 7:30 in the evening. I normally eat at 5, so that gap in the middle is non-negotiable, and I will be honest, the evening stretch after dinner is going to require some deliberate energy management on my part.

Saturdays I will be online from 3:30 to 5:00 in the afternoon, which is a much more manageable block and feels like a gentler way to end the weekend. and of course, there are assessments to do in between all that.

#ActuallyAutistic #AuDHD #NDCommunity #OnlineNow #Availability #DisabilityPride #NeurodivergentLife #Counselling

Weird: I check my site https://miamao.de/blog/ hosted on codeberg from home

- through wifi: works
- through mobile only to avoid potential specifics in my home network: works
- any "check my website" online tool: not reachable

2 days ago from abroad: not reachable
🤔 🤷 😕

For online tools its probably Codeberg's bot self defense, but why not reachable two days ago? Any ideas how I can check availability in general?

#web #dns #availability #hosting #codeberg

Security (b)log: Dumb iPad
It didn't talk to the outside world anymore. The solution was surprising.

#ipad #wifi #vpn #security #availability

News from the big bad world: many hacks | passwords cracked easily | children and fake moustaches | more

https://securityblogpatrick-english.blogspot.com/

GitHub is planning to be more transparent on availability

Two unfortunate incidents that plagued GitHub happened in two different days during April, which caused instability in some areas of GitHub, including:

• April 23rd: GitHub had experienced problems related to merge queue operations for pull requests for affected projects, which caused squash-merged pull requests to produce incorrect merge commits when a merge group had more than one pull request. Because of this, subsequent merges have inadvertently reverted the pull requests’ changes.
• April 27th: GitHub had experienced problems related to search functions, including code search, as well as issues and pull requests searching, because of an incident that affected GitHub’s ElasticSearch subsystem. The cluster was overloaded, with the most possible chance being a botnet attack, which caused GitHub to be unable to perform searches.

According to the article that was published to the official GitHub blog, the team had to resolve a variety of bottlenecks by changing how systems work, such as:

• Authorization and authentication flows have been redone to reduce stress caused by database load.
• Webhooks have been moved to a different backend.
• User session cache has been redesigned.

Critical services have been dealt with by carefully analyzing different dependencies and risk levels, and started working on those improvements in order of risk. Those services like Git and GitHub Actions have been isolated to minimize the blast radius so that attacks will be less efficient. Also, cloud migrations have been initiated to make sure that high reliability and flexibility is achieved.

In order for the official GitHub status page to be more reliable and transparent, the team has also worked on updating the GitHub status page to include availability numbers and to include statuses that are either major or minor, so that users can have a more accurate representation of the service status. Also, GitHub is working on making sure that incidents can be more easily reported by users.

To learn more, visit the official GitHub blog article.