#Sydney #Skyline from #Milsons #Point #VividSydney by Kaye Menner Photography Wide variety #Prints & lovely #Products at:

https://kaye-menner.pixels.com/featured/sydney-skyline-from-milsons-point-during-vivid-sydney-kaye-menner.html

#reflections #harbour #lights #colorful #night #homedecor #mastoart #fediverse #fediart #fedigiftshop #giftideas #wallartforsale #Art #artforsale #BuyIntoArt #AYearForArt #Artist #FineArtAmerica #PhotographyFeed #VisualArts #CreativeArts

Alt...

**ACHIEVED 1ST PLACE IN FAA CONTEST - "Cityscapes at Night Photo Contest" June 2021 June 2018, I went into the City of Sydney to view firsthand the spectacular VIVID SYDNEY, a festival of light, patterns, music and ideas. This image is one of my long exposure photographs of the bright and pretty projections of light over the Sydney skyline captured from the northern Milsons Point side of the harbor under the Harbour Bridge. These colorful projections were continuously changing, illuminating the buildings in various pretty colors, making Sydney Harbour look like a piece of art with all the colorful reflections in the water. A must see if you are in Sydney late May to mid June. It is held each year. #VIVIDSYDNEY THE FINE ART AMERICA LOGO WILL NOT SHOW ON PURCHASED PRINTS OR PRODUCTS. By Kaye Menner Photography https://kaye-menner.pixels.com/featured/sydney-skyline-from-milsons-point-during-vivid-sydney-kaye-menner.html

I can see four things becoming tricky when it comes to comment control. One is if it isn't enough to add support for another implementation, and if either side actually had to change the way it handles permission in a way that isn't backwards-compatible.

The second one is that Hubzilla, (streams) and Forte don't simply allow or forbid comments, but they can allow only certain actors to comment, and be it all contacts of a channel. I don't know if GTS has that feature, or if it can support it.

The third one is that (streams) and Forte can limit the time in which a post can be commented. Channels can be configured so that comments are only allowed for a certain timespan, and individual posts can be configured so that they can only be commented on until a certain point in the future.

Now, the thing is that, much unlike all the many microblogging applications, the permissions in a conversation are always the same on (streams) and Forte (and also on Hubzilla). All comments, regardless of whether they come from (streams) or Mastodon or Lemmy or wherever, always have the same permissions as the post. Replying to a public conversation with a DM is not supported, for example; the DM will be regarded as a public comment.

This also means that you're only allowed to reply to a comment in a thread if you're also allowed to comment on the post itself. But if you're allowed to comment on the post, you're also allowed to reply to any comment in the conversation, full stop.

Speaking in "non-nomadic, no-enclosed-conversations ActivityPub" terms, this means that at a certain point after a post was sent, the owner of the post will have to automatically send a new version of both the post and all comments on the post, with comment permission revoked, around to all participants in the conversation as well as to everywhere that e.g. some Mastodon user has boosted one of the comments.

Either that, or a comment control FEP will have to include temporary comment permissions, and Mastodon and everything else will have to support them. I'm pretty sure that Mastodon users would love this feature, and they'd applaud Eugen Rochko for "inventing" it and "introducing it to the Fediverse". But (streams) and Forte certainly won't remove this feature just because the FEP don't support it.

As for how Hubzilla, (streams) and Forte handle this right now, AFAIK, they only advertise their comment permissions amongst each other. This means that if permission to comment is not granted, the comment button is removed from the UI. Not even greyed out, actually removed.

Towards the wider Fediverse, they act differently: They're fully aware that they can't keep a Mastodon account from commenting. Instead, they reject a comment that isn't allowed. And rejecting works differently on these three than on Mastodon: Rejected content is not first let into the inbox, then filtered and then deleted. It isn't let into the inbox in the first place. And if an activity has only got one possible recipient on a server, and that recipient doesn't allow that activity, the whole server rejects it.

