There's also Irys (from Alan Schaller). It's more open than Glass, as it's a freemium model, but it's also more closed at the same time, as it doesn't offer a web-based version. It's probably even more photographer-oriented than Glass. For something truly open, there's Pixelfed. All those platforms have their pros and cons, especially regarding the audience. Personally, I publish all my photos on my own website and syndicate them to (in order of preference): Glass, Pixelfed, Instagram, Irys.
I've tried Irys as well but the mobile only is kind of a deal breaker for me — I like seeing images in the big monitor to appreciate them more.
Of course I also have my webpage to showcase my favourite pictures but I feel I'm more picky in that site than in, say, Glass and instagram, since I want to show 'the best' there :-)
But you still have to pick up the tickets at the machine. Additionally, my mobile phone internet is not recognized as "being in Japan", so I can't access the QR code needed for the ticket without wifi. You can work around it (save the QR code when you have wifi), but it all just seems so inefficient compared to all the countries where you can _book_ your tickets using a mobile app.
This sounds great, especially as it's linked to the IC card. Unfortunately, I couldn't find anything similar for JR West or JR Kyushu, which I will be using in the next few weeks. Hopefully they will implement the same system in the future.
Vacation is also never mentioned in those discussions or comparisons. 10 days in the US vs. 20-30 (+ 8-14 public holidays, depending on the state) in Germany is much more important for _me_ than the net income.
Can't you take days off without pay in the US? The numbers that usually come up are twice the income compared to France. Taking 20 more days off without pay means losing a month of salary, which doesn't come close to making up the difference.
HTML vs. CSS is a separation of technologies. If HTML was really only about the content and the CSS was only about styling, we wouldn't have to write div soups to style our websites (.container-wrapper .container .container-inner { /* "separation" */ }) and we wouldn't have to adjust our HTML when we change the layout.
Fine for a static site which is frozen at the first version forever.
So, so, painful for apps which need to change and evolve over time, which I'm currently experiencing. It's too easy to break the bits where you needed to get clever to make a layout variant work.
I did also did a Zen Garden on YouTube recently when they removed the list view option from Subscriptions, restyling their grid markup was a fun CSS exercise.
But for that designers should care about the limitations. But they don’t care. Not even about the more basic ones. I’m quite sure many of them don’t even know. Mainly, because their customers are not the one who code.
I got many designs for websites where customers told me that they want a pixel perfect version. The funniest one was when my boss who supposed to be a “senior” web developer told me this. Of course, there is no such thing on the web or really anywhere. Actually, I’ve never seen a design plan in which wildly different aspect ratios and sizes were really considered.
If the designer is not aware of the ins and outs of the medium they are supposedly working with, they are not a very well informed and educated designer.
Just like I don't presume to be able to make a great product packaging design, without knowing firstly much more about visual composition and design, but also secondly the material and form and shape I am designing for. Will that be a plastic wrapper, a paper wrapper or some cardboard packaging? Without knowing the limitations and properties of each, how can I expect to create a good design?
Being that uninformed to me seems like not giving a shit about the quality of work one delivers, ergo not giving a shit about ones job, or simply not having the required understanding or skill to be any good at ones job.
> not giving a shit about the quality of work one delivers
I’ve learned in the past decades that people who care about quality is the minority.
Look at any B2B software. They don’t care because their customers are different than who uses their products. They care about their customers only (managers). They pay attention to users as much as minimally possible without loosing customers.
CSS Zen Garden is quite the opposite of a good example of your point. Even small changes to the original page layout would completely break most of the provided styles.
If I removed the .page-wrapper class it would be also nearly impossible for a different developer to reverse-engineer the issue from the existing Template and CSS files.
The point isn't simply "class removal affects cascading", but "anything upstream is capable of placing the original content in an unrecoverable state".
Where "anything" could be your framework, your CMS, you or your coworkers a few years after the original CSS has been written and you can't fully remember what ".format-header__nav-wrapper:not(:last-child) .model-header__nav-wrapper:not(:last-child)" is doing.
And yes, that's a real CSS selector from a refactoring job I'm doing right now.
I find that most div soup is going away with CSS Grid. CSS Grid is often best when you lose wrappers and nesting. subgrid and display: contents help pop layers when you can't touch the HTML nesting, but now a lot of nesting feels unnecessary in the first place.
This actually blocks a lot more than just AI crawlers. You shouldn’t use this without reviewing it in detail so that you understand what you are actually blocking.
For instance, it includes ChatGPT-User. This is not a crawler. This is used when a ChatGPT user pastes a link in and asks ChatGPT about the contents of the page.
One of the entries is facebookexternalhit. When you share a link on Facebook, Threads, WhatsApp, etc., this is the user-agent Meta uses to fetch the OpenGraph metadata to display things like the title and thumbnail.
Skimming through the list, I see a bunch of things like this. Not every non-browser fetch is an AI crawler!
reply