home.social

#tomo — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #tomo, aggregated by home.social.

fetched live
  1. Aizawa Tomo, Carol Olston, Gundou Misuzu, Kubota Junichirou from Tomo-ChanWaOnnaNoKo by lewdamone
    #ass #blonde #breasts #boobs #bigtits #hentai #rule34 #nsfw #porn #tomo-chanwaonnanoko

  2. Aizawa Tomo, Kubota Junichirou from Tomo-ChanWaOnnaNoKo by flou_(flou_art), mint_moo_(voice_actor), teheefb
    #anal #ass #pussy #hentai #rule34 #nsfw #porn #tomo-chanwaonnanoko

  3. Aizawa Tomo from Tomo-ChanWaOnnaNoKo by ayana_maria_(voice_actor), jellymation
    #breasts #boobs #cum #doggystyle #hentai #rule34 #nsfw #porn #tomo-chanwaonnanoko

  4. Gundou Misuzu from Tomo-ChanWaOnnaNoKo by jellymation
    #hentai #rule34 #nsfw #porn #tomo-chanwaonnanoko

  5. Gundou Misuzu from Tomo-ChanWaOnnaNoKo by jellymation
    #hentai #rule34 #nsfw #porn #tomo-chanwaonnanoko

  6. Aizawa Akemi, Ferris Olston, Gundou Misaki from Tomo-ChanWaOnnaNoKo by orphen_(pink_seito)
    #blonde #breasts #boobs #fingering #bigtits #pussy #yuri #lesbian #hentai #rule34 #nsfw #porn #tomo-chanwaonnanoko

  7. Aizawa Akemi, Ferris Olston, Gundou Misaki from Tomo-ChanWaOnnaNoKo by xter
    #bikini #swimsuit #blonde #breasts #boobs #bigtits #ecchi #hot #sexy #goon #tomo-chanwaonnanoko

  8. Aizawa Akemi, Ferris Olston, Gundou Misaki from Tomo-ChanWaOnnaNoKo by orphen_(pink_seito)
    #blonde #breasts #boobs #fingering #bigtits #pussy #yuri #lesbian #hentai #rule34 #nsfw #porn #tomo-chanwaonnanoko

  9. Gundou Misuzu from Tomo-ChanWaOnnaNoKo by kasseus_maximus
    #cum #oral #hentai #rule34 #nsfw #porn #tomo-chanwaonnanoko

  10. US Top News and Analysis | Buy these two chip stocks primed to benefit from a foldable iPhone, says Barclays

    AI generated summary, Read the full article for complete information.

    Barclays analysts see semiconductor makers Skyworks Solutions and Qorvo poised for gains from Apple’s upcoming foldable iPhone, which is expected in September. The bank maintains an overweight rating on both stocks, with price targets of $70 for Skyworks and $100 for Qorvo, implying potential upside of roughly 17% and 20% respectively. The analysts argue that the new device will require advanced power‑management and structural chips, benefiting the two companies, even as Apple plans lower‑priced iPhone and MacBook models that could temper typical seasonal sales. Barclays’ bullish outlook diverges from the broader street consensus, where most analysts rate the stocks as holds.

    Read more: cnbc.com/2026/04/22/buy-these-

    #Barclays #SkyworksSolutions #Qorvo #Apple #TomO’Malley

    AI generated summary, Read the full article for complete information.

  11. new tomo dev .plan update

    tomo is dead: long live tomo

    a month away from tomo gave me time to think about why the project stalled out for such a long time, and where it could go now.

    tldr: tomo is getting a reboot as shard-based federated discussion forum. think of each shard like running your own BBS, except that it's linked with every other BBS on the network if you want it to be, with full privacy controls for each forum/topic.

    and no more NNTP. it was causing more heartache than it was worth, while adding almost nothing.

    read more here (RSS friendly):

    tomodori.net/#2026-03-04

    #fediverse #tomo #bbs #rss #nntp

  12. new tomo dev .plan update

    tomo is dead: long live tomo

    a month away from tomo gave me time to think about why the project stalled out for such a long time, and where it could go now.

    tldr: tomo is getting a reboot as shard-based federated discussion forum. think of each shard like running your own BBS, except that it's linked with every other BBS on the network if you want it to be, with full privacy controls for each forum/topic.

    and no more NNTP. it was causing more heartache than it was worth, while adding almost nothing.

    read more here (RSS friendly):

    tomodori.net/#2026-03-04

    #fediverse #tomo #bbs #rss #nntp

  13. fuck it. i'm declaring project bankruptcy with rslight-tomo.

    😆 😭

    after futzing around with tomo's (rslight-based) code for the afternoon, i realized that it's such an ensnarled mess that it's not worth trying to untangle the old rslight code from the tomo code i wrote over the last couple of years

    it reminds me a little of the source code for adventure game studio - a game building IDE that is over 20 years old.

    at some point open source projects have changed hands so many times that it's like trying to renovate a 300 year old house. the foundation was built in the 16th century by louise, the bedrooms in the 17th by raoul, and the bathrooms in the 18th by edward. you need to run new electrical wiring throughout the house, but none of it was ever built to accommodate conduits in the stone walls.

    you don't know why louise, raoul or edward designed things the way they did, and you can't ask them now. but you assume there was some kind of rationale to their decisions, so you work around their messes. it seems ok at first. the wiring runs on top of the stonework, but you've found a way to hide it in the crown moulding. you've got it running dangerously close to the water pipes, and god forbid you ever have to fix a broken wire, because you couldn't use conduit anywhere.

    after years of blood, sweat and tears, you've got howl's moving castle. your friends who visit call it quaint, but no one really wants to live there.

    that's what happened with RSLight. it was originally written by Florian Amrhein in 1999 until the mid-2000s. then over a decade later, Retro Guy picked it up and began extending those php scripts with his own particular code.

    and then i picked it up in 2023, and began trying to rewrite *both* retro guy's and florian's code.

    the truth is: louise and raoul and edward never knew what they were doing in the first place. they were all renovators just like me, using their meagre knowledge to solve problems particular to their time and place. the house was never built to accommodate the 21st century.

    it's not pretty. and worse, it's not maintainable. other people love howl's castle precisely because they don't have to live there; howl does.

    #tomo #nntp #programming

  14. fuck it. i'm declaring project bankruptcy with rslight-tomo.

    😆 😭

    after futzing around with tomo's (rslight-based) code for the afternoon, i realized that it's such an ensnarled mess that it's not worth trying to untangle the old rslight code from the tomo code i wrote over the last couple of years

    it reminds me a little of the source code for adventure game studio - a game building IDE that is over 20 years old.

    at some point open source projects have changed hands so many times that it's like trying to renovate a 300 year old house. the foundation was built in the 16th century by louise, the bedrooms in the 17th by raoul, and the bathrooms in the 18th by edward. you need to run new electrical wiring throughout the house, but none of it was ever built to accommodate conduits in the stone walls.

    you don't know why louise, raoul or edward designed things the way they did, and you can't ask them now. but you assume there was some kind of rationale to their decisions, so you work around their messes. it seems ok at first. the wiring runs on top of the stonework, but you've found a way to hide it in the crown moulding. you've got it running dangerously close to the water pipes, and god forbid you ever have to fix a broken wire, because you couldn't use conduit anywhere.

    after years of blood, sweat and tears, you've got howl's moving castle. your friends who visit call it quaint, but no one really wants to live there.

    that's what happened with RSLight. it was originally written by Florian Amrhein in 1999 until the mid-2000s. then over a decade later, Retro Guy picked it up and began extending those php scripts with his own particular code.

    and then i picked it up in 2023, and began trying to rewrite *both* retro guy's and florian's code.

    the truth is: louise and raoul and edward never knew what they were doing in the first place. they were all renovators just like me, using their meagre knowledge to solve problems particular to their time and place. the house was never built to accommodate the 21st century.

    it's not pretty. and worse, it's not maintainable. other people love howl's castle precisely because they don't have to live there; howl does.

    #tomo #nntp #programming

  15. blog post: death's inheritance and the future of tomo

    today, tomo appears to be the only fork of the RSLight nntp server that is still alive. so what now?

    i'll be honest: once Thom/Retro Guy died, i was very tempted to trash the project and move on. I have a half dozen other neglected development projects and books and a podcast to devote my research time to.

    and then I thought about Thom and the thousands of hours of his life that he put into his final project before he passed away. his dedication was infectious. and in 2026, we need decentralized forum software more than ever.

    that being said, I sure as hell don't want to be responsible for taking over someone else's open source project. that's almost as bad as adopting their kid. hard pass.
    .....
    rest of the post here:
    tomodori.net

    rss here:
    tomodori.net/rss.xml

    screenshot: the tomo interface for the user's private mailbox

    #tomo #smallWeb #nntp #usenet #indieWeb

  16. blog post: death's inheritance and the future of tomo

    today, tomo appears to be the only fork of the RSLight nntp server that is still alive. so what now?

    i'll be honest: once Thom/Retro Guy died, i was very tempted to trash the project and move on. I have a half dozen other neglected development projects and books and a podcast to devote my research time to.

    and then I thought about Thom and the thousands of hours of his life that he put into his final project before he passed away. his dedication was infectious. and in 2026, we need decentralized forum software more than ever.

    that being said, I sure as hell don't want to be responsible for taking over someone else's open source project. that's almost as bad as adopting their kid. hard pass.
    .....
    rest of the post here:
    tomodori.net

    rss here:
    tomodori.net/rss.xml

    screenshot: the tomo interface for the user's private mailbox

    #tomo #smallWeb #nntp #usenet #indieWeb

  17. @a good questions -

    all of the development on tomodori was done nearly two years ago. as it is, it's a nntp (and fully usenet-compatible) server with support for peer-peer server syncing. it is basically a re-implementation of "rocksolid" nntp server, with a proper web front end for things like creating new groups, user management, etc.

    development went on pause as i got stuck on a core design issue - how the "groups"-based system works. i've never been impressed with usenet's hierarchical approach (alt.binaries.dogs.etc.etc), and wanted to come up with something more imaginative/useful. and i didn't get anywhere with that design problem.

    the rocksolid server developer died earlier this year, sadly.

    as it stands, the server software works. i plan to release the project as FOSS in the new year, so people can try using it.

    #tomo #usenet

  18. @a good questions -

    all of the development on tomodori was done nearly two years ago. as it is, it's a nntp (and fully usenet-compatible) server with support for peer-peer server syncing. it is basically a re-implementation of "rocksolid" nntp server, with a proper web front end for things like creating new groups, user management, etc.

    development went on pause as i got stuck on a core design issue - how the "groups"-based system works. i've never been impressed with usenet's hierarchical approach (alt.binaries.dogs.etc.etc), and wanted to come up with something more imaginative/useful. and i didn't get anywhere with that design problem.

    the rocksolid server developer died earlier this year, sadly.

    as it stands, the server software works. i plan to release the project as FOSS in the new year, so people can try using it.

    #tomo #usenet

  19. 📰 Tomo-chan Is a Girl: A Hilarious Attempt at Friendship

    In the anime 'Tomo-chan Is a Girl!', the characters often find themselves in humorous situations as they navigate the complexities of friendship and romance. This tweet captures the essence of their comedic trials, inviting fans to enjoy another roun...

    🔗 Read more: animenewsdaily.us/articles/456

    #AnimeNews #CRUNCHYROLL #Tomo-chanIsAGirl!

  20. new tomo devlog post: how do you deal with shitty people behaviour?

    tomo.city/#2025-01-22

    excerpt:

    after posting that "Eris-Free Net" wikipedia article the other day, it made me think about how to deal with misbehaving shards on tomoNet, and how governance works on decentralized networks.

    when i started thinking about creating something like tomo years ago, i often thought about Ultima Online as - not so much a model for - but an example of a network of online communities that was always interesting and sometimes frustrating to deal with

    in-game, for several years, UO really was the "wild west" of online communities - so much was left up to players to figure out. for a long time, there were no game mechanics that enabled players to enact governance of their own (e.g. creating towns, villages, provinces and local laws). the outcome of this was that most often a kind of hillbilly/frontier justice, or outright dog-eat-dog existence, became the norm.

    this was great for player-killers and people who loved strife. it added some intensity to the game that no other game had, or in my view has ever had since. (WoW/EQ/etc all elected to bolt everything down and render the world in nerf).

    ...

    BBSes also had governance-by-sysop/god, FidoNet with network coordinators, and USENET with its backbone cabal.

    tomoNet - a network of tomo shards that agree to all swap groups/posts with one another - is going to have to deal with the question of (self-) governance sooner or later. at the moment, tomoBBS has no specific controls for managing defederation and it does *not* use the ActivityPub protocol. it needs some, and i need help thinking through what the options are, for a network based on NNTP.

    ...

    if you've got thoughts on how your online social community was governed (or failed to be governed) by its users, i'd love to hear about it. it's a wide open topic for debate, and there are no wrong answers at the moment.

    #tomo #ultima #fidonet #bbs

  21. @Screwtapello @Daveography you wouldn't believe how many days it took to get that exact kind of terminal styling (fixed titlebar, fixed bottombar, scrolling middle content) for tomo. 😓

    simple, clean, interface design is harder today than it was with a 132 column terminal!

    #tomo

  22. i've been having fun creating a DEC VT-320 styled interface for tomo.city which led me to rediscovering the Dynix unix system that powered many of our public libraries' catalogue searches in the 80s and 90s.

    just found out that until at least 2013, there were still telnettable dynix catalogues out there. sadly, the IPs I tried are all vacant. some of those systems were replaced.

    has anyone tried discovering ancient telnettable library catalogues via shodan? share your results!

    photo credit @skylarstrickland commons.wikimedia.org/wiki/Fil

    #tomo #libraries

  23. devlog post: tomoBBS back in full development!

    the most important part of this post is that i defined, conceptually, what tomo *is* and how the "tomo" or forum hierarchy works.

    going to /animals/pets/cats/tabby shows you the tabby tomo, but going to /animals/pets/cats/ shows you *all posts* in the tomos below that level of the hierarchy, like tabby, void, siamese, stupid and nutsy

    and of course, because i'm still in love with a Datatrain amber monochrome CRT that my aunt owned in 1988 (and i used to play Gorillas.bas on it), the entire interface has been reskinned to look like you're visiting a public library terminal in the 80s. 😅

    all the specifics here:
    tomo.city/#2025-01-12

    (and - yes, tomo will go into a private alpha in about a month - don't worry, i'll be asking everyone to join in and beat up the poor shard soon).

    #tomo #bbs

  24. new eXiGY devlog post: A drunken walk roadmap for the next couple of months

    www.exigy.org/plan?sort=new#20

    one question I continue to get almost daily is: when can we start goofing around with eXiGY?
    The first 9 months of the project involved roughing out all of the basic functions a 2D game making toolkit would require. I managed to get some basic saving and loading (aka. serialization) set up a few weeks ago, and while it requires some re-tuning, it's in there and working.

    In anticipating of a pre-pre-pre-pre-alpha coming soon, I'm spinning up a tomo shard to facilitate tester feedback, bug reports and creating a little eXiGY community. If you've never heard of tomo, I don't blame you! :) I've been pretty quiet about tomo's development over the past year, as all of my development time has been laser-focussed on eXiGY.

    The short of it is: tomo is a public forum/discussion system that runs on NNTP (the protocol that powers USENET). i realized a few weeks ago that it would be the perfect platform to use as eXiGY's home for discussions about the project, get some ideas and responses on the design of the program, and so on. if you want to read more about tomo, head over to tomo's project page here for a very quick overview: tomo.city/project

    so for the next couple of weeks, eXiGY will be on pause while I rebuild tomo to support posting, user profiles, avatars, bug reports, attachments so you can share your XGY projects, and all the fun stuff we'll need for some old fashioned bug huntin'. (tomo is brand spankin' new software too. so that means we'll be doing two pre-alphas in one!)

    #exigy #indiegamedev #tomo

  25. a year and a half later, finally an update on tomo: sometimes it takes a year to think through a design problem, because it's a life problem

    tomo.city/#2025-01-02

    #tomo #bbs

  26. In preparation of getting Sharkey ready for Web3 and the blockchain, we introduce:

    Sharkey
    X
    TOMO
    That's right! We're adding TOMOCOIN ​:patsTomo:​ integration. Directly into Sharkey. We hope this gets our users excited that we're now entering a NEW ERA of Sharkey.

    Users will be able to exchange and earn TOMOCOINs whenever they post or
    ​:neocat_heart:​ react a random post tastelessly. This can be used for things such as:
    - Buying rizz
    - Downloading games on Steam
    - Gay sex

    This change will be implemented into the next release. Stay tuned!
    #TOMOCOIN #TOMO 🚀🚀🚀🚀🚀🚀

  27. haven't done this before

    taking a week's break after 3 months of nonstop #tomo development and contract work for clients

    working on a SimLife/SimEarth-styled wildfire simulation game for a few days to recharge the creative batteries 🙏

    here's the beginnings of the UI for Wildfire

    #gamedev #1bit #monochrome

  28. once a week i treat myself to an americano at the best #coffee roaster in #yeg. 🤤

    programming #tomo and #gamedev every day tends to narrow my scope a lot, so having some design reading once a week helps to keep me open to new ideas for building online social worlds

  29. open design question for future #tomo architecture:

    what aspects of customizable #bbs (renegade, iniquity, wildcat, etc) or personal web pages (myspace, others?) were interesting or enjoyable for you as a user?

    one of the best requests i've received for tomo has been to allow people to create & visually customize their discussion groups.

    i've thought about just allowing for css tweaks, but allowing users to write custom html seems like a lot more fun. i'm all ears if you've got experience or ideas.