The reason why this works for comment control is because conversations themselves work differently on these three (and Friendica) than on Mastodon: On Mastodon, replies go to a) whoever is mentioned and b) whoever follows the replier. On Friendica, Hubzilla, (streams) and Forte, comments always go straight to the conversation starter, even if they're comments on a comment on a comment on a comment, and from there to all participants in the thread. Of course, Mastodon users won't notice new comments until they're mentioned in the metadata.

Now, if the conversation starter rejects a comment that has actually been sent, the comment is not added to the conversation. This means two things: One, on the conversation starter's own stream, the comment does not appear as part of the conversation. Two, the comment is not forwarded to the other participants in the thread either.

From a Mastodon POV, this means that you may be able to see the branch of the conversation in which you've participated with your rejected comment in it on your own server. But if you go check the whole thread at its source, you will not see your rejected comment in the conversation.

A side-effect of this is that it isn't possible to reply to rejected comments either. Let's suppose you see some toot in your timeline. It's a comment on some (streams) post. What the commenter is blissfully unaware of: They aren't permitted to comment on this post. (streams) has rejected the comment. But you are amongst the lucky few who are permitted to comment.

Still, you can't reply to that one comment.

If a comment is rejected, then all replies to this comment are rejected, too, regardless of permissions. That's because they cannot be attached to the conversation because their own parent is missing. From your Mastodon POV, you will be able to reply. But your reply will never become part of the conversation.

This would all be a whole lot better if the entire Fediverse supported a) enclosed threaded conversations (as opposed to Twitter-like posts-and-more-posts piecemeal) and b) permissions, including comment control all the way to temporary comment permission.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #GoToSocial #Friendica #Hubzilla #Streams #(streams) #Forte #Permission #Permissions #ReplyControl

@paul

I can tell you exactly why:
#Trump declared all #homeless people are #Illegal2BHomeless in #AmeriKKKa with this:
https://www.whitehouse.gov/presidential-actions/2025/07/ending-crime-and-disorder-on-americas-streets/

And people even on the #Fediverse are ignoring 771,000 people.
https://beamship.mpaq.org/@bob/114541200532670451
So I'm camped in plane site for hopefully 90 days
https://kolektiva.social/@justbob/115214609904161483
#Portland #PDX #StopTheSweeps

