home.social

Search

495 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. @zeab @acutesoftware Yeah, that’s one way to do it but requires breaking up existing notes/pages. So far I have no problems with #ObsidianMD and #BearNotes since they don’t use blocks. I haven’t tried with #NotionHQ but I suspect it would face similar issues with #Logseq

  5. Dự án của tôi (docker-staticmaps) bị Zeabur đưa vào làm mẫu triển khai một cú nhấp mà không xin phép, không ghi rõ giấy phép AGPL-3.0, không ghi công tác giả. Chỉ có một liên kết nhỏ đến tài liệu ở cuối trang. Việc này vi phạm điều khoản AGPL khi triển khai dịch vụ mạng. #AGPL #OpenSource #LicenseViolation #FreeSoftware #ViPhạmBảnQuyền #MãNguồnMở #PhầnMềmTựDo #Zeabur

    reddit.com/r/selfhosted/commen

  6. Dự án của tôi (docker-staticmaps) bị Zeabur đưa vào làm mẫu triển khai một cú nhấp mà không xin phép, không ghi rõ giấy phép AGPL-3.0, không ghi công tác giả. Chỉ có một liên kết nhỏ đến tài liệu ở cuối trang. Việc này vi phạm điều khoản AGPL khi triển khai dịch vụ mạng. #AGPL #OpenSource #LicenseViolation #FreeSoftware #ViPhạmBảnQuyền #MãNguồnMở #PhầnMềmTựDo #Zeabur

    reddit.com/r/opensource/commen

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

    Пользователи часто поднимают вопрос неадекватной стоимости исходящего трафика (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

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

    Пользователи часто поднимают вопрос неадекватной стоимости исходящего трафика (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

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

    Пользователи часто поднимают вопрос неадекватной стоимости исходящего трафика (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

  10. 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

  11. One of the promising things that has happened with ai agents is that we now. 😅 product is already well worth it. Now with the CLI, it just makes sense. Not everything needs the api. And these CLI tools make things easier for auth in general. 😎

    blog.dnsimple.com/2026/05/anno

  12. One of the promising things that has happened with ai agents is that we #CLI now. 😅 #DNSimple product is already well worth it. Now with the CLI, it just makes sense. Not everything needs the api. And these CLI tools make things easier for auth in general. 😎

    blog.dnsimple.com/2026/05/anno

  13. One of the promising things that has happened with ai agents is that we #CLI now. 😅 #DNSimple product is already well worth it. Now with the CLI, it just makes sense. Not everything needs the api. And these CLI tools make things easier for auth in general. 😎

    blog.dnsimple.com/2026/05/anno

  14. One of the promising things that has happened with ai agents is that we #CLI now. 😅 #DNSimple product is already well worth it. Now with the CLI, it just makes sense. Not everything needs the api. And these CLI tools make things easier for auth in general. 😎

    blog.dnsimple.com/2026/05/anno

  15. One of the promising things that has happened with ai agents is that we #CLI now. 😅 #DNSimple product is already well worth it. Now with the CLI, it just makes sense. Not everything needs the api. And these CLI tools make things easier for auth in general. 😎

    blog.dnsimple.com/2026/05/anno

  16. I'm quite curious what are the plans for on 2.0. They have an local renaissance in their hands. 😎

    duckdb.org/2026/05/12/quack-re

  17. I'm quite curious what are the plans for #DuckDB on 2.0. They have an #OLAP local renaissance in their hands. 😎

    duckdb.org/2026/05/12/quack-re

  18. I'm quite curious what are the plans for #DuckDB on 2.0. They have an #OLAP local renaissance in their hands. 😎

    duckdb.org/2026/05/12/quack-re

  19. I'm quite curious what are the plans for #DuckDB on 2.0. They have an #OLAP local renaissance in their hands. 😎

    duckdb.org/2026/05/12/quack-re

  20. I'm quite curious what are the plans for #DuckDB on 2.0. They have an #OLAP local renaissance in their hands. 😎

    duckdb.org/2026/05/12/quack-re

  21. #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-

  22. 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-

  23. #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-

  24. #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-

  25. #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-

  26. And... officially has a split product with db and og. It could work.

    But honestly.. I'm kind of liking obsidian now. 🫠 Sure it does 0.1 of what logseq can do. At the same, maybe that's ok? 😅

    Like if you enrich frontmatter, use tags, and follow principles, obsidian can do a lot.

    You don't need an everything tool. Just enough flexibility to shape your needs. 😉

    logseq.io/page/b2ad9ce1-9cb7-4

  27. And... #logseq officially has a split product with db and og. It could work.

    But honestly.. I'm kind of liking obsidian now. 🫠 Sure it does 0.1 of what logseq can do. At the same, maybe that's ok? 😅

    Like if you enrich frontmatter, use tags, and follow #outliner principles, obsidian can do a lot.

    You don't need an everything tool. Just enough flexibility to shape your needs. 😉

    logseq.io/page/b2ad9ce1-9cb7-4

  28. And... #logseq officially has a split product with db and og. It could work.

    But honestly.. I'm kind of liking obsidian now. 🫠 Sure it does 0.1 of what logseq can do. At the same, maybe that's ok? 😅

    Like if you enrich frontmatter, use tags, and follow #outliner principles, obsidian can do a lot.

    You don't need an everything tool. Just enough flexibility to shape your needs. 😉

    logseq.io/page/b2ad9ce1-9cb7-4

  29. And... #logseq officially has a split product with db and og. It could work.

    But honestly.. I'm kind of liking obsidian now. 🫠 Sure it does 0.1 of what logseq can do. At the same, maybe that's ok? 😅

    Like if you enrich frontmatter, use tags, and follow #outliner principles, obsidian can do a lot.

    You don't need an everything tool. Just enough flexibility to shape your needs. 😉

    logseq.io/page/b2ad9ce1-9cb7-4

  30. The ecosystem is interesting. Learning from to produce a concise artifacts.

    What makes it different is targets are based on which craft you use. Like if you want an app, then is likely it. But is a new one to target debs directly. Or say which creates an os image.

    In nix you target all the things with the same language. But I think this approach of target based tooling makes sense as well. 😅

    discourse.ubuntu.com/t/what-ma