mark

joined 2 years ago
[–] mark@social.cool110.xyz 19 points 3 months ago

@AVincentInSpace The template system is a big part of that since it makes active collaboration much easier, as long as the template authors are talking to each other then the rest of the community will automatically get new orders whenever they need to reload the page.

For example that battle was originally planned along the other diagonal, before being flipped in a deal with the osu! logo. Same thing happened later on with the Rocket League logo being moved from where the blue portal is.

[–] mark@social.cool110.xyz 15 points 3 months ago

@1boiledpotato It's just the server getting overloaded, only thing to do is wait for it to come back up.

[–] mark@social.cool110.xyz 6 points 5 months ago (3 children)

@GregorTacTac If you use containers you can map something like 8080 on the host to 80 in the container. Generally it's recommended to have a reverse proxy listening on 80 and 443 with all your individual applications on localhost only high ports.

[–] mark@social.cool110.xyz 19 points 11 months ago (4 children)

@BackOnMyBS @savvywolf With federation the only sensible way to deal with this is to use the precedent set by email.

You don't agree to any of Google's ToS just by sending to a @gmail.com address, and if sending from a work address you certainly wouldn't have the authority to bind the company. Of course Google can do what they want with their spam filter, including blocking everything from you.

Following that the terms of lemmy.world have no relevance to external users, unless the admins decide to defederate. Even then there would still be direct delivery between other servers for followers, along with parent post fetching.

[–] mark@social.cool110.xyz 1 points 1 year ago (1 children)

@robinj1995 That's not the case either, the non-Schengan part of Amsterdam Schiphol is mixed as well. The only separation is along the corridor for the H/M gates as those handle both Schengan and non-Schengan flights.

[–] mark@social.cool110.xyz 1 points 1 year ago (3 children)

@robinj1995 No it isn't, the Spanish airports also maintain segregation between arrivals and departures.

[–] mark@social.cool110.xyz 1 points 1 year ago

@jherazob If you use Podman instead of Docker Cockpit gives a great web dashboard covering both the containers and the host machine.

[–] mark@social.cool110.xyz 17 points 1 year ago (4 children)

@Tippon That is a big part of the point behind containers, you don't have any long term state inside them. Migration is just a case of copying the configuration over along with the contents of any persistent volumes.

It's worth looking into Podman instead of Docker, the daemon-less architecture makes it more lightweight and secure as it's easier to have rootless containers. Management can also be easer as being a Red Hat project it integrates well into Systemd.

With your existing server on Xubuntu you may as well stick with Ubuntu Server or Debian for the familiarity.

[–] mark@social.cool110.xyz 1 points 1 year ago

@octoperson There isn't one, there is Wi-Fi and power to access flight information on the airport website.

[–] mark@social.cool110.xyz 3 points 1 year ago

@Rogue I'm familiar enough with Manchester from years of family holidays that I could have easily followed the usual routine and found some of the lesser used seating areas. At Amsterdam it did help quite a bit with being able to manage such a large busy place and reduce the worry of being late.

[–] mark@social.cool110.xyz 5 points 1 year ago (2 children)

@Crackhappy They're not, given that there's a dimmer switch they can only possibly be LED replacement tubes.

[–] mark@social.cool110.xyz 10 points 1 year ago (4 children)

@Crackhappy That's mostly from my phone camera compensating for it. With the naked eye it's a lot lower, especially when compared to the rest of the terminal building.

 

Recently had a short trip to Amsterdam by myself. This was the experience travelling without pre-booked assistance, but while wearing a sunflower ID card and lanyard.

Manchester T1 Departures

I arrived at a quiet time for the airport with the security queues at a minimum, clear instructions were given to all passengers on how to arrange items in the tray to reduced the need for a manual check. After passing security there is a forced through the duty free shop to reach the main departure lounge, once there a "sunflower room" is off to the side with subdued lighting.
The sunflower room at Manchester Airport T1, containing a few armchairs and tables. the lights are dimmer than in the rest of the airport

Amsterdam Arrivals

Navigating from the gate to the baggage hall was slightly confusing due to ongoing building works with portable signs contradicting the permanent ones in places, however the first of these did have a staff member helping with directions. At passport control I was instantly recognised and directed from the main queue to the "aircrew, diplomats, and disabled" lane, this was very helpful as there were only 2 officers on duty despise a flight from China being ahead with its passengers needing extra documents to be checked..

Amsterdam Departures

I had decided to make a booking with the free security timeslot service available to all passengers, this has no one else at all at my selected time allowing me to proceed directly to the merge point with the main queue. As they have the advanced CT based bag scanners in use this was much faster with no need to remove liquids and electronics from the bag. Passport control was once again the same, being directed to the express lane. While there is no dedicated quiet room in the departure hall there is a small gallery from the Rijksmuseum, which of course requires dimmed lighting to protect the paintings within.

Manchester T1 Arrivals

Fortunately we arrived at a gate on the good side of T1 that prevents conflict with other gate boarding, (unlike the Netherlands the UK does not allow arriving and departing passengers to cross paths). At passport control I was once again directed to the dedicated assistance lane.

view more: next ›