Minneapolis had 13 people shot but blame the homeless and sweep them (no investigation). Portland had 2 people stabbed (barely a story in #StreetRoots).

Fediverse Report 135 - This week's #fediverse news

- @Mastodon launches paid hosting service for institutions
- Gaza Verified is a grassroots initiative to verify Palestinians on Mastodon who need aid, and who have recently completed a 22k USD fundraiser

https://connectedplaces.online/reports/fediverse-report-135/

Next, I wanted to see if (streams) had its way of quote-posting changed in the last seven years or so of development and forking. I expected it to quote-post like Hubzilla, namely by turning a BBcode short code into a dumb copy of the original upon sending, but I wanted to see proof. As (streams) is a fork of a fork of three forks of a fork (of a fork) of Hubzilla that's still maintained by Hubzilla's own creator, I would have been surprised if he had changed the way (streams) quote-posts at some point on the way.

So I quote-posted my own post on (streams) just to see what happens. And (streams) acted exactly like Hubzilla and not at all like described in FEP-044f on the surface. It still inserts a dumb copy.

Good thing I have access to the full source code of any message on (streams). So here's what happened, namely what I expected to happen: (streams) quote-posts like Hubzilla.

First of all, when I clicked the "Share" button, this short code was inserted into the post editor:

[share⁠=1198713][/share]

The number, by the way, is the running number of the message to quote-post on the server.

Upon sending the post, (streams) automatically "expanded" the short code into the dumb copy I had expected.

[⁠share author='Jupiter+Rowland' profile='https://hub.netzgemeinde.eu/channel/jupiter_rowland' portable_id='_moYLN61-o3FbP3jyThygMDf-bjF2cApXgkrwlAE77iKy19xM1_6F06V4b71eTkqqNaTUjGiN0lfw2dyn5nXRw' avatar='https://streams.elsmussols.net/xp/6b50efa4bb804860f6128bba791b74fab4a0a5e09dbcbee8d8ca77cee00f0330-6' link='https://hub.netzgemeinde.eu/item/0a1cdda5-eb1c-4a33-9574-ddd896977b4f' auth='true' posted='2025-09-21 19:42:56' message_id='https://hub.netzgemeinde.eu/item/0a1cdda5-eb1c-4a33-9574-ddd896977b4f'] ...(the source code of the original message goes here)... [/share]

Both Hubzilla and (streams) render this the same way, namely with a header line above the copy that includes the profile picture of the original author, the name of the original author with a Zot/Nomad-type link to their channel/account and a Zot/Nomad-type link to the original of the post ("Zot/Nomad-type" means that [zrl][/zrl] is used rather than [url][/url] which means that the ID of an observer on Hubzilla/(streams)/Forte is attached to the link for OpenWebAuth identity recognition purposes.)

At the same time, curiously, (streams) includes the line "rel": "https://misskey-hub.net/ns#_misskey_quote" and a line that starts with "name": "RE: and continues with the URL of the original message into the code for the link to the original message. The latter is identical to what Misskey and all Forkeys have in quote-posting notes in plain sight, only that (streams) only reveals it in the source code rather than in the content as well.

So this part of FEP-044f is implemented, albeit concealed from most people and only happening in the code.

Now, looking at the quote policy part, that looks like it could be possible to add to the Fediverse's permission champions Hubzilla, (streams) and Forte. After all, they already have comment controls with no FEP backing it (and if GoToSocial's quote policy can be made into an FEP, maybe so can (streams)' and Forte's comment controls so that they actually do blank out reply buttons on the farther ends of the Fediverse if the software on the farther ends implement support for that FEP).

This could be done at three levels again. I'll illustrate this with (streams) and Forte because they're quite a bit less complex than older Hubzilla.

At channel level, quote-posting (and maybe quoting as well) could be set as usually, namely to semi-public (= everyone in the Fediverse = no quote policy), restricted (= only your contacts) and only yourself. (Seriously, you don't want random passersby with no accounts to quote-post you. Even though you can allow them to comment on your posts if you dare.)

"Only yourself" could be overridden at contact level by permitting certain contacts to quote-post (and maybe quote) your messages. This is actually standard behaviour on (streams) and Forte.

And then there is the per-post level which would be similar to (streams)' and Forte's comment controls. These allow you to limit who may comment on a post to only your contacts and those who have already participated in the same conversation, and they allow you to turn off comments altogether.

Quote authorisation would not be much different in handling from manually moderating comments from those who technically aren't permitted to comment (only that spammers don't quote-post, at least not yet, and they probably never will because that simply makes no sense). So that'd be nothing really new.

Of course, this would have some limitations which come from how Hubzilla, (streams) and Forte work and from their conversation architecture.

The first limitation is that you could only give certain contacts permission to quote-post your posts if you didn't give it to the whole Fediverse. Channel-wide permissions are always inherited by contact-specific permissions, and this cannot be overridden. So you couldn't generally allow everyone to quote-post your posts except for one certain contact of yours.

The second limitation is that you can only control the permissions of contacts, but not of non-contacts. So you can't disallow some stranger whom you aren't connected to to quote-post your posts while everyone else is allowed.

Then again, FEP-044f doesn't make either of these two possible either. It can only define who is permitted to quote-post a post, not who isn't.

The third limitation is that, on Hubzilla, (streams) and Forte, comments always have the same permissions as the post that they belong to because comments always have the same owner as the post that they belong to. Basically, if FEP-044f was to be defined for each comment individually, it would have a chance of clashing with conversation containers as per FEP-171b.

