home.social

Search

365 results for “zeab”

  1. Zeabur 计划不再提供共享计算资源

    本月 23 日, PaaS 初创公司 Zeabur 宣布自身将不再提供平台客户共享的计算资源「共享集群」, 由于这部分共享资源依旧是基于 AWS 这样的基础设施供应商之上构建并提供的, 所以成本难以和 AWS 自身竞争, Zeabur 不得不额外支出成本来维持共享集群的运行, 以显得比 AWS 等厂商更有竞争力. 未来 Zeabur 将仅提供专用主机, 即用户通过 Zeabur 间接向 AWS, GCP, Hetzner 等供应商订购服务器, 而对于更高规格的计算需求, 也将提供订购这些供应商的集群计算服务, 被称为「专用集群」.

    3 月 15 日之后, 用户将无法继续创建新的部署在共享集群的项目, 4 月 1 日之后, 存量的共享集群项目也无法创建新服务. 对于存量客户, 已有的已在共享集群上部署的项目服务不会受到任何影响. 对于原本免费可用的共享集群资源, 也将在 3 月 15 日之后必须订阅开发者方案(每月 US$5)才能继续使用, 同时 Zeabur 也在考虑「移除开发者方案内包含的 5 美金共享集群使用额度」.

    Changelogs: 共享集群将不再开放新项目 - Zeabur

    #PaaS

  2. @zeab Thank you for sharing. This is really interesting to me.

    I think the spec format does make sense and it could be easily transformed into HTML with schema.org markup (that’s what I use in my recipe posts). It is kind of sad that the HTML version of recipes.cooklang.org does not have schema.org markup (or JSON-LD markup), but that would be a good contribution.

    I did not find any examples of the RSS feed format. I think that the description probably is expected to be cooklang rather than HTML, but it isn’t clear. I did not realize federation/spec.md was the RSS format.

    Maybe I’ll try to adopt the format so that I can write in cooklang and then format as HTML (or cooklang in RSS?) for my recipes from now on. It would be easier than trying to go schema.org markup to cooklang. Then I could federate out recipes to followers as normal in HTML, have search engines pick up the markup, and have it read via the cooklang recipes feed reader.

  3. @zeab as @laund noticed, *24.04* is named #Noble Numbat, next release with all #Rust replacements and additions is 25.10 called #Questing Quokka - it lies foundation to see if all that makes sense.

    Next #Ubuntu LTS 26.04 is called #Resolute Raccoon. We'll now shortly before RC if changes done to QQ stay in the LTS

  4. Неадекватная стоимость исходящего трафика у некоторых облачных хостеров

    Пользователи часто поднимают вопрос неадекватной стоимости исходящего трафика (egress) у отдельных облачных провайдеров. Если обычные хостеры не тарифицируют этот трафик, то некоторые другие сервисы устанавливают специальные тарифы . Как показывает практика, это может стать неприятным сюрпризом для клиентов.

    habr.com/ru/companies/ruvds/ar

    #ruvds_статьи #внешний_трафик #egress #тарифы #VPS #Bandwidth_Alliance #Civo #Cloudflare #Heroku #OVHcloud #Scaleway #Hetzner #Linode #Oracle_Cloud #Backblaze #Bunny_CDN #DigitalOcean #Entrywan #UpCloud #Vultr #Flyio #Koyeb #Alibaba_Cloud #Microsoft_Azure #Amazon_Web_Services #Railway #Zeabur #Google_Cloud #Vercel #Render #Netlify

  5. Неадекватная стоимость исходящего трафика у некоторых облачных хостеров

    Пользователи часто поднимают вопрос неадекватной стоимости исходящего трафика (egress) у отдельных облачных провайдеров. Если обычные хостеры не тарифицируют этот трафик, то некоторые другие сервисы устанавливают специальные тарифы . Как показывает практика, это может стать неприятным сюрпризом для клиентов.

    habr.com/ru/companies/ruvds/ar

    #ruvds_статьи #внешний_трафик #egress #тарифы #VPS #Bandwidth_Alliance #Civo #Cloudflare #Heroku #OVHcloud #Scaleway #Hetzner #Linode #Oracle_Cloud #Backblaze #Bunny_CDN #DigitalOcean #Entrywan #UpCloud #Vultr #Flyio #Koyeb #Alibaba_Cloud #Microsoft_Azure #Amazon_Web_Services #Railway #Zeabur #Google_Cloud #Vercel #Render #Netlify

  6. Неадекватная стоимость исходящего трафика у некоторых облачных хостеров

    Пользователи часто поднимают вопрос неадекватной стоимости исходящего трафика (egress) у отдельных облачных провайдеров. Если обычные хостеры не тарифицируют этот трафик, то некоторые другие сервисы устанавливают специальные тарифы . Как показывает практика, это может стать неприятным сюрпризом для клиентов.

    habr.com/ru/companies/ruvds/ar

    #ruvds_статьи #внешний_трафик #egress #тарифы #VPS #Bandwidth_Alliance #Civo #Cloudflare #Heroku #OVHcloud #Scaleway #Hetzner #Linode #Oracle_Cloud #Backblaze #Bunny_CDN #DigitalOcean #Entrywan #UpCloud #Vultr #Flyio #Koyeb #Alibaba_Cloud #Microsoft_Azure #Amazon_Web_Services #Railway #Zeabur #Google_Cloud #Vercel #Render #Netlify

  7. Africa Roundup: Goldman leads $30M Twiga raise, China grows tech influence, Jumia weathers lockup-expiry - Kenya’s Twiga Foods raised a total of $30 million in October from lenders and investors led by Goldm... more: feedproxy.google.com/~r/Techcr #u.s.securitiesandexchangecommission #phuthimahanyele-dabengwa #onlinemarketplaces #naspersfoundry #rocketinternet #startupcompany #africaroundup #goldmansachs #sanfrancisco #techadvocacy #unitedstates #companies

  8. And post speaks exactly towards why closed source move from makes no sense.

    Simply put, it's not security and it's not ai. 😅

    blog.discourse.org/2026/04/dis

  9. Interesting to see come out as the prime contender to . I did think was the easier of the bunch.

    Still, pretty cool to see work cross products to help out users move. 😎

    earthly.dev/blog/shutting-down

  10. Found out about and kind of in love. It's simple enough. No fluff and can do operations with keybindings. Absolute joy. 😄

    Honestly, I don't know why I haven't been trying file managers. I'm like 99.9999% in the terminal. 😅

  11. Kind of wild gets a description from guides posts.

    Not always should you reach for microservices (read never). 😅 But when your company is knee deep, it does help to have some common way for services. Plus dapr follows erlang patterns. 😎

    aws.amazon.com/blogs/opensourc

  12. But you may wonder... why not 'just' use the docker-language-server for ? Good question. You see~ if that's done, then I don't get all my terraform files working as intended.

    But I could simply leave as is. Then using the docker-language-server solely when the file is loaded, but then falling back to switching the language to hcl when I want the rest of the grammar.

    That's where the annoyance came from. 😅

  13. Without a doubt, I'm "trying to change a lightbulb."

    All I wanted was to start up a server. 🫠

    I'm now researching creating a grammar for docker-bake. Forking one. So I can get the bake set up "JUST right" on with docker-language-server. So I can fix the annoyance of being used incorrectly. Then refactor a dockerfile. So I can then upload into a registry cleanly.

    So I can finally host the darn thing. 🤣

    youtube.com/watch?v=5W4NFcamRhM

  14. #email standards are how to federate widely.

    I'm a fan of #JMAP. Extensively versatile protocol. Without the baggage of gotchas from #IMAP. 🫠

    But won't be adopted by corps. They already built their custom version on top of IMAP. 😅

    Still. Email works. 😎

    buttondown.com/blog/future-of-

  15. standards are how to federate widely.

    I'm a fan of . Extensively versatile protocol. Without the baggage of gotchas from . 🫠

    But won't be adopted by corps. They already built their custom version on top of IMAP. 😅

    Still. Email works. 😎

    buttondown.com/blog/future-of-

  16. #email standards are how to federate widely.

    I'm a fan of #JMAP. Extensively versatile protocol. Without the baggage of gotchas from #IMAP. 🫠

    But won't be adopted by corps. They already built their custom version on top of IMAP. 😅

    Still. Email works. 😎

    buttondown.com/blog/future-of-

  17. #email standards are how to federate widely.

    I'm a fan of #JMAP. Extensively versatile protocol. Without the baggage of gotchas from #IMAP. 🫠

    But won't be adopted by corps. They already built their custom version on top of IMAP. 😅

    Still. Email works. 😎

    buttondown.com/blog/future-of-

  18. #email standards are how to federate widely.

    I'm a fan of #JMAP. Extensively versatile protocol. Without the baggage of gotchas from #IMAP. 🫠

    But won't be adopted by corps. They already built their custom version on top of IMAP. 😅

    Still. Email works. 😎

    buttondown.com/blog/future-of-

  19. Everyone excited with #jujutsu. But I do think #sapling has a lot of polish. A fork of #mercurial, with lots of usability thoughts. 😎 And fully #git compatible as well.

    Of course, if you want the real MVP, mercurial is still around. All with the design of using a #DVCS that makes sense. 😁

    mercurial-scm.org/

  20. Everyone excited with #jujutsu. But I do think #sapling has a lot of polish. A fork of #mercurial, with lots of usability thoughts. 😎 And fully #git compatible as well.

    Of course, if you want the real MVP, mercurial is still around. All with the design of using a #DVCS that makes sense. 😁

    mercurial-scm.org/

  21. Everyone excited with #jujutsu. But I do think #sapling has a lot of polish. A fork of #mercurial, with lots of usability thoughts. 😎 And fully #git compatible as well.

    Of course, if you want the real MVP, mercurial is still around. All with the design of using a #DVCS that makes sense. 😁

    mercurial-scm.org/

  22. I just found out is unmaintained and fork exists. 🤯

    I can't even remember the last time I thought of using something else. Like... I forgot normal ls. 😅

    Any time on a server, it computes to me the "ls is old here." not that it's different. 🤣

    github.com/eza-community/eza

  23. So let's get this straight. is moving proprietary because ai is finding bugs. Bugs also can be patched by ai as well. And they think is the problem?! 🤣

    Mind you, ai will STILL find bugs on. 😅 AI is a lot of things, but these excuses are getting ridiculous. 🫠

    cal.com/blog/cal-com-goes-clos

  24. Discovered recently for artifact handling.

    I thought the normal way for these uploads was setting the metadata manually to the container registry. 😅

    Meaning... I'm using this now. 😁

    oras.land/

  25. All these quality of life improvements in #ghostty. 😍 Congrats to the whole team for 1.3.

    The native notification on command finish! I've had a #fishshell plugin for I don't know how many years for this... I'm going to need to test this magic. 😎

    ghostty.org/docs/install/relea