Is there any way people can help? From your last sentence, it sounds like another PR isn't it and the opposite might be needed. But would love to contribute with testing if helpful. I'm regularly jumping between XFCE, KDE, GNOME, Niri, etc..
I agree that displays and input changed. But if you think in fundamentals, like clarity, readability, affordances, you tend to arrive at the right answers anyway.
Those principles survived CRTs, TN panels, Retina, touch, trackpads. They’re not tied to a specific technology.
Can you give me an example of a change in todays UI that was motivated by change in display quality?
I’m working on something similar for Linux. Would love to chat if this is interesting to you.
The idea is to bring the UX of OSX Snow Leopard back, adjusted for today’s possibilities (better developer experience, AI, etc.). I’m developing a DE, SwiftUI/AppKit-equivalent, and a bunch of reference apps I‘m personally missing in terms of quality (e.g. Raycast/Spotlight, Mail).
Can you share a bit more on the small LLMs you've trained? I'm interested in the applicability of current consumer hardware for local training and finetuning.
I've shared this example in another thread, but it fits here too. Few weeks ago, I talked to a small business owner who found out that Google's AI is telling users his company is a scam, based on totally unrelated information where a different, similarly named brand is mentioned.
We actually win customers who's primarily goal is getting AI to stop badmouthing them.
The goal is not to use a similar tech stack e.g. GNUstep. Instead I'm focusing more on outcome - a desktop environment with a similar degree of polish and functionality without the need for third party tools.
To stay competitive and iterate fast I'm adding a high-level JS/CSS API on top of Wayland, think AppKit + SwiftUI. If you look over my shoulder it might look like I'm making a webapp, but on a custom browser.
A desktop environment for Linux, visually inspired by OSX Snow Leopard with a touch of contemporary. Coming with compositor, apps like dock, finder, status bar, and a UI framework like AppKit. Scratching my own itch and would love to see if it can gain traction. Still in the early innings though.
We (Geostar.ai) work with many brands and companies that have experienced near-death situations caused by Google's AI Overviews. The negative impact this feature has had on people's livelihoods is heartbreaking to witness.
Just today, I met with a small business owner who showed me that AIO is warning users that his business is a scam, based on bogus evidence (some unrelated brands). It's a new level of bullshit. There's not much these businesses can do other than playing the new GEO game if they want to get traffic from Google.
Who knows if Google will even present any search results other than AIO a few years from now.
Would be interested to learn more about how and why this was coded in Common Lisp, in particular which value it provides specific to the problem being solved compared to other languages.
Please take into account that Bluesky is still young and run by a small team which is moving fast. Ignoring a few reports that they consider non-critical is not a strong negative signal, especially not during a time of rapid growth and while they're in beta and invite-only. They just cracked the million users and are probably navigating through a lot of chaos on a daily basis. Those of us who've been in similar situations know that this is normal.
Shameless plug: I've recently started my own transactional email service (https://www.markix.com), primarily targeting small senders, after having been a very happy Postmark customer for a long time. Our service is still in closed beta but delivering live emails.
I run a couple other businesses and moved all of my transactional email sending over to Markix.
Would love to have a chat with anyone that might be starting a new project and is open to try out a new mail service (mail in bio).
Do you have a custom return-path configured? Using a custom return path might help, because it ties your reputation primarily to your domain.
ESPs check multiple factors. Both IP and domain reputation play a role. They will check your return path / envelope sender domain reputation and your IP. Your domain will start with it's own reputation, but can be boosted with a good IP reputation. But if your domain had bad sending behaviour in the past, that might be an issue.
Source: I'm running a transactional mail service that solely works with shared IPs: https://www.markix.com.
I'm building https://www.markix.com, a transactional email service that's meant to be boring and reliable.
At this stage, I'm primarily targeting small senders that need great reputation. There are no dedicated IPs. Emails are delivered from a pool of shared IPs that have great time-to-inbox and deliverability.
In contrast to other providers, I do not plan to support click and open tracking to protect recipients privacy. I'd appreciate feedback on that though.
Always happy to chat about email in general if there are any questions.
Is the solo part non-negotiable or would you consider working as a duo? I started multiple businesses alone for the past 10 years with a few successes and even more failures. While I wouldn't want to grow too large as a team, it can be quite depressing at times and that one time I worked with someone else has been immensely rewarding (and the business was a success!). If you were both aligned on your goals, your partner could hold you accountable right now and propose ideas to work on.
> How do I get an idea to start?
I usually check marketplaces where businesses are sold. Not to acquire one, but to get an idea of what makes money. Then start assessing each business from your point of view: Is it easy to build a similar product? Do you have ideas for a improvement? Do you have a strategic advantage through your network or knowledge?