Here on Hubzilla, as well as from (streams)' point of view, everyone's comments in this thread are owned by me because I've started the thread. And the permissions on all these comments are defined by my post. I've seen my share of permission clashes whenever someone on Mastodon replied to a public post or a public comment with a DM, and Hubzilla overrode this by forcing the permissions of the post on that reply.

In practice, this means that the quote policies of all comments would be the same as that of the post. At least that's how Hubzilla, (streams) and Forte would understand them because the concept of comments having different permissions than the post is alien to them. So if you say that I'm not permitted to quote-post your comment, but I say that anyone can quote-post my post, Hubzilla and (streams) override the quote policy that you've given your comment on Mastodon with the quote policy that I've given my post on Hubzilla, and I can quote-post you.

So the actually difficult part would be to implement an exception in how Hubzilla, (streams) and Forte handle comment permissions for quote policies and make them individual for each comment rather than making comments inherit them from the post.

Well, and lastly, if you permitted all your contacts to quote-post a post of yours, and you had a few more contacts, the "canQuote" section would end up monstrous. (A bit less so if you could cherry-pick those who are allowed to quote-post you on a per-post base, just like you can cherry-pick those who are allowed to see the post in the first place.) Also, I'm wondering just how well policies as per FEP-044f (and their implementations in various server applications) will work with DIDs as per FEP-ef61 which (streams) and Forte use, and I guess, so does Mitra now.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Misskey #Forkey #Forkeys #GoToSocial #Hubzilla #Streams #(streams) #Forte #Mitra #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #Permission #Permissions #FEP_044f #FEP_171b #FEP_e232 #FEP_ef61

Was Mastodon da gebaut hat, funktioniert nur innerhalb von Mastodon. Ich habe es ja oben erklärt:

• Auch wenn du einen Post als nicht quote-post-bar einstellst, können Pleroma, Misskey, Friendica & Co. den trotzdem ungehindert quote-posten.
• Gleichzeitig kann niemand auf Mastodon irgendwas auf Pleroma, Misskey, Friendica & Co. quote-posten, obwohl es jeder darf.

Sie hätten die Art des Quote-Postens übernehmen können, die Misskey schon lange hat und die auch Threads verwendet. Sie hätten die Art des Quote-Postens übernehmen können, die Friendica seit über 15 Jahren erfolgreich einsetzt. Nein, statt dessen hat Mastodon eine eigene, proprietäre Technik entwickelt und sich mit vollem Vorsatz zum Rest des Fediverse noch inkompatibler gemacht.

Aber noch einmal: Mike Macgirvin sagt, es ist technisch nicht möglich, Quote-Posts von öffentlichen Posts zu verhindern. Und noch einmal: Der Mann muß es wissen.

Mike entwickelt schon seit fast einem halben Jahrhundert Software. Er ist Profi. Er war mal bezahlter Profi. Mike hat Friendica rausgehauen, da ging Eugen Rochko noch zur Schule.

Mike hat mehr Fediverse-Serveranwendungen entwickelt als jeder andere da draußen. Jede einzelne davon ist von den Features her leistungsfähiger als alles andere, was es im Fediverse gibt. Mike hat im Alleingang sogar mehr Fediverse-Protokolle entwickelt als jeder andere da draußen. Mike hat nomadische Identität im Alleingang erfunden, und sie funktioniert seit 2012.

Und Mike hat in puncto Sicherheit und Berechtigungssteuerung weit mehr gemacht als jeder andere Fediverse-Entwickler. Das, was er entwickelt hat, ist in seiner Funktionalität auch nicht eingeschränkt auf die eigene Software, sondern er hat sich immer auch Gedanken darüber gemacht, wie es außerhalb funktioniert, während für Eugen Rochko alles außerhalb von Mastodon Feindesland ist, das ignoriert wird und totgeschwiegen gehört.

