#Development #Discussions
Influence the State of HTML 2025 survey · Which new HTML features or Web APIs are on your radar? https://ilo.im/1658sh
_____
#HTML #Survey #Community #Browser #Interoperability #WebPlatform #WebDev #Frontend #WebAPI
#WebAPI
Apple veröffentlicht Safari Technology Preview 222: Verbesserte Leistung und Fehlerbehebungen
Apple hat eine neue Version de
https://www.apfeltalk.de/magazin/news/apple-veroeffentlicht-safari-technology-preview-222-verbesserte-leistung-und-fehlerbehebungen/
#News #Services #Accessibility #Apple #CSS #Entwickler #Entwicklerfeedback #MacOSSequoia #MacOSTahoe #Media #ReleaseNotes #Rendering #SafariTechnologyPreview #Scrolling #Softwareaktualisierung #Testversion #Update #WebAPI #Webbrowser
File encryption with a browser.
I've been exploring the #WebCryptoAPI and I'm impressed!
When combined with the #FileSystemAPI, it offers a seemingly secure way to #encrypt and #store files directly on your device. Think #localstorage, but with #encryption!
I know #webapps can have #security vulnerabilities since the code is served over the web, so I've #OpenSourced my demo! You can check it out, and it should even work if #selfhosted on #GitHubPages.
Live Demo: https://dim.positive-intentions.com/?path=/story/usefs--encrypted-demo
Demo Code: https://github.com/positive-intentions/dim/blob/staging/src/stories/05-Hooks-useFS.stories.js
Hook Code: https://github.com/positive-intentions/dim/blob/staging/src/hooks/useFS.js
IMPORTANT NOTES (PLEASE READ!):
* This is NOT a product. It's for #testing and #demonstration purposes only.
* It has NOT been reviewed or audited. Do NOT use for sensitive data.
* The "password encryption" currently uses a hardcoded password. This is for demonstration, not security.
* This is NOT meant to replace robust solutions like #VeraCrypt. It's just a #proofofconcept to show what's possible with #browser #APIs.
#Encryption #Cryptography #JavaScript #Frontend #Privacy #Security #WebDevelopment #Coding #Developer #Tech #FOSS #OpenSource #GitHub #MastodonDev #Programming #WebStandards #FileSystem #WebAPI #ProofOfConcept
Using JsonPropertyName to map Json to Class C# Tip #42 - How to use the [JsonPropertyName] attribute in C# to map mismatched JSON fields (like "id") to class properties (like UniquePostId) during deserialization. #CSharp #JSON #Deserialization #HttpClient #JsonPropertyName #DataMapping #WebAPI #DotNet #Attributes
#ASPNETCore OData #WebAPI Template Preview is live! Scaffold #OData APIs in .NET 8+ with query options ($filter,$select,$expand), batch support, Swagger & case-insensitive routing. Install with
`dotnet new install Microsoft.OData.WebApiTemplate`
https://devblogs.microsoft.com/odata/asp-net-core-odata-web-api-template-preview-release/
I was writing yet another JsonConverter<T>... until I discovered how .NET handles polymorphic serialization with just two attributes 😲
Here’s how I ditched boilerplate & made my APIs cleaner with [JsonPolymorphic] + [JsonDerivedType] 🚀👇
https://wp.me/p29SK-ZB
#DotNet #CSharp #SystemTextJson #WebAPI #CleanCode
#ASPNETCore OData Web API Template Preview Release.
buff.ly/uFe42oL
#odata #webdev #webapi #dotnet
ASP.NET Core OData Web API Tem...
#ASPNETCore OData Web API Template Preview Release.
https://devblogs.microsoft.com/odata/asp-net-core-odata-web-api-template-preview-release/
Scalar на замену Swashbuckle в .NET 9 и как это готовить с Design API First
Рассказываю чем заменить Swashbuckle, который убрали из .Net 9, для создания страницы похожей на Swagger UI.
https://habr.com/ru/articles/904738/
#web_api #aspnet_core #swagger #open_api #net_9 #dotnet_core #dotnet #typespec #webapi #openapi
Software Consultant Bipin Joshi summarizes new OpenAPI document generation options and configurations when writing .NET Core web apis using .NET Core 9. He also shows how to read and visualize the generated document using Swagger.
Automatic OpenAPI document generation also facilitates integration with existing endpoint testing software, such as Scalar.
"Understand OpenAPI document generation in ASP.NET Core"
https://www.binaryintellect.net/articles/48c6fc8a-70bf-4cb3-af64-06ab33f83f40.aspx
An ASP.NET Core Web API of my authorship to access and manipulate project data using EF Core, and JWT on a PostgreSQL or SQL Server database.
Having played a bit I'm now adding #OpenAPI docs with #Swagger UI to #Autonomi dweb using #utoipa and #utoipauto.
EDIT: switched from #utoipauto to #utoipa_actix_web
I'm neither a user nor, until now a builder of HTTP APIs so stumbling around, but these crates do a decent job of being usable even to a novice.
I really shouldn't be let loose with all this :rofl:
Code on Demand is REST’s wildcard—optional but powerful. It lets servers send executable code to clients for enhanced functionality when needed. Want to know when, why, and how to use it effectively? Check out the latest post!
htmx up next!
https://woodruff.dev/rest-constraint-6-code-on-demand-when-why-and-how-to-use-it/
REST’s layered system is all about flexibility and scale. You can improve performance, security, and scalability by stacking components like gateways and load balancers without messing with the core API. Curious how this works? Check out my latest post!
https://woodruff.dev/rest-constraint-5-embracing-layers-for-flexibility-and-scale/
Caching is what makes REST APIs lightning fast. Performance gets a huge boost by sending clients reused responses instead of constantly asking servers. Want to see how caching works and why it matters? Check out my latest post!
https://woodruff.dev/rest-constraint-4-cacheable-for-better-performance/
Going stateless is one of REST’s secret weapons. Treating each request as independent makes APIs more scalable, reliable, and easier to cache. Want to know why statelessness is such a big deal? Read the post!
https://woodruff.dev/rest-constraint-3-going-stateless-for-scalability/
Client-server separation is the secret sauce behind REST’s scalability. By keeping the UI and data storage separate, each can evolve independently. Want to know why this design choice is such a game-changer? The blog post will explain a lot.
https://woodruff.dev/rest-constraint-2-why-client-server-separation-is-a-game-changer/
Great #RESTful APIs aren’t about cramming in features—they’re about keeping things simple. Clear URLs, predictable responses, and a clean structure make all the difference. Want to know why simplicity wins in #API design? Check out my latest post!
https://woodruff.dev/restful-api-design-why-simplicity-wins/
I am in the situation that I need to talk to a #WebAPI that I am not familiar with (PlayFab). The documentation could be better, so there is a lot of stuff that I need to find out by trial-and-error.
Some weeks ago I bought an issue of the c't magazine - the only one I bought in years - that by chance had an article about a tool for such a situation: #Bruno (https://www.usebruno.com/).
After playing around a bit with it: Full recommendation.
Lapidary-render 0.12.0 is now released.
To the best of my knowledge it's the only #codeGenerator that properly handles #jsonSchema anyOf and allOf.
Also has support for oneOf, but not per the specs.
https://github.com/python-lapidary/lapidary-render/releases/tag/v0.12.0
#pythonLapidary #openAPI #openAPI3 #openAPI30 #programming #python #webAPI
Client Info
Server: https://mastodon.social
Version: 2025.04
Repository: https://github.com/cyevgeniy/lmst