#there is an ARG about this entity that happened in 2021 !!!
Photo
Came-cruse, the 222nd Known One.
Despite its appearance, a camacrusa is very rapid in movement, capable of hiding behind haybales, jumping over ditches and hedges, and easily running down its prey – children who remain outside after dark. How it eats them is unspecified.
Text by @a-book-of-creatures, full entry here !
#came-cruse#i wanted to do this one for sooo long#there is an ARG about this entity that happened in 2021 !!!#on Airbnb ?? brilliant#another thing interesting some people have used the Fachan to illustrate the Camecruse and its also a one legged cyclop it may have a link??#ALSO once again ive done a limb based on myself#maybe one day with enough entries i could make a full body ahah#like Exodia in Yu-Gi-Yo#human#homonculus#body horror#France#Gascogne#the Known Ones#chimera#monster#creature design#folklore#bestiary#ink#888#octem 111#terra 4
58 notes
·
View notes
Text
You posted 3,756 times in 2022
That's 1,886 more posts than 2021!
131 posts created (3%)
3,625 posts reblogged (97%)
Blogs you reblogged the most:
@elytrians
@spooksier
@dudeiwannasleep
@mag200
@all-chickens-are-trans
You tagged 3,025 of your posts in 2022
Only 19% of your posts had no tags
#0 - 146 posts
#tma - 911 posts
#art - 648 posts
#jon my beloved - 221 posts
#tag game - 142 posts
#queer - 141 posts
#myar - 126 posts
#fav - 111 posts
#writing - 89 posts
#important - 83 posts
Longest Tag: 139 characters
#the biggest one is following instructions to a t but the other person gets mad at you cos apparently they wanted you to do 'implied' things
Your Top Posts in 2022:
#5
Everything everywhere all at once or something
76 notes - Posted October 18, 2022
#4
Ok so apparently ive admitted defeat about my resolve to not get hyped up. So since ive seen other people do it here's some things im hoping come out of this tma surprise
("Realistic chances" of any given idea happening have not been considered<3)
A full blown tma arg, where jon/martin/annabelle/oliver have travelled to our world along with the fears and are messaging in forums, posting videos, etc, trying to gain information and stop the fears from gaining power and stop our world from ending up on the same trajectory as theirs. We have to solve the arg to understand what is going on in Magnus Archives Part 2
HARDCOVER BOOKS OF PRINTED STATEMENTS GOD PLEASE
Tma artbook. Illustrated statements, entities concept art, bonus enamel pins, ceaseless watcher poster, map of uk but eldritch infested. Do you see my vision
(Once again taps sign that says "realistic chances" have not been considered, im just daydreaming<3)
Comeback of everyone's favorite bitch s1 jonathan 'everything is stupid and i hate gertrude' sims. Just him tearing some statements to pieces, classic s1 tma style
Animated statements. I do not want tma adapted to any other medium because it is made for audio-only but. I'll be very hyped for some statements animated shorts, like those banger Guest for Mr Spider animatics on yt
Jmart trauma recovery somewhere else 100k hurt/comfort podfic
TMA EPISODES TRANSLATED TO OTHER LANGUAGES DO YOU KNOW HOW COOL THAT WOULD BE
"Supplemental"
Feel free to add your own i wanna hear wjat other people want :]
78 notes - Posted October 13, 2022
#3
Friendly reminder to not let your queer headcanons take the spotlight away from the poc representation in the movie
91 notes - Posted January 12, 2022
#2
Hermitcraft Charity Livestream highlights so far
(Of the past 15 mins or so cos it just occured to me to note my fav moments) (which is basically all of them)
Grians cursed skins are back
The ACK! guy who kept coming back in donos abdj o7 o7 /pos
Banana false<3
PEARL WHAT IS THAT MASK GOOD GOD
Doc revealed his diamonds and everyone immediately stole them😭
Someone just donated 5k holy shit
Just. I love when everyone fires rockets in joy when the donos are being announced
On that note, martyn is SO good at the announcements, the hermits chose so well
THE GONG IS OUT
Ren: let me tell you, grian's gong is the most relaxing thing you'll ever experience
Grian: the most horrid parrot squacks while beating the gong
101 notes - Posted October 24, 2022
My #1 post of 2022
HELP tma is trending because of that live slug thing dhkkdd. Last month it was jurgen leitner getting piped. From now on i want tma to trend every month for some new insane reason
497 notes - Posted March 9, 2022
Get your Tumblr 2022 Year in Review →
#year in review#your tumblr year in review#2022#Yes i changed all the i's to yous cos i didnt like them#Girl i didnt write this post#But anyways this is SO fun :D#Ofc my top post is tma<3#also Excellent blogs to have as my most reblogged. Excellent taste on everyone's part<3
1 note
·
View note
Text
Exploring a minimal Web API with ASP.NET Core 6
I write about minimal Web APIs in 2016 and my goal has always been for "dotnet server.cs" to allow for a single file simple Web API. Fast forward to 2021 and there's some great work happening again in the minimal API space!
Let's do a 'dotnet new web' with the current .NET 6 preview. I'm on .NET 6 preview 7. As mentioned in the blog:
We updated .NET SDK templates to use the latest C# language features and patterns. We hadn’t revisited the templates in terms of new language features in a while. It was time to do that and we’ll ensure that the templates use new and modern features going forward.
The following language features are used in the new templates:
Top-level statements
async Main
Global using directives (via SDK driven defaults)
File-scoped namespaces
Target-typed new expressions
Nullable reference types
This is pretty cool. Perhaps initially a bit of a shock, but this a major version and a lot of work is being done to make C# and .NET more welcoming. All your favorite things are still there and will still work but we want to explore what can be done in this new space.
Richard puts the reasoning very well:
The templates are a much lower risk pivot point, where we’re able to set what the new “good default model” is for new code without nearly as much downstream consequence. By enabling these features via project templates, we’re getting the best of both worlds: new code starts with these features enabled but existing code isn’t impacted when you upgrade.
This means you'll see new things when you make something totally new from scratch but your existing stuff will mostly work just fine. I haven't had any trouble with my sites.
Let's look at a super basic hello world that returns text/plain:
var builder = WebApplication.CreateBuilder(args);
var app = builder.Build();
if (app.Environment.IsDevelopment()){ app.UseDeveloperExceptionPage(); }
app.MapGet("/", () => "Hello World!");
app.Run();
Slick. Note that I made line 3 (which is optional) just be one line to be terse. Not needed, just trying on these new shoes.
If we make this do more and support MVC, it's just a little larger. I could add in app.MapRazorPages() if I wanted instead of MapControllerRoute, which is what I use on my podcast site.
var builder = WebApplication.CreateBuilder(args);
// Add services to the container.
builder.Services.AddControllersWithViews();
var app = builder.Build();
// Configure the HTTP request pipeline.
if (app.Environment.IsDevelopment())
{
app.UseDeveloperExceptionPage();
}
else
{
app.UseExceptionHandler("/Home/Error");
// The default HSTS value is 30 days. You may want to change this for production scenarios, see https://aka.ms/aspnetcore-hsts.
app.UseHsts();
}
app.UseHttpsRedirection();
app.UseStaticFiles();
app.UseRouting();
app.UseAuthorization();
app.MapControllerRoute(
name: "default",
pattern: "{controller=Home}/{action=Index}/{id?}");
app.Run();
Back to the original Web API one. I can add Open API support by adding a reference to Swashbuckle.AspNetCore and then adding just a few lines:
var builder = WebApplication.CreateBuilder(args);
builder.Services.AddEndpointsApiExplorer();
builder.Services.AddSwaggerGen();
var app = builder.Build();
if (app.Environment.IsDevelopment())
{
app.UseDeveloperExceptionPage();
}
app.UseSwagger();
app.MapGet("/", () => "Hello World!");
app.UseSwaggerUI();
app.Run();
Then I hit https://localhost:5001/swagger and I get the SwaggerUI and a little WebAPI Tester:
Anuraj has a great blog where he goes deeper and pokes around David Fowlers GitHub and creates a minimal WebAPI with Entity Framework and an in-memory database with full OpenAPI support. He put the source at at https://github.com/anuraj/MinimalApi so check that out.
Bipin Joshi did a post also earlier in June and explored in a bit more detail how to hook up to real data and noted how easy it was to return entities with JSON output as the default. For example:
app.UseEndpoints(endpoints => {
endpoints.MapGet("/api/employees",([FromServices] AppDbContext db) =>
{
return db.Employees.ToList();
});
...snip...
}
That's it! Very clean.
Dave Brock did a tour as well and did Hello World in just three lines, but of course, you'll note he used WebApplication.Create while you'll want to use a Builder as seen above for real work.
var app = WebApplication.Create(args);
app.MapGet("/", () => "Hello World!");
await app.RunAsync();
Dave does point out how nice it is to work with simple models using the C# record keyword which removes a LOT of boilerplate cruft.
Check this out!
var app = WebApplication.Create(args);
app.MapGet("/person", () => new Person("Scott", "Hanselman"));
await app.RunAsync();
public record Person(string FirstName, string LastName);
That's it, and if you hit /person you'll get back a nice JSON WebAPI with this result:
{
firstName: "Scott",
lastName: "Hanselman"
}
Dig even deeper by checking out Maria Naggaga's presentation in June that's on YouTube where she talks about the thinking and research behind Minimal APIs and shows off more complex apps. Maria also did another great talk in the same vein for the Microsoft Reactor so check that out as well.
Is this just about number of lines of code? Have we moved your cheese? Will these scale to production? This is about enabling the creation of APIs that encapsulate best practices but can give you the "middleware-like" performance with the clarity and flexibility that was previous available with all the ceremony of MVC.
Here's some more resources:
David Fowler's GitHub demo https://github.com/davidfowl/dotnet6minimalapi/tree/main/Dotnet6_Minimal_API
A ToDo API as a Minimal API https://github.com/davidfowl/CommunityStandUpMinimalAPI
Exploring what Integration Testing looks like in a .NET 6 world by Martin Costello https://github.com/martincostello/dotnet-minimal-api-integration-testing I'll be exploring Martin's codebase next!
Have fun! Lots of cool things happening this year, even in the middle of the panini. Stay safe, friends.
Sponsor: Pluralsight helps teams build better tech skills through expert-led, hands-on practice and clear development paths. For a limited time, get 50% off your first month and start building stronger skills.
© 2021 Scott Hanselman. All rights reserved.
Exploring a minimal Web API with ASP.NET Core 6 published first on https://deskbysnafu.tumblr.com/
0 notes
Text
Exploring a minimal Web API with ASP.NET Core 6
I write about minimal Web APIs in 2016 and my goal has always been for "dotnet server.cs" to allow for a single file simple Web API. Fast forward to 2021 and there's some great work happening again in the minimal API space!
Let's do a 'dotnet new web' with the current .NET 6 preview. I'm on .NET 6 preview 7. As mentioned in the blog:
We updated .NET SDK templates to use the latest C# language features and patterns. We hadn’t revisited the templates in terms of new language features in a while. It was time to do that and we’ll ensure that the templates use new and modern features going forward.
The following language features are used in the new templates:
Top-level statements
async Main
Global using directives (via SDK driven defaults)
File-scoped namespaces
Target-typed new expressions
Nullable reference types
This is pretty cool. Perhaps initially a bit of a shock, but this a major version and a lot of work is being done to make C# and .NET more welcoming. All your favorite things are still there and will still work but we want to explore what can be done in this new space.
Richard puts the reasoning very well:
The templates are a much lower risk pivot point, where we’re able to set what the new “good default model” is for new code without nearly as much downstream consequence. By enabling these features via project templates, we’re getting the best of both worlds: new code starts with these features enabled but existing code isn’t impacted when you upgrade.
This means you'll see new things when you make something totally new from scratch but your existing stuff will mostly work just fine. I haven't had any trouble with my sites.
Let's look at a super basic hello world that returns text/plain:
var builder = WebApplication.CreateBuilder(args);
var app = builder.Build();
if (app.Environment.IsDevelopment()){ app.UseDeveloperExceptionPage(); }
app.MapGet("/", () => "Hello World!");
app.Run();
Slick. Note that I made line 3 (which is optional) just be one line to be terse. Not needed, just trying on these new shoes.
If we make this do more and support MVC, it's just a little larger. I could add in app.MapRazorPages() if I wanted instead of MapControllerRoute, which is what I use on my podcast site.
var builder = WebApplication.CreateBuilder(args);
// Add services to the container.
builder.Services.AddControllersWithViews();
var app = builder.Build();
// Configure the HTTP request pipeline.
if (app.Environment.IsDevelopment())
{
app.UseDeveloperExceptionPage();
}
else
{
app.UseExceptionHandler("/Home/Error");
// The default HSTS value is 30 days. You may want to change this for production scenarios, see https://aka.ms/aspnetcore-hsts.
app.UseHsts();
}
app.UseHttpsRedirection();
app.UseStaticFiles();
app.UseRouting();
app.UseAuthorization();
app.MapControllerRoute(
name: "default",
pattern: "{controller=Home}/{action=Index}/{id?}");
app.Run();
Back to the original Web API one. I can add Open API support by adding a reference to Swashbuckle.AspNetCore and then adding just a few lines:
var builder = WebApplication.CreateBuilder(args);
builder.Services.AddEndpointsApiExplorer();
builder.Services.AddSwaggerGen();
var app = builder.Build();
if (app.Environment.IsDevelopment())
{
app.UseDeveloperExceptionPage();
}
app.UseSwagger();
app.MapGet("/", () => "Hello World!");
app.UseSwaggerUI();
app.Run();
Then I hit https://localhost:5001/swagger and I get the SwaggerUI and a little WebAPI Tester:
Anuraj has a great blog where he goes deeper and pokes around David Fowlers GitHub and creates a minimal WebAPI with Entity Framework and an in-memory database with full OpenAPI support. He put the source at at https://github.com/anuraj/MinimalApi so check that out.
Bipin Joshi did a post also earlier in June and explored in a bit more detail how to hook up to real data and noted how easy it was to return entities with JSON output as the default. For example:
app.UseEndpoints(endpoints => {
endpoints.MapGet("/api/employees",([FromServices] AppDbContext db) =>
{
return db.Employees.ToList();
});
...snip...
}
That's it! Very clean.
Dave Brock did a tour as well and did Hello World in just three lines, but of course, you'll note he used WebApplication.Create while you'll want to use a Builder as seen above for real work.
var app = WebApplication.Create(args);
app.MapGet("/", () => "Hello World!");
await app.RunAsync();
Dave does point out how nice it is to work with simple models using the C# record keyword which removes a LOT of boilerplate cruft.
Check this out!
var app = WebApplication.Create(args);
app.MapGet("/person", () => new Person("Scott", "Hanselman"));
await app.RunAsync();
public record Person(string FirstName, string LastName);
That's it, and if you hit /person you'll get back a nice JSON WebAPI with this result:
{
firstName: "Scott",
lastName: "Hanselman"
}
Dig even deeper by checking out Maria Naggaga's presentation in June that's on YouTube where she talks about the thinking and research behind Minimal APIs and shows off more complex apps. Maria also did another great talk in the same vein for the Microsoft Reactor so check that out as well.
Is this just about number of lines of code? Have we moved your cheese? Will these scale to production? This is about enabling the creation of APIs that encapsulate best practices but can give you the "middleware-like" performance with the clarity and flexibility that was previous available with all the ceremony of MVC.
Here's some more resources:
David Fowler's GitHub demo https://github.com/davidfowl/dotnet6minimalapi/tree/main/Dotnet6_Minimal_API
A ToDo API as a Minimal API https://github.com/davidfowl/CommunityStandUpMinimalAPI
Exploring what Integration Testing looks like in a .NET 6 world by Martin Costello https://github.com/martincostello/dotnet-minimal-api-integration-testing I'll be exploring Martin's codebase next!
Have fun! Lots of cool things happening this year, even in the middle of the panini. Stay safe, friends.
Sponsor: Pluralsight helps teams build better tech skills through expert-led, hands-on practice and clear development paths. For a limited time, get 50% off your first month and start building stronger skills.
© 2021 Scott Hanselman. All rights reserved.
Exploring a minimal Web API with ASP.NET Core 6 published first on http://7elementswd.tumblr.com/
0 notes
Last Seen Blogs
mypocketcalculator
I Am The Operator
k-naji
Follow your Dreams
kaufvman
* 𝑏𝑜𝑦𝑠 𝑑𝑜𝑛'𝑡 𝑐𝑟𝑦.
winchestifer
SPN!Smuttland
ellyatjutju-blog
Untitled