Ganz ehrlich: Was vor allem Hubzilla und (streams) und Forte können in puncto Berechtigungssteuerung, das ist für die meisten Mastodon-Nutzer vollkommen unvorstellbar. Es gibt Berechtigungseinstellungen auf bis zu drei Ebenen (ganzer Kanal, einzelne Kontakte, pro Post/Thread) für fast alles bis hin zu Features, die Mastodon gar nicht hat.

Nur für Quote-Posts gibt's keine. Weil das fediverseweit nicht möglich ist.

Wenn es öffentlich ist und jeder es sehen kann, dann kann es auch jeder quote-posten. Das geht schlicht und ergreifend nicht zu verhindern. Nicht mal innerhalb von Hubzilla und (streams) und Forte. Außerhalb schon mal erst recht nicht.

Innerhalb von Mastodon geht's nur aus zwei Gründen. Zum einen, weil Mastodon den ganzen Rest des Fediverse bestenfalls komplett ignoriert. Zum anderen, weil Mastodon-Nutzer zwingend für jeden Pups auf GUI-Knöpfchen angewiesen sind. Sie sind es nicht gewohnt, irgendwas in ihren Tröts per Hand zu formatieren, weil sie noch nie irgendwas haben formatieren können. Und weil gefühlt beinahe jeder nur ein Smartphone und eine dedizierte Mastodon-App verwendet und kein Copy-Paste kennt, ist das Quote-Post-GUI-Knöpfchen das einzige, was sie haben, abgesehen von Screenshots.

Aber schon Mastodons Methode funktioniert, wie ich oben schon schrieb, nicht über Mastodon hinaus. Und da kann Mastodon lange drauf warten, daß der Rest des Fediverse seine eigene jahrelang etablierte Technologie wegschmeißt und auf Mastodons proprietäre Technologie umschwenkt.

Auf Misskey, den Forkeys und allen anderen, die auf dieselbe Art quote-posten, ist Quote-Posten überhaupt nicht verhinderbar. Das liegt daran, daß Quote-Posts pupeinfach als Link auf den Originalbeitrag ausgeführt sind mit "RE:" davor. RE: https://domain.tld/Adresse_des_Originalbeitrags Zack, hast du einen Quote-Post. Und mal ehrlich, für sowas braucht man kein GUI-Knöpfchen, wenn man tippen und URLs copy-pasten kann.

Auch auf Friendica, Hubzilla, (streams) und Forte, die ganz anders quote-posten, ist Quote-Posten öffentlicher Beiträge nicht verhinderbar. Da nutzen die Leute keine Apps auf Smartphones. Nein, die meisten sitzen am Desktop-PC oder Laptop mit Hardwaretastatur und nutzen einen Standardbrowser statt einer dedizierten App. Copy-Paste ist für sie kein Problem und schon gar kein Fremdwort. Außerdem sind vor allem die alten Hasen es höchstwahrscheinlich meistens gewohnt, Markup-Code für Formatierungen per Hand einzutippen, statt sich auf die GUI-Knöpfchen zu verlassen, die auch nur BBcode-Stückchen in den Editor reinpflanzen.

Mike Macgirvin sagt: Es gibt genau eine Art und Weise, wirksam fediverseweit zu verhindern, daß du gequote-postet wirst. Und das ist, nicht öffentlich zu posten.

Für jemanden für ihn ist es aber auch einfach, das zu sagen. Gerade auf Hubzilla, (streams) und Forte gibt es etliche Abstufungen zwischen öffentlich und DM. Auf Hubzilla kann ich einen Post

• in alle Öffentlichkeit
• nur an mich selbst
• an eine bestimmte Privacy Group (quasi wie eine Liste auf Mastodon, aber sehr viel mächtiger)
• an diejenigen, denen ich ein Profil zugewiesen habe, das nicht das Standardprofil meines Kanals ist (Mastodon hat dagegen nur ein Profil pro Konto)
• an ein bestimmtes Forum/eine bestimmte Gruppe
• eine beliebige individuelle Auswahl aus einzelnen Kontakten, Foren/Gruppen, Privacy Groups und Profilzugewiesenen

Und der Witz ist: Das steuert nicht nur, an wen der Post geht. Das steuert auch, wer den Post (und sämtliche Kommentare zum Post) sehen darf. Wenn der Post nicht an dich geht, wirst du ihn nie zu Gesicht bekommen. Nein, auch nicht per Boost. Das ist nämlich bei nichtöffentlichen Posts explizit verboten, und das dafür nötige Bedienelement ist schlicht und ergreifend nicht da.

Es wird noch besser: Das funktioniert sogar bis nach Mastodon. Denn wenn es nicht öffentlich ist, dann stellt es sich Mastodon gegenüber als DM dar.

Ich setze noch einen drauf: Im krassen Gegensatz zum restlichen Fediverse posten Hubzilla, (streams) und Forte mit Standardeinstellungen nicht öffentlich. Alle drei haben standardmäßig schon eine Privacy Group/Zugriffsliste namens "Freunde", in der alle neuen Kontakte landen. Und alle drei posten standardmäßig nur zu dieser Privacy Group/Zugriffsliste namens "Freunde". Aus Mastodon-Sicht verschicken alle drei standardmäßig immer nur DMs. Wenn du öffentlich posten willst, ist das Extraaufwand.

So gehen Sicherheit und Privatsphäre. Und nicht mit proprietärem, zu nichts anderem kompatiblem Hokuspokus für Doofe wie auf Mastodon.

#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Pleroma #Misskey #Forkey #Forkeys #Friendica #Hubzilla #Streams #(streams) #Forte #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteTröt #QuoteTröts #Drüko #Drükos #Druko #Drukos #QuoteBoost #QuoteBoosts #QuotePostDebatte #QuoteTrötDebatte #Sicherheit #Berechtigung #Berechtigungen

#Pretty #Waves in #Paradise by Kaye Menner #Photography Wide variety #Prints & lovely #Products at:

https://kaye-menner.pixels.com/featured/pretty-waves-in-paradise-by-kaye-menner-kaye-menner.html

#beach #water #sand #clouds #sky #photography #beauty #peaceful #relax #homedecor #mastoart #fediverse #fediart #fedigiftshop #giftideas #wallartforsale #Art #artforsale #BuyIntoArt #AYearForArt #Artist #FineArtAmerica #PhotographyFeed #VisualArts #CreativeArts

Alt...

A photograph I captured on a perfect day of sunshine and warmth on 20th May 2016 at Palm Beach, Sydney, Australia. The sea was tranquil and crystal clear with many beautiful colors and pretty small waves were lapping at the seashore upon the colorful wet sand. There was a beautiful rich blue sky with some cumulus clouds floating by. It was just like paradise. May is our last month of Autumn, but our weather has been like summer or spring. Warm and beautiful. By Kaye Menner Photography https://kaye-menner.pixels.com/featured/pretty-waves-in-paradise-by-kaye-menner-kaye-menner.html THE FINE ART AMERICA LOGO WILL NOT APPEAR ON PURCHASED PRINTS OR PRODUCTS.

#Blooming #White #Azaleas by Kaye Menner #Photography Wide variety #Prints & lovely #Products at:

https://kaye-menner.pixels.com/featured/blooming-white-azaleas-by-kaye-menner-kaye-menner.html

#flowers #flora #whiteflowers #pinkcentres #homedecor #mastoart #fediverse #fediart #fedigiftshop #giftideas #wallartforsale #Art #artforsale #BuyIntoArt #AYearForArt #Artist #FineArtAmerica #PhotographyFeed #VisualArts #CreativeArts

Alt...

I captured these pretty Azaleas near my home in the north of Sydney, NSW, Australia. By Kaye Menner Photography https://kaye-menner.pixels.com/featured/blooming-white-azaleas-by-kaye-menner-kaye-menner.html Vibrant azaleas in full bloom are captured under bright sunlight, showcasing their white petals with pink accents. The surrounding green foliage adds to the composition's lushness. The image shows a lush cluster of blooming azaleas with large, delicate white petals with vibrant pink speckles at their centers. The flowers are in full bloom, creating a striking contrast against the deep green leaves surrounding them. Sunlight brightens the blossoms, highlighting their soft texture and the intricate details of the stamens, while a brilliant blue sky peeks through the background. The overall scene radiates freshness and the beauty of springtime in full flourish.

Holstein Soak: https://1-lisas-baker.pixels.com/featured/holstein-soak-lisa-s-baker.html

#holstein #cow #bovine #farm #farmanimal #blackandwhite #art #arte #artwork #wallart #homedecor #artforhome #artforsale #buyintoart #mastoart #fediart #fediverse #artprints #canvasprints #cowart #whimsical #fun #pretty #charming #farmart #cowart #puzzles #stationary #shabbychic

Alt...

Holstein Soak / Cow Art by Lisa S Baker. A whimsical scene features a black and white cow leisurely lying in a vintage clawfoot bathtub. The colorful, floral-patterned wallpaper adds a playful and surreal backdrop, contrasting with the serene expression of the cow. The image combines elements of humor and peculiarity, inviting a smile from the viewer.

I'm a computer programmer with a Fediverse account, and I am this many years old.

Please consider boosting for a more representative sample.

#programming #poll #demographics #fediverse #age

#Pier Over #Ocean at #Sunrise by Kaye Menner Wide variety #Prints & lovely #Products at:

https://kaye-menner.pixels.com/featured/pier-over-ocean-at-sunrise-by-kaye-menner-kaye-menner.html

#beach #water #waves #jetty #pier #sun #reflections #colorful #ai #digitalart #homedecor #mastoart #fediverse #fediart #fedigiftshop #giftideas #wallartforsale #Art #artforsale #BuyIntoArt #AYearForArt #Artist #FineArtAmerica #PhotographyFeed #VisualArts #CreativeArts

Alt...

A serene sunrise casts a warm glow over a tranquil sea or ocean with gentle waves breaking on the shore. A wooden pier extends into the water, offering a peaceful viewpoint to enjoy the vibrant skies. By Kaye Menner https://kaye-menner.pixels.com/featured/pier-over-ocean-at-sunrise-by-kaye-menner-kaye-menner.html THE FINE ART AMERICA LOGO WILL NOT APPEAR ON PURCHASED PRINTS OR PRODUCTS.

I guess @NanoRaptor is being a #Fediverse #Celebrity.

• I do wished her #cursed / #shitpost #tech wasn't being auto-deleted but #archived.

If, in a hypothetical situation, a benevolent Alien race comes to Earth & says that Earth will be annihilated by a gamma-ray burst in 5 years, which will be affirmed by NASA. 

They are moving the entire human population to a habitable planet in another place. How will you react? Will you buy it?

#thoughtExperiment #science #knowledge #space #astronomy #research #scicomm #Astrodon #OpenScience #explore #aliens #earth #nasa #opinion #fediverse #philosophy #thought #mastodon #author #writing

#Furnace in a #Tulip 2 by Kaye Menner #Photography Wide variety #Prints & lovely #Products at:

https://kaye-menner.pixels.com/featured/furnace-in-a-tulip-2-kaye-menner.html

#droplets #night #nightlight #macro #stamen #light #redyellow #homedecor #mastoart #fediverse #fediart #fedigiftshop #giftideas #wallartforsale #Art #artforsale #BuyIntoArt #AYearForArt #Artist #FineArtAmerica #PhotographyFeed #VisualArts #CreativeArts

Alt...

My macro image of a Tulip at night with water droplets lit from behind. I love playing with light. By Kaye Menner Photography https://kaye-menner.pixels.com/featured/furnace-in-a-tulip-2-kaye-menner.html THE FINE ART AMERICA LOGO WILL NOT SHOW ON PURCHASED PRINTS OR PRODUCTS.